[SOLVED] Multisensor Aeon PST02-A motion detection not working correctly with OH2

Right SiHui , in fact I do have them in the customer mode - have I have been playing with the sensor for over a year now with OH1 - never any issues until now…

Thanks for your efforts. :slight_smile:

From what I see in the database config parameter 5 is free entry, so it should :grinning: work.

Last idea: did you reinitialize the device? Delete the thing, delete the xml, start discovery and then wake up the device manually, you should see recreating the node.xml file.

Good idea, I will reinitialize and see what happens. :slight_smile: Thanks!

I have tried initializing the sensor 4 times. Every time, the OH2 habmin still does not let me change the Operation mode (even to the preset value of 10) - displaying the Error 400 - bad request. What is interesting I have noticed the customer functions shows twice, and I also cannot change those settings either.

That looks like PaperUI, although it should provide the same functionality, I would try HABmin when dealing with zwave devices.

1 Like

Thanks a ton Sihui, going the HABmin route (silly me for calling paperui habmin) worked like a charm. I had no idea paperui is not recommended for z-wave. The issue is solved.

1 Like

Which Firmware are you using?

I currently have 4 sensors, but only one (Firmware 1.24 ) works as expected, the other (Firmware 1.16 Hauppauge) don’t show motion changes. When motion happens, they update temp and luminance… But motion is not working.

I still don’t understand the custom function fully… Do I have to translate the Decimal number to Binary and enter the decimal no. into the field? And is the last no, always overwriting all other no. in custom function field?
Im asking because the custom function 20 never worked out of the box and after several tries on other custom function numbers it seems to work partly (no motion) with the 20 now. (I use habmin)

All settings are same between 4 sensors, only difference I could find is my firmware.
Customer function is set to 20 at all sensors and motion, Door contact is working at same time.

I used item file and also here everything is same…

Hi,
20 is 0x14 which means binary report and super sensitive mode.

Assuming you want to set bits two and four:

BIT No		7		6		5		4		3		2		1		0	
BIN			0		0		0		1		0		1		0		0
HEX			0		0		0		1		0		4		0		0	=	14
DEC			128		64		32		16		8		4		2		1	=	20 (16+4)

In your config you need to enter the decimal number.

thank you very much for the explanation. At least I know now, that I understood it right :slight_smile:

Do you have any ideas what I could try, when I still don’t get any motion report?
I don’t need luminance or temp, if I could get motion report instead.

Have you set the dip switches on the device correctly? Not that it is still in testing mode.
Otherwise it has to work with OH2 - I am running two devices successfully.
Also check parameters:

 2: -1
 3: 80
 4: 99
 5: 8
 6: 20
 8: 3

It doesn’t seem to matter what I change…
Both dips are OFF, (if I turn them on into test mode, The LED reports works, so dips seem to be ok)

There is also an undocumented Switch called S4, I tried this one as well, but it didn’t changed anything.
When I update the values via openhabmin the value gets updated, but it has no impact.
I created a little sheet to faster try different settings


and even if i try to disable all reports by setting 07 Customer function to 123 and 06 to 63…
I still get reports for illum, temp etc… like before.

Do I have to wait ages until those vals will be updated?
The thing is, that I have one sensor which works perfectly, and all other 3 sensors (with older firmware and from Hauppauge instead from philo directly) are not reporting motion.

//is working
Number    MS_Battery                "Battery [%d %%]"                        				(Status)                { channel="zwave:device:5e0fd4ba:node17:sensor_battery" }
Number    MS_Temperature            "Temperature EG [%.1f °C]"    	<temperature>    		(Status,Temperature)    { channel="zwave:device:5e0fd4ba:node17:sensor_temperature" }
Number    MS_Bright                 "Brightness [%d]"                        				(Status)                { channel="zwave:device:5e0fd4ba:node17:sensor_luminance" }
Contact   MS_Door                   "Door [%s]"                     						(Status, Doors)         { channel="zwave:device:5e0fd4ba:node17:sensor_door" }
Switch    MS_Motion                 "Door Motion[%s]"          		<motion>         		(Status)                { channel="zwave:device:5e0fd4ba:node17:alarm_motion" }
Number    MS_Alarm                  "Alarm [%d]"                            				(Status)                { channel="zwave:device:5e0fd4ba:node17:alarm_tamper" }
Switch    MS_AAlarm                 "Alarm Access [%s]"          	<motion>         		(Status)                { channel="zwave:device:5e0fd4ba:node17:alarm_access" }

