Philio PSM 4-1 | Home Assistant | Page 1

dusk sun Sep 18, 2021, 6:27 PM

#

That looks like you're polling the device on wakeup.

#

Multiple times the same values actually, which might be something the driver should avoid doing

#

Are any associations to the controller node configured?

fallen venture Sep 19, 2021, 1:11 AM

#

I have not configured anything other than the wakeup interval and the sensor report intervals (configuration parameters. I thought zwavejs does not support associations. I excluded the device from SmartThings and included it in zwavejs2mqqt. Should I have done a factory reset?

#

The device is responding better after changing the wakeup interval. I will share another debug log at the end of my day. In the mean time this is the device debug information: http://hastebin.com/bihawoqohe.json

fallen venture Sep 19, 2021, 9:04 AM

#

Today's debug log (sofar) http://hastebin.com/raw/tupowoboca

dusk sun Sep 19, 2021, 1:35 PM

#

zwave-js certainly does support associations. The HA integration just doesn't give you a way to edit them yet. zwavejs2mqtt does.

#

The dump doesn't include the associations either - you'll have to look at the associations UI in z2m.

#

In your log the device still isn't reporting on its own, all updates are obtained by polling after it wakes up.

#

You could also re-interview the device and make a driver log of that. That includes the associations.

#

Or try this:
https://community.ezlo.com/t/the-philio-psm02-4-in-1-z-wave-sensor-not-reporting/192373/3
Param 7 is missing from our config file I think, so you'll have to use the controls for manually setting config params in zwavejs2mqtt

fallen venture Sep 19, 2021, 1:53 PM

#

If updates are still obtained by polling, it explains why I do not get motion events. I did set parameter #7 to 22 and confirmed it by doing a get. I will do an re-interview and share the debug log.

fallen venture Sep 19, 2021, 6:07 PM

#

In zwave2mqqt, MultiSensor 6 has a group, while PSM02 does not. In the Z-Wave JS Config DB, MultiSensor 6 has Association Group #1 auto assigned checked, while PSM02 has not.

dusk sun Sep 19, 2021, 7:09 PM

#

Hm, that's probably it. Do you already have a log of the re-interview?

fallen venture Sep 19, 2021, 7:10 PM

#

PSM02 is not a ZWave Plus device and therefor does not define lifeline. Would “isLifeline”: true instruct zwave2mqqt to create an association or is there another to create an association automatically.

dusk sun Sep 19, 2021, 7:11 PM

#

Yep, that line needs to be added to the config file - that should be all

fallen venture Sep 19, 2021, 7:19 PM

#

Here is the log for the re-interview: http://hastebin.com/raw/gonipifore

dusk sun Sep 19, 2021, 7:39 PM

#

[Node 004] No information about Lifeline associations, cannot assign ourselves

#

yep, we need the isLifeline entry in the config file

#

Would you be willing to create a PR?

fallen venture Sep 19, 2021, 7:41 PM

#

Yes, I have started on it. I have not done it before, but there is a first time for everything.

dusk sun Sep 19, 2021, 7:53 PM

#

If you need pointers, here we walked someone else through the process (which was a bit more complicated in his case):
https://github.com/zwave-js/node-zwave-js/pull/3357

#Philio PSM 4-1