Closed carrierone closed 3 weeks ago
I2C scan says that there is a device with address 0x41. Have you changed its address from 0x43 to 0x41 as it can be changed via a register? Or is something else connected to this bus?
I thought maybe it was that but when I set the 8angle to 0x41 it crashed the esp. So I am pretty sure that 0x41 is the esp itself. It does in fact see the 8angle on 0x43 in the log it just won't load the module --Sent with GMX Mail appOn 8/22/24, 3:35 AM Roman Priesol @.***> wrote:
I2C scan says that there is a device with address 0x41. Have you changed its address from 0x43 to 0x41 as it can be changed via a register? Or is something else connected to this bus? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Nope, there is nothing connected to the external connector. Only Atom S3 has mcp23017 (0x20) connected to 38/39.
It's weird that the 8angle is on 0x41 new out of the box, so I changed the esphome config to 0x41 and still getting the same error but its now logging some other problem _Component m5stack8angle.sensor took a long time for an operation but I'm more concerned about the _Component m5stack8angle is marked FAILED
Any chance you can assign this to @rnauber so he can look at this?
[02:10:48][C][logger:186]: Level: DEBUG [02:10:48][C][logger:188]: Log Baud Rate: 115200 [02:10:48][C][logger:189]: Hardware UART: UART0 [02:10:48][C][i2c.idf:075]: I2C Bus: [02:10:48][C][i2c.idf:076]: SDA Pin: GPIO26 [02:10:48][C][i2c.idf:077]: SCL Pin: GPIO32 [02:10:48][C][i2c.idf:078]: Frequency: 50000 Hz [02:10:48][C][i2c.idf:084]: Recovery: bus successfully recovered [02:10:48][I][i2c.idf:094]: Results from i2c bus scan: [02:10:48][I][i2c.idf:100]: Found i2c device at address 0x41 [02:10:48][C][esp32_rmt_led_strip:175]: ESP32 RMT LED Strip: [02:10:48][C][esp32_rmt_led_strip:176]: Pin: 27 [02:10:48][C][esp32_rmt_led_strip:177]: Channel: 0 [02:10:48][C][esp32_rmt_led_strip:202]: RGB Order: GRB [02:10:48][C][esp32_rmt_led_strip:203]: Max refresh rate: 0 [02:10:48][C][esp32_rmt_led_strip:204]: Number of LEDs: 1 [02:10:48][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Button' [02:10:48][C][gpio.binary_sensor:016]: Pin: GPIO39
[02:10:48][C][light:105]: Default Transition Length: 0.0s [02:10:48][C][light:106]: Gamma Correct: 2.80 [02:10:48][C][template.switch:068]: Template Switch 'Use wake word' [02:10:48][C][template.switch:091]: Restore Mode: restore defaults to ON [02:10:48][C][template.switch:057]: Optimistic: YES [02:10:48][C][template.switch:068]: Template Switch 'Use listen light' [02:10:48][C][template.switch:091]: Restore Mode: restore defaults to ON [02:10:48][C][template.switch:057]: Optimistic: YES [02:10:48][C][template.switch:068]: Template Switch 'timer_ringing' [02:10:48][C][template.switch:091]: Restore Mode: always OFF [02:10:48][C][template.switch:057]: Optimistic: YES [02:10:48][C][safe_mode.button:024]: Safe Mode Button 'Safe Mode Boot'
[02:10:48][C][factory_reset.button:011]: Factory Reset Button 'Factory reset'
[02:10:48][C][m5stack_8angle:031]: Address: 0x41 [02:10:48][C][m5stack_8angle:032]: Firmware version: 0 [02:10:48][E][component:082]: Component m5stack_8angle is marked FAILED
[02:10:49][C][mdns:117]: Hostname: m5stack-atom-echo-168750 [02:10:49][C][esphome.ota:073]: Over-The-Air updates: [02:10:49][C][esphome.ota:074]: Address: m5stack-atom-echo-168750.lan:3232 [02:10:49][C][esphome.ota:075]: Version: 2 [02:10:49][C][safe_mode:018]: Safe Mode: [02:10:49][C][safe_mode:020]: Boot considered successful after 60 seconds [02:10:49][C][safe_mode:021]: Invoke after 10 boot attempts [02:10:49][C][safe_mode:023]: Remain in safe mode for 300 seconds [02:10:49][C][api:139]: API Server: [02:10:49][C][api:140]: Address: m5stack-atom-echo-168750.lan:6053 [02:10:49][C][api:142]: Using noise encryption: YES [02:10:52][W][component:237]: Component m5stack_8angle.sensor took a long time for an operation (1001 ms). [02:10:52][W][component:238]: Components should block for at most 30 ms. [02:10:53][W][component:237]: Component m5stack_8angle.sensor took a long time for an operation (1000 ms). [02:10:53][W][component:238]: Components should block for at most 30 ms. [02:11:02][W][component:237]: Component m5stack_8angle.sensor took a long time for an operation (1001 ms). [02:11:02][W][component:238]: Components should block for at most 30 ms. [02:11:03][W][component:237]: Component m5stack_8angle.sensor took a long time for an operation (1000 ms). [02:11:03][W][component:238]: Components should block for at most 30 ms.
So sorry! I just realized I have the 8encoder not the 8angle, I didn't even know there was two different things that looked so similar! Now it makes sense why the ID is different!
yup, unfortunately they used totally different registers http://docs.m5stack.com/en/unit/8Angle / https://docs.m5stack.com/en/unit/UNIT%208EnCoder
The problem
Component m5stack_8angle is marked FAILED on startup. This is a new module so not sure if its a bug or I configured it wrong.
Which version of ESPHome has the issue?
2024.8.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.8.2
What platform are you using?
ESP32-ADF
Board
m5stack Atom Echo with m5stack 8Angle
Component causing the issue
components/m5stack_8angle
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response