After a power outage I get “Missing Capability Listener” errors for my Roller Shade devices. Each shade (I have 17) is controlled by a Rollease Acmeda motor.
I use a RA-Pulse2 Hub to control the shade motors, and the hub is added to my Homey Pro via the HomeKit Controller app (developed by @Martin_Verbeek). Each shade is then added as a unique device.
Once the power outage has been fixed the Homey Pro, Pulse2 Hub and shade motors restart simultaneously. Once everything is powered back on I can control the shades through the Pulse2 app, indicating that the Pulse2 hub is functioning correctly to control the shade motors. However, if I try to control the shades via the device card in Homey I get a “Missing Capability Listener” error, with the additional info for the error dependant on the action I try to execute, e.g. set open % or close. I also get the same error type when a flow tries to execute an action on a roller shade.
I assume, but don’t know how to confirm, that during the simultaneous restart there is a “handshaking issue” between the Homey Pro and HomeKit app and the Rollease system (hub and motors).
I can fix the issue by removing and re-adding each device, but as there are 17 of them, and literally dozens of advanced flows impacted, this is time consuming and not a viable workaround everytime there is a power outage. I live in a rural area and power outages are not infrequent, I have experienced three over the X-mas period.
I’m keen to find a way to identify the root cause of the issue and hopefully a set of quick steps I can take after a power outage that enables Homey to resume being able to control the devices without error.
Any help from the community on this issue is greatly appreciated.
It’s an improvement of my previous workaround, automating updates to impacted flows after a remove and re-add for each device, but doesn’t help identify the root cause of the error.
Very keen to understand why the issue is occurring.
I have had identical issue. No zwave device was working due to missing capablity listener. No restart/unplug/app restart helped. However I finally realized that all those unknown devices that are appearing, are paired devices, that have failed while pairing. They even respond to test frames, and are reachable, just unknown, even though they have been later added correctly. Lastest device (fibaro walli) was not correctly paired like five times, when I simply disconnected it from the power, and was able to finally remove it (the unknown device) in developers tools – suddently all my other zwave devices started to work fine. I wish I was able to remove unknown devices without testing if they are reachable or not
