Core: RFXTRX stops receiving signals

[goldbowler]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.57.2

Python release (python3 --version):
3.5.2

Component/platform:
RFXTRX

Description of problem:
Nothing happens then receiving signals from switches or motion detectors
I posted the log in additional info.
The log stops receiving signals after the last line. The device is sending 0004bc27 but sometimes hass receives 0084bc27 instead. After that hass receives nothing from any 433MHz device. Sending still works.
The device is added as a binary sensor.
Expected:
The opposite

Problem-relevant configuration.yaml entries and steps to reproduce:

binary_sensor:
  platform: rfxtrx
  automatic_add: False
  devices:
    0a1411090004bc1b000030:
      name: motion_cellar
      device_class: motion

1. 
   
   
   2.
   
3.

Traceback (if applicable):

Additional info:
2017-11-08 15:26:42 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Device_id: 0004bc27 device_update. Command: On
2017-11-08 15:26:42 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Device_id: 0004bc27 device_update. Command: On
2017-11-08 15:26:56 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0004bc27 Class: LightingDevice Sub: 17, Pkt_id: 0a1411030004bc1b000070)
2017-11-08 15:26:56 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Device_id: 0004bc27 device_update. Command: Off
2017-11-08 15:26:56 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Device_id: 0004bc27 device_update. Command: Off
2017-11-08 15:27:03 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0004bc27 Class: LightingDevice Sub: 17, Pkt_id: 0a1411040004bc1b010070)
2017-11-08 15:27:03 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Device_id: 0004bc27 device_update. Command: On
2017-11-08 15:27:03 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Device_id: 0004bc27 device_update. Command: On
2017-11-08 15:27:16 DEBUG (Thread-24) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0084bc27 Class: LightingDevice Sub: 17, Pkt_id: 0a1411050084bc1b000070)

[isabellaalstrom]

Also having problems with this.

[turbokongen]

I also can confirm this. Last sensor signal seems random.
1: 2017-11-08 17:22:11 DEBUG (Thread-23) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 00070b18 Class: LightingDevice Sub: 17, Pkt_id: 0a1411e900070b12010060)
2: 2017-11-08 01:13:55 DEBUG (Thread-23) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: c80418 Class: LightingDevice Sub: 0, Pkt_id: 0913003ac8041800f130)
Absolutely no errors are printed, just stop receiving signals.
Only restart fixes it.
None automatic_add: true in my config.

[remkolodder]

I have the same with sensors. They stop responding after some time, they appear again after restarting hass, but then fail.

[Danielhiversen]

I am not sure how we can debug this, since there is no error message.

Do you all use the binary_sensor?
There is a bug in the binary sensor that will be fixed with this pr: https://github.com/home-assistant/home-assistant/pull/10203

[goldbowler]

Last night i removed all my motionsensors from the config. But still leave them running.
On motion they show up in the log after restart. But after a while everything comming to the RFXTRX dont show in the hass log. I tried with the rfxmgr tool and there everything runs fine. Now a have tested to remove the battery from my motionsensors since taking them of the config doesn't seem to help. And yes im using all my motionsensors as binary_sensor.

[goldbowler]

Mabye it helps if i say that everything was working in version 0.54.
I upgraded from 0.54 to 0.57.2 and after that the issue started.

[turbokongen]

I can narrow it further down. It happened somewhere after 0.56 release. I always run dev branch, but some Frontend issues forced me to run 0.56 until 0.57.1 was released.

[jaboka]

Same problem here

[isabellaalstrom]

@Danielhiversen It might be that it's the binary sensor that's the main problem! I just realized that my switches work fine but none of the binary sensors. I can try to change some of them to switches to see if they work then, in that case it's almost certainly that same problem.
Edit: No sorry, I just realized one of the none working enitites actually is a switch already. :/

[isabellaalstrom]

It maybe seems like it's only the entities that sends information that becomes unresponsive. Like motion sensors, buttons, temperature sensors etc. The light switches I have is working fine, but they are receiving only.
What can we do to help debug this when nothing is showing in the logs? Can I in some way see if the pr with binary_sensors is helping by some means?

