Hi
Anyone else starting to have issues with Nexa door sensors in the later versions of HASS?
Suddenly all of my sensors stopped reporting status.
It was working before but I can´t say exactly when it stopped 
I´m using the rfxcom component for 433mhz
EDIT:
After enabling debug it seems that if has some problems to fetch the “off” cmd?
17-04-09 14:17:45 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0101 Class: RFXtrxDevice Sub: 8, Pkt_id: 0a52080e010100cc2f$
17-04-09 14:18:19 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0fc174a10 Class: LightingDevice Sub: 0, Pkt_id: 0b11000f00f$
17-04-09 14:18:19 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Device_id: 0fc174a10 device_update. Command: On
17-04-09 14:18:22 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0fc174a10 Class: LightingDevice Sub: 0, Pkt_id: 0b11001000f$
17-04-09 14:18:22 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Device_id: 0fc174a10 device_update. Command: On
17-04-09 14:18:25 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-09 14:18:30 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0fc174a10 Class: LightingDevice Sub: 0, Pkt_id: 0b11001100f$
17-04-09 14:18:30 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Device_id: 0fc174a10 device_update. Command: On
17-04-09 14:18:32 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0fc174a10 Class: LightingDevice Sub: 0, Pkt_id: 0b11001200f$
17-04-09 14:18:32 DEBUG (Thread-14) [homeassistant.components.rfxtrx] Device_id: 0fc174a10 device_update. Command: Off
On is received every time but not off