Philio 4-in-1 sensor (PST02-A) not working with new Zwave-JS integration

Hi there,

I recently decided to swithc from Domoticz to HA, running the latest HA in Docker container. In addition I have a Zwave Plus USB controller, and decided to install the new Zwave-JS integration (also in docker) to control my Zwave devices.

One of these Zwave devices is the Philio 4-in-1 multisensor, however it does not seem to work properly with HA/Zwave-JS (while it did with Domoticz). It is probably related to parameter 7, which is by default configured to 4 and configures the sensor so that reports are being send in a Notification Report format. See attached logging. While using this setting, no door open/close events are detected/logged.

While configuring this parameter to 22, it will make sure binary reports are being send and the door open/close event is indeed logged (see logging). However, the sensor in HA is not being updated and I don’t see any changes in the entities for this device related to the door open/close. I do see other entities, like temperature, being provided and updated in HA.

I assume this has something to do with either the new Zwave-JS integration, HA itself, or maybe both. Would you be able to help with this? Thank you.

Edit: I could not add attachments, so here is a snippet of the logs:
Notification Report:

Subscribed to Z-Wave JS Log Messages...
2021-08-10T19:48:00.762Z SERIAL « 0x010b0004000603800364c600d4                                        (13 bytes)
2021-08-10T19:48:00.767Z CNTRLR   [Node 006] [~] [Battery] level: 100 => 100                        [Endpoint 0]
2021-08-10T19:48:00.777Z CNTRLR   [Node 006] [~] [Battery] isLow: false => false                    [Endpoint 0]
2021-08-10T19:48:00.785Z SERIAL » [ACK]                                                                   (0x06)
2021-08-10T19:48:00.794Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[BatteryCCReport]
                                      level:  100
                                      is low: false
2021-08-10T19:48:00.804Z SERIAL « 0x010d00040006053105030103c60006                                    (15 bytes)
2021-08-10T19:48:00.809Z CNTRLR   [Node 006] [Multilevel Sensor] Illuminance: metadata updated      [Endpoint 0]
2021-08-10T19:48:00.817Z CNTRLR   [Node 006] [~] [Multilevel Sensor] Illuminance: 2 => 3            [Endpoint 0]
2021-08-10T19:48:00.821Z SERIAL » [ACK]                                                                   (0x06)
2021-08-10T19:48:00.826Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[MultilevelSensorCCReport]
                                      type:  Illuminance
                                      scale: Percentage value
                                      value: 3

Binary Sensor/Report:

`Subscribed to Z-Wave JS Log Messages...
Log Level changed to: Debug
2021-08-10T18:37:48.010Z SERIAL « 0x010b0004000603800364c700d5                                        (13 bytes)
2021-08-10T18:37:48.021Z CNTRLR   [Node 006] [~] [Battery] level: 100 => 100                        [Endpoint 0]
2021-08-10T18:37:48.030Z CNTRLR   [Node 006] [~] [Battery] isLow: false => false                    [Endpoint 0]
2021-08-10T18:37:48.039Z SERIAL » [ACK]                                                                   (0x06)
2021-08-10T18:37:48.059Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[BatteryCCReport]
                                      level:  100
                                      is low: false
2021-08-10T18:37:48.067Z SERIAL « 0x010c00040006043003ff0ac700f4                                      (14 bytes)
2021-08-10T18:37:48.071Z CNTRLR   [Node 006] [Binary Sensor] Door/Window: metadata updated          [Endpoint 0]
2021-08-10T18:37:48.078Z CNTRLR   [Node 006] [~] [Binary Sensor] Door/Window: false => true         [Endpoint 0]
2021-08-10T18:37:48.083Z SERIAL » [ACK]                                                                   (0x06)
2021-08-10T18:37:48.089Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Door/Window
                                      value: true`

Regards,
Rolf

There is no Notification report in your first set of logs.

If you enable binary reports, there should be a disabled binary_sensor that you now need to enable. It is disabled by default in favor of the notification reports.

Ah, I knew this device sounded familiar. Philio - PST02A - needs compat flag to treat `unknown` Notification as `idle` · Issue #2674 · zwave-js/node-zwave-js · GitHub

Even with Notification reports it never sends an “Idle” value, so the motion sensor would appear stuck on. So you do want to use the disabled binary_sensor entities instead, after updating the config parameters.

I also saw no Notification Report in the first set of logs, thats I assume because Zwave-Js is not receiving/parsing them properly, because I did open/close the door.

In addition I have enabled the binary sensor devices for this device, but there is no status change or logbook entry in HA, so the entity does not get updated properly. See below my enabled entities:

For example this door change event I didn’t see any status change.

2021-08-13T19:18:41.247Z SERIAL « 0x010c00040006043003000ac1000d                                      (14 bytes)
2021-08-13T19:18:41.250Z CNTRLR   [Node 006] [Binary Sensor] Door/Window: metadata updated          [Endpoint 0]
2021-08-13T19:18:41.258Z CNTRLR   [Node 006] [~] [Binary Sensor] Door/Window: true => false         [Endpoint 0]
2021-08-13T19:18:41.263Z SERIAL » [ACK]                                                                   (0x06)
2021-08-13T19:18:41.270Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[BinarySensorCCReport]
                                      type:  Door/Window
                                      value: false

Update, I did (finally) found the correct device which gets updated: binary_sensor.slim_multi_sensor_pir_door_temperature_illumination_door_window

Thank you! Although it is still weird that the Notification Reports were not displayed in the Zwave-JS logging (and unfortunately the Notification Report is not supported).

Hello,

I’m the one who opened the issue on Github and I’m the one who is deseperate to get this sensor working…

Could you please confirm that for parameter 7 you are using 20 or 22?

You have no strange behavior of the binary sensor in that case?
As mentioned on the Github issue, mine keeps triggering then, even if I can’t get its status in HA, it is not usable because of this…
127901787-64cc22a0-6309-469c-827e-f7fbab5cdb33
Thanks for your feedback,

Regards,

HI,

since I moved over some motion sensors from devolo HC towards home assistant I had also trouble to get them working.
I changed the paramter 7 from 4 (default) to 6 (enable sending motion off report), see https://manual.zwave.eu/backend/make.php?lang=en&sku=PHI_PST02-1B&cert=ZC10-14080017

Now it seems to work

Br, Oliver

1 Like

Hi there :grinning:

I have the same buttons i bought

I`m not so experienced with HA jet, could anybody help with the code i need to get the Philio PSR04-1 working please

I like to use the center button function as on/of and rotation for the dimming part

Thx in advance