//is not working
Number    MS_T_Battery                "Battery T [%d %%]"                        			(Status)                { channel="zwave:device:5e0fd4ba:node23:sensor_battery" }
Number    MS_T_Temperature            "Temperature EG T [%.1f °C]"  <temperature>    		(Status,Temperature)    { channel="zwave:device:5e0fd4ba:node23:sensor_temperature" }
Number    MS_T_Bright                 "Brightness T [%d]"                        			(Status)                { channel="zwave:device:5e0fd4ba:node23:sensor_luminance" }
Contact   MS_T_Door                   "Door T [%s]"                     					(Status, Doors)         { channel="zwave:device:5e0fd4ba:node23:sensor_door" }
Switch    MS_T_Motion                 "Door T Motion [%s]"          <motion>         		(Status)                { channel="zwave:device:5e0fd4ba:node23:alarm_motion" }
Number    MS_T_Alarm                  "Alarm T [%d]"                            			(Status)                { channel="zwave:device:5e0fd4ba:node23:alarm_tamper" }
Switch    MS_T_AAlarm                 "Alarm T Access [%s]"                  				(Status)                { channel="zwave:device:5e0fd4ba:node23:alarm_access" }

I restarted openhab service and also reboot the pi 3.
I also switched from latest OH2 stable to openHAB 2.2.0 Build #1058



Does someone knows, what the S4 switch is for?

After playing around, I found when I set motion to OFF manually, the device will receive an motion On, when motion is happening… But the motion will not update back to off state, even when I cover the whole device, so no motion could be happening.

My current workaround for this issue is a rule, which now triggers off after some time has after the on passed.
It is still weird, that the custom function doesn’t seem to have a real impact, but at least I found a workaround…

Yea, it is intended that there is no Motion OFF sent by the device.
Maybe give this a read:

1 Like

Great. I’m tinkering since two weeks with a D-Link version of that device and was always wondering why I can’t get the OFF command to work.
I’m using the expire binding to turn it OFF by the way. This was meant as a workaround, but now it has to be the final solution I think :rofl:

I think this has been updated by the firmware … With a more updated Firmware 1.24, I get the off command. But the latest devices by Hauppauge with older Firmware 1.16 don´t report it.
And unfortunately there is no way updating the Device… I already spoke to CEO of Philo, and they don’t want to publish the Firmware to public (only to provider who could assure that the device will not break during update)…

Just use the expire binding and your problem is solved:

Switch DCH-Z120 {channel="zwave:device:15ca6a108b9:node39:alarm_motion" , expire="2s,command=OFF"}

1 Like

Hi there

Was this issue ever really solved?
I just recently shifted to OH2, and I am converting my OH1 setup one by one. My most reliable PIR sensor was the PST02-B, which I have yet to change battery in, and turns on my light every time. #AWESOME
Until now, that is. I cannot for the love of … get the Binary Sensor channel to work. I briefly tried the Alarm channel, but as you mention, it does not send an off command. However, the ON command returnes as expected.

From the log file, you can see that the basic entry calls out with 255 when I enter the room, and 4 minutes later with 0.
However, my item, does not get updated, and even with a rule set to Technic_Room_PIR.changed is not getting called.

Any ideas?

Switch Technic_Room_PIR			"Technic Room PIR [MAP(motion.map):%s]"	<pir>	(All_PIRs)	{ channel="zwave:device:15f5e96a49b:node11:sensor_binary" }

