async_initialize' stage failed: 'power_on_state'
See original GitHub issueThe problem
In my logs for zigbee im getting these for y zigbee module switches
Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486
Integration: Zigbee Home Automation ([documentation](https://www.home-assistant.io/integrations/zha), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+zha%22))
First occurred: 7:30:48 am (60 occurrences)
Last logged: 7:30:48 am
[0xE469:3:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0x52E6:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0x0900:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0xB6F3:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0x62EF:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
What version of Home Assistant Core has the issue?
Home Assistant 2022.11.2
What was the last working version of Home Assistant Core?
Unsure
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zha
Link to integration documentation on our website
No response
Diagnostics information
Logger: homeassistant.components.zha.core.channels.base Source: components/zha/core/channels/base.py:486 Integration: Zigbee Home Automation (documentation, issues) First occurred: 7:30:48 am (60 occurrences) Last logged: 7:30:48 am
[0xE469:3:0x0006]: ‘async_initialize’ stage failed: ‘power_on_state’ [0x52E6:1:0x0006]: ‘async_initialize’ stage failed: ‘power_on_state’ [0x0900:1:0x0006]: ‘async_initialize’ stage failed: ‘power_on_state’ [0xB6F3:1:0x0006]: ‘async_initialize’ stage failed: ‘power_on_state’ [0x62EF:1:0x0006]: ‘async_initialize’ stage failed: ‘power_on_state’
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 7:30:48 am (60 occurrences)
Last logged: 7:30:48 am
[0xE469:3:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0x52E6:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0x0900:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0xB6F3:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
[0x62EF:1:0x0006]: 'async_initialize' stage failed: 'power_on_state'
Additional information
No response
Issue Analytics
- State:
- Created 10 months ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
PowerOnState - Tasmota
The setting of the relay GPIO is then executed. After a warm restart, the mask variable is re-initialised with the saved state from...
Read more >poweronstate 1 not working for Sonoff Dual R2 Module both ...
PROBLEM DESCRIPTION poweronstate 1 not working for Sonoff Dual R2 Module for both relais only relais 2 is on after powerup. powerupstate 1 ......
Read more >PowerOnState (e.g., =1) relay settings at boot: MQTT state ...
I am new to Home Assistant, Sonoff and Tasmota, this noob question might have an easy answer - but I can't find it....
Read more >Sonoff basic (tasmota) turns on automatically after power ...
Hello, Getting a weird issue with 1 of my sonoff devices. All sonoff devices were flashed with tasmota 9.2.0 but there is an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Both are Tuya devices without quirk.
@TheJulianJES sorry to ping you directly, but seems that the problem could be here:
OnOff channel and model TS0001, but no
power_on_state
attribute. I can’t think of how it could be fixedIf not having one quirk loaded its better getting one warning then its only matter of time we is getting one device support request for it then the user is missing the functionality. And we is knowing how of tuya is changing the endpoint / cluster config in there devices and need updating the quirks.
The last suggestion checking if quirk is loaded i thing is one good way and also writing one warning in the log that the device need one quirk for getting full functionality in ZHA.
Removing it for all TS000X i think its going in the wrong direction then have adding the GUI functionality and hope we is getting more nice one GUI for tuya devices in the future.