Philio PST-02A

Tags: #<Tag:0x00007efed8759ad0>

Hi,

this is the configuration I am using (all nodes are PST02A).
If you have multiple sensors, you can use HABApp to change the values on all sensors (it’s the textual thing config example which I made for the philio) without having to click so many times.

+-------------------------------------------------------------------------------------------------------+
|                               Current configuration                                                   |
+-------------------------+-------------------+-------------------+------------------+------------------+
|        Parameter        | controller:node15 | controller:node17 | controller:node3 | controller:node5 |
+-------------------------+-------------------+-------------------+------------------+------------------+
| 2                       | -1                | -1                | -1               | -1               |
| 3                       | 80                | 80                | 80               | 80               |
| 4                       | 99                | 99                | 99               | 99               |
| 5                       | 8                 | 8                 | 8                | 8                |
| 6                       | 0                 | 0                 | 0                | 0                |
| 7                       | 20                | 20                | 20               | 20               |
| 8                       | 3                 | 3                 | 3                | 3                |
| 9                       | 0                 | 4                 | 4                | 4                |
| 10                      | 12                | 12                | 12               | 12               |
| 11                      | 12                | 12                | 12               | 12               |
| 12                      | 12                | 2                 | 12               | 4                |
| 13                      | 12                | 2                 | 12               | 4                |
| 20                      | 30                | 30                | 30               | 30               |
| 21                      | 0                 | 0                 | 0                | 0                |
| 22                      | 0                 | 0                 | 0                | 0                |
| Group1                  | ['controller']    | ['controller']    | ['controller']   | ['controller']   |
| Group2                  | []                | []                | []               | []               |
| binding_cmdrepollperiod | 1500              | 1500              | 1500             | 1500             |
| binding_pollperiod      | 86400             | 86400             | 86400            | 86400            |
| wakeup_interval         | 86400             | 86400             | 86400            | 86400            |
+-------------------------+-------------------+-------------------+------------------+------------------+

I thing the most import one is parameter 5 and 7.
And yes - the first wake up is always very annoying, but you can hit the small button under the plastic cover a couple of times or just leave the sensor sitting next to the controller for one day.
Once the initialization is complete it will work flawlessly.

1 Like

Same Config works for me like a charm.

1 Like

DIP switches one up one down ? (“normal mode”)

See log above: SENSOR_BINARY_REPORT is sent but unlike the other commands, there’s no channel action taken for this one.

DIP switches are set to normal mode, as per default.
As @Spaceman_Spiff wrote, parameter 7 is very important. Yours is set to 22, please change to 20 and see if the behaviour changes. Took me a couple of days to get mine working…

Tried multiple changes, 20 among them (my +2 is to send motion off, too, should not do harm)

A little off-topic but you may be interested in the upcoming Z-Wave database site changes.

Is it also a V0 report on your sensors ? My device is very old, and so probably is the firmware (V1.16).
I think it should be V2 according to the database.

There is also no binary_sensor channel on my device, is there any on yours ?

Then again, there’s no motion channel in that DB entry either ?

Quite confusing…

That is a test copy . Current link here.

I know. But they say the same, don’t they.

I have two devices with firmware 1.16 and they work, so yours have to work, too.

What really irritates me is that you correctly receive the sensory binary report, but the channel does not get updated.

This is the entry from the node.xml in, do you have it, too?

            <commandClass>COMMAND_CLASS_SENSOR_BINARY</commandClass>
            <COMMAND__CLASS__SENSOR__BINARY>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <isGetSupported>true</isGetSupported>
              <types>
                <binarySensorType>TAMPER</binarySensorType>
                <binarySensorType>MOTION</binarySensorType>
                <binarySensorType>DOORWINDOW</binarySensorType>
              </types>
            </COMMAND__CLASS__SENSOR__BINARY>

I get the V2 report:

NODE 15: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
NODE 15: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
NODE 15: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
Processing Sensor Type 10
Sensor Type is DOORWINDOW
NODE 15: Sensor Binary report, type=Door/Window, value=0
NODE 15: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
NODE 15: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
NODE 15: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
NODE 15: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
NODE 15: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
NODE 15: Sensor Binary report, type=Motion, value=255
NODE 15: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
NODE 15: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
NODE 15: Updating channel state zwave:device:controller:node15:alarm_motion to ON [OnOffType]

Can your try to copy my config of node 15 to your sensor?

