search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.07k stars 29.73k forks source link

Motion Blinds not available on same LAN, possibly due to multicast issue? #49439

Closed saxopwn closed 3 years ago

saxopwn commented 3 years ago

The problem

Similar to this issue here, I'm having all entities show as unavailable due to timeout. The Motion Blinds gateway is on the same network as the HA instance (no VLANs at all) and I've toggled/untoggled mDNS, IGMP snooping, and opened the appropriate ports listed in the documentation with no luck. My router is a UniFi Dream Machine Pro and my AP is an ASUS router running in AP mode. The blinds work fine with Alexa but attempting to add them into Homebridge is equally unsuccessful.

What is version of Home Assistant Core has the issue?

2021.4.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Motion Blinds

Link to integration documentation on our website

https://www.home-assistant.io/integrations/motion_blinds/#troubleshooting

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: motionblinds.motion_blinds
Source: /usr/local/lib/python3.8/site-packages/motionblinds/motion_blinds.py:874
First occurred: 2:00:38 PM (120 occurrences)
Last logged: 2:57:13 PM

Timeout of 5.0 sec occurred on 5 attempts while waiting on multicast push from update request, communication between gateway and blind might be bad.

Additional information

No response

probot-home-assistant[bot] commented 3 years ago

motion_blinds documentation motion_blinds source (message by IssueLinks)

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.