2017-11-01 20:35:12.729 [ZWaveBatteryCommandClass  ] - NODE 11: Battery report value = 100
2017-11-01 20:35:12.730 [ZWaveThingHandler         ] - NODE 11: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-11-01 20:35:12.730 [ZWaveThingHandler         ] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2017-11-01 20:35:12.731 [ZWaveThingHandler         ] - NODE 11: Updating channel state zwave:device:15f5e96a49b:node11:battery-level to 100 [DecimalType]
2017-11-01 20:35:12.774 [icationCommandMessageClass] - NODE 11: Application Command Request (ALIVE:DETAILS)
2017-11-01 20:35:12.774 [icationCommandMessageClass] - NODE 11: Incoming command class ALARM
2017-11-01 20:35:12.775 [ZWaveAlarmCommandClass    ] - NODE 11: Received ALARM command V4
2017-11-01 20:35:12.775 [ZWaveAlarmCommandClass    ] - NODE 11: Process NOTIFICATION_REPORT V4
2017-11-01 20:35:12.775 [ZWaveAlarmCommandClass    ] - NODE 11: NOTIFICATION report - 0 = 0, event=8, status=255
2017-11-01 20:35:12.776 [ZWaveAlarmCommandClass    ] - NODE 11: Alarm Type = BURGLAR (0)
2017-11-01 20:35:12.777 [ZWaveThingHandler         ] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-11-01 20:35:12.777 [ZWaveThingHandler         ] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-11-01 20:35:12.778 [ZWaveThingHandler         ] - NODE 11: Updating channel state zwave:device:15f5e96a49b:node11:alarm_burglar to ON [OnOffType]
2017-11-01 20:35:12.813 [icationCommandMessageClass] - NODE 11: Application Command Request (ALIVE:DETAILS)
2017-11-01 20:35:12.813 [icationCommandMessageClass] - NODE 11: Incoming command class BASIC
2017-11-01 20:35:12.814 [ZWaveBasicCommandClass    ] - NODE 11: Received Basic Request
2017-11-01 20:35:12.814 [ZWaveBasicCommandClass    ] - NODE 11: Basic Set sent to the controller will be processed as Basic Report
2017-11-01 20:35:12.814 [ZWaveBasicCommandClass    ] - NODE 11: Basic report, value = 0xFF
2017-11-01 20:35:12.815 [ZWaveThingHandler         ] - NODE 11: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-11-01 20:35:12.815 [ZWaveThingHandler         ] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2017-11-01 20:35:12.868 [icationCommandMessageClass] - NODE 11: Application Command Request (ALIVE:DETAILS)
2017-11-01 20:35:12.869 [icationCommandMessageClass] - NODE 11: Incoming command class SENSOR_MULTILEVEL
2017-11-01 20:35:12.869 [ltiLevelSensorCommandClass] - NODE 11: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
2017-11-01 20:35:12.870 [ltiLevelSensorCommandClass] - NODE 11: Sensor Multi Level REPORT received
2017-11-01 20:35:12.870 [ltiLevelSensorCommandClass] - NODE 11: Sensor Type = Temperature(1), Scale = 0
2017-11-01 20:35:12.871 [ltiLevelSensorCommandClass] - NODE 11: Sensor Value = 21.5
2017-11-01 20:35:12.871 [ZWaveThingHandler         ] - NODE 11: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-11-01 20:35:12.872 [ZWaveThingHandler         ] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 21.5
2017-11-01 20:35:12.872 [eMultiLevelSensorConverter] - NODE 11: Sensor is reporting scale 0, requiring conversion to 0. Value is now 21.5.
2017-11-01 20:35:12.873 [ZWaveThingHandler         ] - NODE 11: Updating channel state zwave:device:15f5e96a49b:node11:sensor_temperature to 21.5 [DecimalType]
2017-11-01 20:39:02.893 [icationCommandMessageClass] - NODE 11: Application Command Request (ALIVE:DETAILS)
2017-11-01 20:39:02.894 [icationCommandMessageClass] - NODE 11: Incoming command class BASIC
2017-11-01 20:39:02.895 [ZWaveBasicCommandClass    ] - NODE 11: Received Basic Request
2017-11-01 20:39:02.895 [ZWaveBasicCommandClass    ] - NODE 11: Basic Set sent to the controller will be processed as Basic Report
2017-11-01 20:39:02.896 [ZWaveBasicCommandClass    ] - NODE 11: Basic report, value = 0x00
2017-11-01 20:39:02.898 [ZWaveThingHandler         ] - NODE 11: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-11-01 20:39:02.899 [ZWaveThingHandler         ] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0

Best regards
Morten Attermann Holst

Morten,

Most of my problems resolved when I started from scratch aned used habmin instead of paperui to do the config. What have you used?

  • Tom

I used habmin, but my device was running fine under 1.x, so all zwave configuration was done in the old system. I am wondering why the Basic report does not get the…

 [OnOffType]

… type below the 255 value, as the ALARM does.

/Morten