Hello @pauli_anttila ,
I just received a cheap PIR sensor which works via the lighting4 protocol and I can confirm that it should not include the pulse-id in the device-id.
The strange thing is that the openHAB 1 binding includes the pulse id for output but not for input. And it will not work for input because it varies in a small range. However maybe some actors who run the Lighting4 protocol might require a proper value to be able to control them.
Could we also make it asymmetric in OH2?
A detected sensor is stored without pulse and if you want to add an output you can (optionally) add the pulse.
Note in OH1 my config looks like this:
Contact cheap_motion_sensor (gMyOpenHAB, gSyncToOH2) { rfxcom="<286169:Contact", expire="4s,CLOSED" }
Switch cheap_motion_sensor_2 (gMyOpenHAB, gSyncToOH2) { rfxcom="<286169:Command", expire="4s,OFF" }
Number cheap_motion_sensor_signal_level (gMyOpenHAB, gSyncToOH2) { rfxcom="<286169:SignalLevel" }
String cheap_motion_sensor_rawData (gMyOpenHAB, gSyncToOH2) { rfxcom="<286169:RawData" }