Has anyone managed to get the Philio PSP05 motion sensor working in HA? With the default configuration values, once motion has been detected, HA reports it as permanently detected - it never clears after a certain time. Thanks in advance.
No, but I have had problems with other motion sensor.
Go into the HASS device config for that device and look for disabled entities, enable them, restart HASS, and see if any of them work,
Thanks, I found an entity that gave me what I wanted after some trial and error with the configuration settings as well.
For future reference, this is how I have the PSP05 configured:
And the entity I am using is Sensor state (Motion):
Hi Geoff,
Did you find a way to solve the issue ? I meet exactly the same problem : once the motion state has been âDetectedâ, it never reverts back to âClearâ.
I had to set it up using the Sensor state (Motion) entity instead of the expected Motion detectionâŚ
Thanks Geoff,
Unfortunately, the sensor âSensor state (Motion)â is unavailable on my system I have only the âMotion detectionâ state which is never triggered if my Philio is configured as âBinary Sensorâ (parameter 7, bit 4, âNotification typeâ).
The good news is that the detection state is triggered if I configure the parameter 7, bit 4, to âReport Notificationâ, but, as many people in the forums, the state âDetectedâ is never reverted back to âClearâ (it is like the âmotion offâ of the sensor is never sent or received by Home Assistant). But I finally find a way to make it work, by configuring a small Python script which automatically reset the motion state (Detected > Clear) after some seconds. So, at the end, it WORKS !
Thanks anyway for your kind support.
Pierre
Iâve found the IKEA (zigbee) motion sensors to be decent (and cheap). Iâve also had good luck with the Fibaro ones if you need zwave.
Thank you very much, Geoff!
You made my day!
I have enabled the sensor
binary_sensor.motion_sensor_sensor_state_motion
and disabled the sensor
binary_sensor.motion_sensor_motion_detection
(which was always on âdetectedâ)
now everything works as desired.
For me too both the motion sensor and tamper functionality work after enabling the both -by default disabled- sensor state entities. Donât forget to also set the âShow asâ for the both entities âSensor state (Motion)â and âSensor state (Tamper)â to âmotionâ and âtamperâ respectively at the same time you enable them.
Looking at the ZWave JS UI debug window it seems the problem with the standard motion device not going back to âclearâ is caused by the psp05 firmware returning an unknown (incorrect?) value of 254 for the âclearâ notification. According to the log this notification gets disregarded by zwave js.