Cover does not accept commands from HA (only one-way communication) #32
Description
Since running 0.4.1 (0.4.3 currently) of duoFERN, one of my covers started to have issues. Immediately after updating duoFERN, it was not closed automatically (using an automation firing cover.close_cover to a group of all covers).
The last days it worked, I'd say, unremarkable reliable.
Now I can not control it anymore (at all) from HA, entity state stays in "moving", potentially waiting for the device to perform/respond. Steps:
- Not a single command (open, close, set position) from HA is performed by the cover.
- If I control it locally, the status is updated in HA a few seconds later. So cover --> duoFERN --> HA is fine, not the other way.
- I ran
service: duofern.sync_devicesand surprisingly got two new entites where I have absolutely no idea to which devices they might belong. I suspected maybe the not working cover would be one of them, but that's not the case. Any idea? I think I'll just disable those two as they seem to be not related to this issue at all. Side-story, but wondering anyway.
- I ran
service: duofern.dump_device_statewhich gave (only relevant deviceXXXXXX):
Logger: custom_components.duofern
Source: custom_components/duofern/__init__.py:99
Integration: Duofern control (documentation, issues)
First occurred: 14:52:12 (1 occurrences)
Last logged: 14:52:12
{'by_code': {'XXXXXX': {'name': 'XXXXXX', 'channels': {None}, 'version': '15', 'ventilatingPosition': 30, 'ventilatingMode': 'off', 'sunPosition': 65, 'sunMode': 'off', 'timeAutomatic': 'off', 'sunAutomatic': 'off', 'dawnAutomatic': 'off', 'duskAutomatic': 'off', 'manualMode': 'on', 'position': 5, 'state': 5, 'moving': 'up'},
- I enabled debug logging for duoFERN, only for few minutes. Within all that mess/masses of messages I could not spot anything surprising. Filtered for XXXXXX only:
(had to split this log - see next comment(s) - as GitHub was complaining...)
Note I sent few moving commands (open, close, set_position) to the cover during that time. I guess/hope usually there's not that much communication going on in the back.
Any idea what happened here? Really strange, to sum up:
- (states) device --> duoFERN --> HA ✔
- (commands) HA --> duoFERN --> device ❌