[Newbie] Z-Wave PIR Sensor shows as Unknown Device

Bruce_Osborne · June 29, 2019, 3:45pm

I verified last Sunday. See?

chris · June 29, 2019, 3:47pm

Sorry - I missed it. If you don’t reply to me, then I don’t get a notification and it relies on me finding the message in the list of new messages…

I’ll have a look.

chris · June 29, 2019, 3:49pm

So the log shows the same thing -:

2019-06-23 09:26:18.377 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:16b83f77166:node3:sensor_temperature to 24.8 °C [QuantityType]

It’s clearly configured as a QuantityType, and is setting the units correctly.

Bruce_Osborne · June 29, 2019, 3:57pm

Sorry (Newbie, remember?)

IMO it is more important right now for you to get Zigbee ready for release

chris · June 29, 2019, 4:07pm

Another thought - how have you defined the item? I’m not an expert on the QuantityType, but possibly if you’ve not defined the item correctly, then OH may not perform the conversion.

Bruce_Osborne · June 29, 2019, 4:25pm

Yes and trying the default units (%units?) gave an error.

chris · June 29, 2019, 4:33pm

Ok, I’m not sure then. I’m not super familiar with the QuantityType - only what the binding does, and from the logs, it is providing a QuantityType with the correct units, so the binding looks fine at least.

Bruce_Osborne · June 29, 2019, 4:36pm

Is OH keying off the message before that? It does not show units.

2019-06-23 09:26:18.375 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=24.8

My item (now with my transform) is

Number Outdoor_Temperature "Temperature [JS(tempConvert.js):%s F]" <temperature>
 (papillon_yard) { channel="zwave:device:16b83f77166:node3:sensor_temperature" }

chris · June 29, 2019, 4:41pm

No. You should check your events log if you want to see the OH side.

Also, remember that this is working for others here (at least it used to, and I’ve not heard any problems other than with your setup, so I’m assuming it’s still working for others). The static unit tests that are run every time the binding is compiled also shows that this is correctly decoding and sending the channel types as QuantityType.

Hmmm - are you sure this is correct for a QuantityType???

chris · June 29, 2019, 4:42pm

Maybe it’s worth taking a look at the docs -:

Bruce_Osborne · June 29, 2019, 5:02pm

I 'borrowed" a script that just keys off the F

I just changed to try
Number Outdoor_Temperature "Temperature [%.2f %unit%]" <temperature> (papillon_yard) { channel="zwave:device:16b83f77166:node3:sensor_temperature" }
and , after an update, received
2019-06-29 13:00:04.483 [vent.ItemStateChangedEvent] - Outdoor_Temperature changed from NULL to 31.4
and

No units.

chris · June 29, 2019, 5:04pm

I’m not sure what you mean by this?

I’d suggest to read the docs I referenced!

As far as I can tell, your item definition is incorrect - no matter how it was generated. As suggested earlier, you’re not using the quantity type - you’re using a standard number, so I suspect that this doesn’t work for that reason?

Bruce_Osborne · June 29, 2019, 5:19pm

Sorry, I missed how to specify a quantity. Looks OK now. Newbie error for sure.

2019-06-29 13:17:28.808 [vent.ItemStateChangedEvent] - Outdoor_Temperature changed from NULL to 88.52 °F

Thank you for your patient instruction.