RFXcom motion sensor CT60M and changing packetid's

Configuration
1

running: HA 0.101.3 on a RBPi3+
RFXtrx433XL via USB connected

I can use some help on this one.
I have several PIR’s (sonoff CT60M’s and no-name window/door sensors) in my house.
These used to work perfectly, but all of a sudden they stopped working. HA does not see the enities anymore. I can see the debug/log messages in the logging but I’m unable to add the sensors back to HA because the packet_id’s keep changing.

When I trigger the motion sensor this is being displayed in the log viewer:

2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130058e9ae3e019d50)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Device_id: e9ae3e device_update. Command: Unknown command (0xe9ae3e)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130059e9ae3e019e60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 0913005ae9ae3e019d60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 0913005be9ae3e019e60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 0913005ce9ae3e019d60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 0913005de9ae3e019c60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 0913005ee9ae3e019b60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 0913005fe9ae3e019d60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130060e9ae3e019f60)
2019-11-15 18:49:11 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130061e9ae3e019c60)
2019-11-15 18:49:12 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130062e9ae3e019d60)
2019-11-15 18:49:12 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Device_id: e9ae3e device_update. Command: Unknown command (0xe9ae3e)
2019-11-15 18:49:12 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130063e9ae3e019e60)
2019-11-15 18:49:12 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130064e9ae3e019c60)
2019-11-15 18:49:12 DEBUG (Thread-2) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: e9ae3e Class: LightingDevice Sub: 0, Pkt_id: 09130065e9ae3e019d60)

As you can see the packet_id is in the format:
09130059e9ae3e019e60
where 091300 is the type (Lightning4) + subtype (PT2262) and e9ae3e is the device_id.

I also have several KaKu power switches in my house and these still work like a charm.

So my question is, how can I add these PIR’s and window/door sensors permanently to HA?

my configuration.yaml looks like this at the moment:

# RFXCOM BRIDGE INTEGRATION
rfxtrx:
  device: /dev/ttyUSB1
  debug: true
binary_sensor:
    0913001be9ae3e019d60:
      name: ms_2_beweging
      device_class: motion
      off_delay:
        seconds: 5
      data_bits: 4
      command_on: 0xe

I already did some reading here but I just cannot figure out how to add the correct sensor to my configuration.

2

The packet content will change but the sensor ID (cmd1,cmd2,cmd3) should be the same.
The structure of a Lighting4 packet:

struct { BYTE packetlength; BYTE packettype; BYTE subtype; BYTE seqnbr; BYTE cmd1; BYTE cmd2; BYTE cmd3; BYTE pulseHigh; BYTE pulseLow; BYTE filler : 4; BYTE rssi : 4; } LIGHTING4;

cmd1, cmd2, cmd3 is the sensor ID.
The seqnbr, pulseHigh, pulseLow and rssi can change for each packet received from this sensor.

3

thank you b_weijenberg, this will definitely help in the future when trying to decode packets.
For some strange reason my motion/door sensors came up again after about a week. So for now this problem is resolved.