My HA is not pickingup my rfxtrx sensors anymore after some time.
Switches and other devices still work. After reboot the sensors work again for some time and than stop being pickedup agian.
Running HA 0.53.1 on Raspberry PI Ubuntu Mate.
Does anybody know what can cause thuis issue?
hi @jpostema,
Not sure if related to RFXTRX only seeing one switch
but I’ll ask you the same anyway:
Have you tried to set your rfx in debug mode to see whether you receive anything at all?
logger:
default: error
logs:
homeassistant.components.rfxtrx: debug
Thanx for the tip I will try debug and see if I can see more.
I used the logging you said and indeed now I see an error. But I also started HA in a teminal window instead as a service in unbuntu the terminal window gave even more logging.
The logging from the logger was:
2017-09-21 18:12:17 DEBUG (Thread-22) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 280e Class: RFXtrxDevice Sub: 7, Pkt_id: 0a520700280e00de370179)
2017-09-21 18:12:28 DEBUG (Thread-22) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 390e Class: RFXtrxDevice Sub: 7, Pkt_id: 0a520700390e00e0370169)
2017-09-21 18:12:31 DEBUG (Thread-22) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 081489a1 Class: LightingDevice Sub: 0, Pkt_id: 0b1100000081489a01040f50)
2017-09-21 18:12:31 INFO (Thread-22) [homeassistant.components.rfxtrx] rfxtrx: found possible device 081489a1 for 0d69b1e5 with the following configuration:
data_bits=28
command_on=0xd69b1e5
command_off=0x81489a1
2017-09-21 19:25:58 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
File “/usr/lib/python3.5/asyncio/selector_events.py”, line 662, in _read_ready
data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
The logging from the terminal window is:
Recv: 0x0a 0x52 0x07 0x00 0x39 0x0e 0x00 0xe0 0x37 0x01 0x69
2017-09-21 18:12:28 DEBUG (Thread-22) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 390e Class: RFXtrxDevice Sub: 7, Pkt_id: 0a520700390e00e0370169)
Recv: 0x0b 0x11 0x00 0x00 0x00 0x81 0x48 0x9a 0x01 0x04 0x0f 0x50
2017-09-21 18:12:31 DEBUG (Thread-22) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 081489a1 Class: LightingDevice Sub: 0, Pkt_id: 0b1100000081489a01040f50)
2017-09-21 18:12:31 INFO (Thread-22) [homeassistant.components.rfxtrx] rfxtrx: found possible device 081489a1 for 0d69b1e5 with the following configuration:
data_bits=28
command_on=0xd69b1e5
command_off=0x81489a1
Exception in thread Thread-22:
Traceback (most recent call last):
File “/usr/lib/python3.5/threading.py”, line 914, in _bootstrap_inner
self.run()
File “/usr/lib/python3.5/threading.py”, line 862, in run
self._target(*self._args, **self._kwargs)
File “/srv/homeassistant/lib/python3.5/site-packages/RFXtrx/init.py”, line 710, in _connect
self.event_callback(event)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/rfxtrx.py”, line 167, in handle_receive
subscriber(event)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/binary_sensor/rfxtrx.py”, line 92, in binary_sensor_update
poss_id = slugify(poss_dev.event.device.id_string.lower())
AttributeError: ‘RfxtrxLight’ object has no attribute ‘event’
2017-09-21 19:25:58 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
File “/usr/lib/python3.5/asyncio/selector_events.py”, line 662, in _read_ready
data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x01 0x01 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x02 0x01 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x05 0x01 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x05 0x00 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x01 0x00 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x02 0x00 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x06 0x01 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x06 0x00 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x06 0x01 0x00 0x00
Send: 0x0b 0x11 0x00 0x00 0x00 0xd6 0x9b 0x1e 0x06 0x00 0x00 0x00
I have no idea how to fix this. Looks like the Rfxtrx is finding a new device and than the thread 22 stops working that why I am not recieving any sensors anymore after this error. All devices that I have are already configured in the HA system so I don’t know what the problem is with the possible device.
I restarted HA after the error again in a terminal window and again after hours working fine the same error occured.
Can somebody please help with this issue?
I found something that can help solving this problem.
I have a small COCO/KAKU remote AKCT-510 the moment I press the remote the following error occures:
Exception in thread Thread-21:
Traceback (most recent call last):
File “/usr/lib/python3.5/threading.py”, line 914, in _bootstrap_inner
self.run()
File “/usr/lib/python3.5/threading.py”, line 862, in run
self._target(*self._args, **self._kwargs)
File “/srv/homeassistant/lib/python3.5/site-packages/RFXtrx/init.py”, line 710, in _connect
self.event_callback(event)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/rfxtrx.py”, line 167, in handle_receive
subscriber(event)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/binary_sensor/rfxtrx.py”, line 92, in binary_sensor_update
poss_id = slugify(poss_dev.event.device.id_string.lower())
AttributeError: ‘RfxtrxLight’ object has no attribute ‘event’
If the remote AKCT-510 is not supported it is fine but if it breaks my HA is not fine
I hope somebody can help me fixing this.
@Danielhiversen Do you know thefix for this issue?
Thanx in advance!
So far, for me it seems like the issue is only triggered when automatic_add is activated on RFXtrx devices, I have disabled it for all, and so far it is working.