Closed shortbloke closed 1 year ago
Adding some simple logging before sock.bind((self._binding[0], self._binding[1]))
I can see that update method is called for each sync worker (0 to 16 in the log above). Each attempt to bind to the same address and port.
So I suspect the first SyncWorker will succeed and bind to the port, and rest will always fail as in use.
The previous version of this component would also have called multiple times, so I don't why this is now occurring, unless this regression has been introduced by the multicast support, or some change to HA that is now calling update more than before? I don't know...
Reverting sensor.py to a version before the multicast changes, and the unable to bind error is still present, so seems likely it is caused by a HA change.
Seeing identical issues as well, appears the HA update was the cause as I downgraded to 2023.4.6 as per https://community.home-assistant.io/t/owl-intuition-pv-home-assistant/18157/99 and was then able to view the output again.
Reverting to 2023.4.6 shows that the update method is still called by each SyncWorker. I also noticed that startup time has improved significantly on 2023.5.2, on my Pi4 it's < 10 seconds now, whereas when I reverted back to 23.4.6 it was > 100 seconds.
Hi there, I'm getting the exact same error and owl no longer working. I've checked I am the website for owl everything there working as expected and the data push address matches and it's in the config but HA just not seeing the data at all.
I've tried downgrading the core to the same as mentioned above and but that hasn't helped although it did sort a different issue.
Is there anything you can advise to try?
Many thanks Steven
@muzzy00uk Tryt the change in PR linked to this issue. I believe it will fix it for you.
Updating to the latest HA version and Owl custom component version I'm now seeing an error being logged multiple times every 30 seconds.
Versions:
Section from configuration.yaml:
HomeAssistant.log