Closed r00tat closed 4 years ago
Hi Paul,
Kindly sorry for my late answer. I am very happy about you are using my Elero lib. At first, I have no idea why it happens. My the Home Assistant has been running on a Raspberry Pi3B in a Docker container on USB SSD without any problem for one year. Please give me a time and I will get back soon.
Thanks, Istvan
It seems it's somehow tied to when the stick is connected. If it is connected pre boot it will show up in the logs.
As a recommendation I would say it should be connected before it boots or at least the container is started.
I think we can close this issue.
Hi Istvan,
great work!
I had some troubles finding the correct id of the transmitter stick and I'm not a 100% sure, what went wrong.
TLDR: hass.io's packaging of Home Assistant into a container might break the discovery.
The logs did not show any information about the elero stick, so I did some debugging.
The discovery did not display any Elero sticks, so I wrote a small script (from your sources) to discover the usb stick.
It worked in the first place, but now I got:
I'm not sure why it worked in the first place but now it didn't.
I'm using Home Assistant with hass.io on a Raspberry Pi4. To execute the code I've used the Cloud9 IDE, running in unprotected mode.
After a restart of Cloud9 I was able to get the the ID of the stick:
So I think the cause of the issue is that Home Assistant is running in a Docker container. I don't know if there is an easy workaround for that issue.