ioBroker z-wave2 adapter has not been updated for a while

[nesheimt]

I first posted this question on ioBroker Facebook group, but was requested by the group expert to post it here instead:

I'm considering to make ioBroker my main smart home system, but for that I need to start using the zwave2 adapter. However, it appears that the available adapter is based on a rather older version (v10.23.6) of node-zwave-js which is now v13.10.1?

I seems no to be a good idea to rely on the zwave2-adapter available since it hasn't been updated in a year?

Would an alternative good solution be to install zwave-js-ui as a stand-alone and run states/data over to ioBroker via MQTT?

My apologies if this is not the appropriate place to post such a question.

[TiDO2k]

is there any further development?

[AlCalzone]

I'll update it soon

[nesheimt]

Will this updated version of ioBroker Zwave2 have (automatical) dependency bump (?) from the underlaying node-zwave-js components that are constantly updated and improved?

[TiDO2k]

soon? I'll change to HomeAssistant. No further development here.

[nesheimt]

soon? I'll change to HomeAssistant. No further development here.

Looks you might be right about this adapter. But a way around is to use Zwave JS UI as stand alone, and use MQTT to ioBroker. This takes a few more things to handle(and fiddle with) but works quite nice. Once you are past this hurdle(requires some efforts), but then you are no longer dependent on any adapter even though an adapter would be very nice.

[AlCalzone]

I can understand the frustration. This year alone (8 weeks), my kids have been home sick 3 weeks, I've been sick 1 week, and I've been on vacation for 1 week. The remaining time needs to be somehow divided between work, family and everything else that's going on.

Hard to find the 3-4 hours it will take to update the adapter, considering I don't even have much of a smart home right now.

I still plan on updating, but it's far from my highest priority at the moment.

[mcm1957]

Take car of yourself. Health and family are of course much much higher priority!
I'm sure that this is not only my personal oppinion.

[WendlTo]

Hello, I just wanted to ask what it looks like. As a father myself, I know how difficult it is to find time.
Best regards Tobias

[LaplaceII]

Hello AlCalzone, do you see a chance for update or do you recommend to go for the proposal mentioned above: Zwave JS UI as stand alone, and use MQTT to ioBroker?

[nesheimt]

After months of using Zwave JS UI as stand alone I can in general say that it's very stable. There might be something I do wrong but here is one isseue for actuators that operates with "current value - target value pairs". If a device is turned off by a local switch or auto off, the current value in Zwave JS UI is updated, but not the target value(which stays at the "on-value" of 99).

That poses a problem when turning on again using MQTT. Since the target value is already 99 and I'm sending 99 there is no change and hence the value is not sent. I have not managed to send value updates(as opposed to value changes) with MQTT without causing ringing/feedback. My workaround is a JS-handler triggering on current value=0 -> targe value=0.

[PG248]

@AlCalzone So you didn't find the necessary 3-4 hours to update the adapter in the last 5 month? No offense, you are doing this in your free time, but then I'd call this project as currently not being maintained. I suggest you place a message in the Readme WARNING: This adapter is currently not maintained! as it is in the GitHub repository of the original ioBroker z-wave adapter (https://github.com/ioBroker/ioBroker.zwave) so people know they are installing legacy software without having to read through the issues list first.

Unfortunately there is no alternative z-wave adapter for ioBroker available that is actively maintained aside from Zwave JS UI over MQTT.

Given that z-wave integration is an essential protocol for any home automation system as is Zigbee, this is probably the final motivation for me to move over fully to home assistant.

[Apollon77]

@PG248 hm… about which exact issue we talk? If all is working why you push for an update?
Or is it about missing feature?

I don‘t get it

[torbjornnesheimbring]

@Apollon77 I have been reluctant to push the question of upgrades since it's peoples sparetime any effort is taken from. Instead I use the MQTT-approach. I must however admit that I never tried the zwave2 adapter fearing that it would come to a sudden stop caused by some breaking change from the "ioBroker components/framework" and a not up to date adapter.
But, based on your answer above...such a scenario is not likely? If so, I will definitely install the zwave2 instead of using the MQTT(which have a few particularities).

[Apollon77]

Without trying no one knows ;-) I will try to do some basic eep updates in next days.

[Apollon77]

Alright ... ok I did some relevant updates to ensure it runs in models js-controllers and such
#1097

if someone likes to verify you can use Admin - Expertmode - Custom install (Github icon) - Custom tab and use "https://github.com/Apollon77/ioBroker.zwave2#update-deps0825" to install from my fork.