Closed u20p17 closed 1 year ago
Hi @u20p17
please help us to understand this issue and share your environment where the HA and the Elero stick run.
Thanks,
Hi @W00D00, I am running UnRaid on an Intel Nuc, where HomeAssistant OS is running in a VM. Up to HA2023.4.x everything was working flawlessly, since HA2023.5.x I get lot of errors (listed above) in the log and sometimes the roller shutters are working, sometimes not ( e.g. i have an automation to open the rollershutters in the morning --> since 2023.5.x some open in the morning, some not... (which is not opening is random, so not everytime the same roller shutter...)
If you need more infos don't hesitate to ask! Thanks for your commitment!
BR
EDIT: What I forgot to say: The Elero stick is connected to the Intel Nuc and passed-through to the HA VM...
Hi, I have the same problem since 2023.5. I'm running HA on a Nuc with Proxmox on a VM. Here some examples:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: homeassistant.helpers.entity Source: custom_components/elero/init.py:542 Integration: Elero (documentation) First occurred: 19:00:17 (1 occurrences) Last logged: 19:00:17
Update for cover.terrassenbeleuchtung_dach fails Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 554, in async_update_ha_state await self.async_device_update() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 784, in async_device_update await coro File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/elero/cover.py", line 257, in update self._transmitter.info(self._channel) File "/config/custom_components/elero/init.py", line 347, in info self.process_command( File "/config/custom_components/elero/init.py", line 485, in process_command resp = self.__parse_response(ser_resp, channel) File "/config/custom_components/elero/init.py", line 542, in parse_response response["ch_l"] = self.get_lower_channel_bits(ser_resp[4]) IndexError: index out of range
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.elero Source: custom_components/elero/init.py:347 Integration: Elero (documentation) First occurred: 19:00:15 (4 occurrences) Last logged: 19:00:15
The channel is not learned 'A506Q9S7' on the transmitter: '4'. The channel is not learned 'A506Q9S7' on the transmitter: '6'. The channel is not learned 'A506Q9S7' on the transmitter: '8'. The channel is not learned 'A506Q9S7' on the transmitter: '10'.
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.elero.cover Source: custom_components/elero/cover.py:257 Integration: Elero (documentation) First occurred: 19:00:15 (1 occurrences) Last logged: 19:00:15
Transmitter: 'A506Q9S7' ch: '2' error response: 'blocking'.
I can confirm that I also have that issue on HA 2023.5.2
version | core-2023.5.2 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.10.11 |
os_name | Linux |
os_version | 6.1.21-v8 |
arch | aarch64 |
timezone | Europe/Berlin |
config_dir | /config |
It seems that with HA2023.5 there will be some issues with the SyncWorker threads. It should easily be fixed by adding a threading lock around the serial communication of a single command (write & read). I've already created a pull request #43 for this issue.
Hello, since updating to the latest HA version I see the following errors in the log (which I didn't had before):
Anybody else? @W00D00 : How can we fix the issues?
Thanks!