ZWave binding updates

[rdslw (Rado Sław)]

@chris Is using daily zwave heal safe/working as expected in 2.5.8 ?

[5iver (Scott Rushworth)]

@rdslw

1. I understand I can change “Thing {} changed” to “Thing {} received update” (this may be needed due to how zwave works)

You will be fine with changed. You’re also probably only concerned with when the Thing goes to OFFLINE, which would simplify things.

@rdslw

2. How does logging (last line) works, specifcally how/when .log.warn is attached to function zwave_thing_alert

The core.rules.rule decorator creates the log attribute for you.

@rdslw

3. I understand that I can just drop it to jsr223/python/personal/anyfilename.py ?

It would be found and executed anywhere under /automation/jsr223/. The directory you stated uses the directory structure that I have recommended for use with the helper libraries.

@rdslw

4. what would be cosher way to access thing.properties dictionary inside of zwaver_thing_alert function?

    zwave_thing_alert.log.warn("things.get(event.thingUID).properties: {}".format(things.get(event.thingUID).properties))

This returns a java.util.Collections.unmodifiableMap(), not a dict. So, you’ll need to use the Map methods.

    zwave_thing_alert.log.warn("things.get(event.thingUID).properties.get(\"modelId\"): {}".format(things.get(event.thingUID).properties.get("modelId")))

You are using Jython, so you can use and access Java classes, interfaces, etc. One of the methods for Map is get, which makes it very easy to think you are dealing with a dict. To be sure of what type of object you are dealing with, just use type…

    zwave_thing_alert.log.warn("type(things.get(event.thingUID).properties): {}".format(type(things.get(event.thingUID).properties)))

2020-08-24 17:44:00.878 [WARN ] [jython.Alert: Z-Wave Thing] - type(things.get(event.thingUID).properties): <type 'java.util.Collections$UnmodifiableMap'>

[Duke_Jones]

Hi,
The last answer in this thread was a long time ago, but I think my question still fits best here.
I have been using openHAB with pleasure for a few years and have built up an extensive Z-Wave network, among other things.
With reference to the headline, however, I have the following question: Is there still (or will be) any kind of development for Z-Wave binding or is this binding slowly dying in openHAB ?
Unfortunately, I have not been able to find any news for some time.
So, what is the future of Z-Wave in openHAB ?

Best regards …

Edit:
@chris : a month has now passed without a reply - so just mention you. I guess you don’t read here anymore. Please, would you mind giving a short answer to my question, so that people know how zwave is developing - or could develop within openhab ?
Thank you

[digitaldan (Dan Cunningham)]

I can’t answer for @chris , but personally i would not classify the binding as dying at all, you can see it gets regular updates for devices:
https://github.com/openhab/org.openhab.binding.zwave/commits/main
That being said, the binding itself is in a mature state, which means less core changes are needed for day to day operations, in addition the z-wave specification has not changed for some time (most vendors are focusing on matter) , so again , less changes are needed for it.

[Andrew_Rowe]

IDK… PR from Bob to add 700 series controller been sitting there since Feb