[rbravenboer]

I just realized I probably have the same issue. I just created the following topic: https://community.home-assistant.io/t/how-to-use-kerui-p829-with-ha/32095/1
And that sounds a lot like this issue. Also motion sensor as a binary sensor, rxftrx and no logging.

If I need to test anything please let me know. I'm running hass.io

Regards,
Robin

[erikjoens]

I can confirm what @turbokongen wrote. I had the same problem after upgrading to the latest 0.57.2, all my entities that send signals to the RfxTrx stops working after a few minutes. Works another few minutes after a restart of home assistant. Switches and lights seems to work fine all the time, i.e. entities that only receive signals from RfxTrx.

I tried downgrading to 0.56.2 again, and everything now seems to be working normal again. So something has happened between 0.56.2 and 0.57.2 that partially breaks RfxTrx.

(I run home assistant in a python virtual environment and downgraded by running pip3 install homeassistant==0.56.2)

Related pull requests:

• #10128
• #10152

[isabellaalstrom]

I also tried downgrading to 0.56.2, and it's now been 10 hours since latest reboot with no issues.
I downgraded with hassctl, I run latest Hassbian.

[turbokongen]

So I reverted only 1 commit: e819678 and the issue is gone. Also I noticed that the last packet id received was 13. So this gets processed even if automatic_add: false is set.

[Oreron]

Reverted to HA 0.55 and it seems to work fine now.

[isabellaalstrom]

0.56.2 is still working great with regards to this. Sad to see that #10203 did not make it into this release. Anyone updated to .58 and noticed something getting better?

[jaboka]

Yes, still the same problem in .58 (Docker)

[erikjoens]

Can't see any related fixes for this in the new 0.59 release :( anyone who tried upgrading yet?

[jaboka]

Same problem here after upgrade to 0.59. All RFX sensor stop working after a while.

[Danielhiversen]

https://github.com/home-assistant/home-assistant/pull/10203 is still not approved

[Webserve]

Same problem here. V0.59.2

[jmekroth]

Same issue still 0.59.2. Worked just fine before 0.59 with automatic_add: false . Any Solutions upcoming? Otherwhise i probably change gateway for the 433 protocol which would be really sad . I really like the rfxtrx controller

[Webserve]

I also tried to copy the dev scripts into production. The problem still exists after this.

Maby i'm doing something wrong.

[Danielhiversen]

@pvizeli
Do you know when you will finish https://github.com/home-assistant/home-assistant/pull/10501 ?

10203 would have fixed this issue

[jmekroth]

Feel bad for missing say thanks for all the great work you guys do for Hass and this component. You are kings ! Hope you get the solution soon, Everything with this component except binary sensors works perfectly for me

[jaboka]

Broken for months now. For the moment I run rfx binary sensor on Telldus Live to solve the problem until a fix is available. So good for now :)

[ypollart]

Hi everyone. I'm sorry for not being able to spend more time on the code at the moment. I do not know the hass platform enough to help in rewriting the rfxtrx component.

@pvizeli i, given that:

• the current RFXTRX binary sensor component is still broken in the current home-assistant release, and has been broken for weeks ;
• it looks like it will take some more weeks before the component can be refactored ;
• the PR #10203 (before you started modifying it) fixes the problem while it does not seem to do more harm.

Would you consider allowing the merge of PR#10203 )while continuing your refactoring work? Or should I create another PR that only fixes the binary sensor issue while not adding the "set decoded protocols" functionality to the platform?

Thanks!

[Danielhiversen]

@balloob / @pvizeli Could you comment on the questions from @ypollart ?
I think it is bad that the component has been broken for so long.

I think we should revert the "clean up" changes in #10203 and merge it

[jaboka]

Why is there no response?
An update that there is currently no time for this would have been enough so the users know ..

[Webserve]

Yes. Please respond. Now i cant use my rfxcom stuff.

[jmekroth]

Had been wonderful if you got the component to work again! nice to be able to use presence detection and remote as before. Thank you for all the work you all put down, hope you get a solution soon :)