Z-way binding & Aeotec Multisensor 6 - no PIR event

Tags: #<Tag:0x00007f7452564de8> #<Tag:0x00007f7452564c80>
  • Platform information:

    • Hardware: RPi4, RaZberry 2nd gen controller
    • OS: Raspbian Buster
    • Java Runtime Environment: OpenJDK (Zulu Embedded) v.1.8.0_152
    • openHAB version: Openhab2 2.4.0-1
  • Issue of the topic:
    I use the Z-way binding in Openhab2, which talks to my z-way-server and RaZberry communication stack.
    I have included the Aeotec Multisensor 6 (unsecurely).
    I used Openhabs “simple mode” when adding the Thing, which instantiates the PIR Item as a Switch.
    I can see the PIR link being enabled and turning ON during Openhab startup.
    I can also see the PIR event happening - both by the green light blinking on the device, and in the z-way-server.log; but nothing shows up in Openhab’s events.log.
    I am able to trigger a rule based on the PIR item being updated - which only happens once during boot.
    I have tried to re-include, restart servers of course, but Openhab does not react to the event.
    The device is USB powered.

So the problem is I cannot react to the event in Openhab and perform any logic based on the PIR firing

  • Please post configurations (if applicable):
    • Items configuration related to the issue
Switch		PIR_sensor_1	"Motion sensor"		<network>		{channel="zway:zwayDevice:SERVER_IP:47:sensorMotion-ZWayVDev_zway_47-0-48-1"}
  • Sitemap configuration related to the issue
  • Rules code related to the issue
rule "Handle PIR Events"
when
    Item PIR_sensor_1 received update
then
    GF_LivingDining_Light_2.sendCommand(100)
end
  • Services configuration related to the issue
  • If logs where generated please post these here using code fences:
    openhab2/events.log
2019-11-09 10:25:56.199 [.ItemChannelLinkAddedEvent] - Link 'zway_zwayDevice_192_168_1_80_47_sensorMotion_ZWayVDev_zway_47_0_48_1-zway:zwayDevice:192_168_1_80:47:sensorMotion-ZWayVDev_zway_47-0-48-1' has been added.
...
2019-11-09 10:26:04.926 [vent.ItemStateChangedEvent] - zway_zwayDevice_192_168_1_80_47_sensorMotion_ZWayVDev_zway_47_0_48_1 changed from NULL to ON

z-way-server.log excerpt:

[2019-11-09 10:15:50.050] [D] [zway] SETDATA devices.47.data.lastReceived = 0 (0x00000000)
[2019-11-09 10:15:50.050] [D] [zway] SETDATA devices.47.instances.0.commandClasses.48.data.1.level = True
[2019-11-09 10:15:50.050] [D] [zway] SETDATA devices.47.instances.0.commandClasses.48.data.1 = Empty
[2019-11-09 10:15:50.063] [I] [core] Notification: device-info (device-OnOff): {"dev":"PIR (#47)","l":"on","location":""}
[2019-11-09 10:15:50.491] [D] [zway] RECEIVED: ( 01 11 00 04 00 2F 09 71 05 00 00 00 FF 07 08 00 CA 00 82 )
[2019-11-09 10:15:50.492] [D] [zway] SENT ACK
[2019-11-09 10:15:50.492] [D] [zway] SETDATA devices.47.data.lastReceived = 0 (0x00000000)
[2019-11-09 10:15:50.492] [D] [zway] SETDATA devices.47.instances.0.commandClasses.113.data.7.eventParameters = byte[0]
[2019-11-09 10:15:50.492] [D] [zway]   ( zero-length buffer )
[2019-11-09 10:15:50.492] [D] [zway] SETDATA devices.47.instances.0.commandClasses.113.data.7.event = 8 (0x00000008)
[2019-11-09 10:15:50.494] [D] [zway] SETDATA devices.47.instances.0.commandClasses.113.data.7.eventString = "Motion detected, location unknown"
[2019-11-09 10:15:50.494] [D] [zway] SETDATA devices.47.instances.0.commandClasses.113.data.7.status = 255 (0x000000ff)
[2019-11-09 10:15:50.494] [D] [zway] SETDATA devices.47.instances.0.commandClasses.113.data.7 = Empty

Is there any reason you are using Z-Way instead if the Z-Wave binding?
I believe many people have that sensor working with the Z-Wave binding.

Because I use the z-way-server’s Node.js capabilities for more advanced logic.