Not necessarily. Personally I seem to have some browser caching issues with the new site. Many f is are free to make changes, testing the system. the plan is to shut down the okld system before the final export / import.

My .xml … is GONE?

Thing display seems to be fine but habmin does not offer reinitialization, and on heal, all I get is

2020-07-30 14:51:35.941 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Configuration update received
2020-07-30 14:51:35.953 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Configuration update set action_heal to true (Boolean)
2020-07-30 14:51:35.955 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Starting heal on node!
2020-07-30 14:51:35.957 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 151: Can not start heal as initialisation is not complete (VERSION).

I’ll try to fake a .xml. Can you send me your full one, please ?

I have seen that sometimes discovery threads get hung after a long time.

I’ve just included a spare device (already had thrown that into the trashbin!) and it did not give me any binary_sensor either ;(

It does not generate any .xml either.

2020-07-30 15:03:41.078 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Configuration synchronised
2020-07-30 15:03:41.106 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising Thing Node...
2020-07-30 15:03:41.108 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:sensor_door for OpenClosedType
2020-07-30 15:03:41.110 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:sensor_door for OpenClosedType
2020-07-30 15:03:41.112 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:alarm_motion for OnOffType
2020-07-30 15:03:41.114 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:alarm_motion for OnOffType
2020-07-30 15:03:41.116 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:alarm_tamper for OnOffType
2020-07-30 15:03:41.118 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:alarm_tamper for OnOffType
2020-07-30 15:03:41.120 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:sensor_luminance for DecimalType
2020-07-30 15:03:41.121 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:sensor_luminance for DecimalType
2020-07-30 15:03:41.123 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:sensor_luminance for DecimalType
2020-07-30 15:03:41.126 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:sensor_temperature for QuantityType
2020-07-30 15:03:41.127 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:sensor_temperature for QuantityType
2020-07-30 15:03:41.129 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:sensor_temperature for QuantityType
2020-07-30 15:03:41.131 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:alarm_access for OnOffType
2020-07-30 15:03:41.133 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:alarm_access for OnOffType
2020-07-30 15:03:41.136 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:alarm_burglar for OnOffType
2020-07-30 15:03:41.137 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:alarm_burglar for OnOffType
2020-07-30 15:03:41.140 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising cmd channel zwave:device:ddd23e6c:node21:battery-level for PercentType
2020-07-30 15:03:41.141 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Initialising state channel zwave:device:ddd23e6c:node21:battery-level for PercentType
2020-07-30 15:03:41.143 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Polling initialised at 1800 seconds - start in 1326600 milliseconds.
2020-07-30 15:03:41.145 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Device initialisation complete.

Again no xml - strange. Maybe restart openhab?

Before you throw em away you can always send them to me! :wink:

Restarted zwave bundle but that resulted in queue full, restart ongoing.
At least it said to initialize from the fake XML and I caught

2020-07-30 15:20:58.666 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Initialising Thing Node...
2020-07-30 15:20:58.668 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Initialising cmd channel zwave:device:ddd23e6c:node151:sensor_door for OpenClosedType
2020-07-30 15:20:58.671 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Initialising state channel zwave:device:ddd23e6c:node151:sensor_door for OpenClosedType

this time.

With the fake XML, I’m now getting closer:

2020-07-30 16:12:09.388 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 151: Application Command Request (ALIVE:REQUEST_NIF)
2020-07-30 16:12:09.389 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 151: Decapsulating COMMAND_CLASS_MULTI_CMD
2020-07-30 16:12:09.390 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 151: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-07-30 16:12:09.391 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 151: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
2020-07-30 16:12:09.392 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 151: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2020-07-30 16:12:09.395 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 151: Sensor Binary report, type=Motion, value=0
2020-07-30 16:12:09.396 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-07-30 16:12:09.397 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2020-07-30 16:12:09.398 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 151: Updating channel state zwave:device:ddd23e6c:node151:alarm_motion to OFF [OnOffType]
2020-07-30 16:12:09.400 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 151: Commands processed 1.

does it work?

PIR, yes. Reed sensor, no.
I have seen a couple of messages to trigger the sensor_door channel, but it’s pretty unreliable und not reproducible.

Is this an initialization problem (messages arrive and don’t trigger the channel) or does the sensor not send the message? If it is the latter: do you have the magnet properly aligned with the lower part of the sensor?