You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add this repository as a custom repository in HACS
Install the MyHOME integration
Restart Home Assistant
Manual installation
Download myhome.zip from the assets below
Extract it into custom_components/myhome/ in your Home Assistant
configuration directory (the archive holds the integration's files
themselves, with no top-level folder)
Restart Home Assistant
Changelog
Fixed
A command written into a session the gateway had quietly closed is sent again. A MyHOMEServer1 drops a command session that has had nothing to send for about half a minute, without telling anyone; the next write into that socket succeeds locally while the frame never reaches the bus, and only the acknowledgement that never comes says so. Since 0.4.3 such a frame was neither sent again nor treated as lost — it was reported to the caller as delivered — so a light stayed off while Home Assistant showed it switching, and a shutter that never moved ran a phantom estimate to 35 %. Every transport failure is retried on a fresh session again, whatever the write itself returned, and a command counts as delivered only once the gateway has answered it (a refusal included), timed from the write that was answered. A command no attempt was answered for is dropped, so a cover cancels its estimate instead of timing a run that never started. The retry can put a second copy of a command on the bus, which for these commands changes nothing — on twice is on, up twice is up — and is the cheaper mistake by a wide margin.
An idle command session is given back before the gateway takes it. Home Assistant held it for 60 seconds against the gateway's ~30, so in a quiet house the connection was usually already dead when the next command was written into it. It is now closed after 20 seconds of silence and re-opened on demand.