I am having some trouble with zigbee to HA to a z-wave socket automation working for a period of time then stopping working.
The automation is a simple z-wave device toggle state from a zigbee switch. It works fine for a period of time and then just stops working.
When I go into the HA configuration in Lovelace, manually trigger the automation, the automation then starts working perfectly again for a period time.
I am not sure what to do to troubleshoot why it stops, the Zigbee control is via a dedicated deCONZ server running on a Pi and the switch activation shows in the logs, but the automation doesn’t run.
In Lovelace, I open the menu configuration -> automations. Click on the i in the circle, the automation information opens.
In the bottom right of that dialogue is a trigger button. I click the trigger button. The automation then runs after being manually triggered.
After it has been triggered that way then the wall switch starts working again to trigger the automation.
There is no config change, just triggering the automation this way re-enables the automation.
The automation was created in the Lovelace interface and not as a manual yaml.
No worries. In the HA logs, the incoming deconz event shows and in decomz gui, the wall switch is seen triggered. I’ll need to re-enable debuging to capture the full details as I don’t have them saved.
The automation states output below.
last_triggered: '2019-11-23T11:30:09.892442+00:00'
id: '1574031213191'
friendly_name: Toggle Stair lights from bathroom
In the history, the automation shows “on” all the time, unless I’ve turned it off to test it.
It’s odd, the set up works, just randomly stops working after a few hours and then won’t run again until it’s triggered.
I thought it might be a RAM / Swapfile issue on the Pi and even removed the Zigbee Raspbee HAT from the HA Pi and installed a dedicated deCONZ server Pi to reduce the swapfile from 80% to 10%. This made things a bit better, but still hasn’t completely solved the issue
I had noticed that, the deconz exposed switch shows as a device, but only has the battery level entity under it. Is the entity_id essential for automation or is device_id ok?
Hmmm ! but it does have a device I’d (some long pseudo random generated string) inlue of any other explanation I’d assume this was the state machine reference to the entity which it hangs other stuff to
Device I’d, friendly name, domain, child attributes etc.