You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Will this updated version of ioBroker Zwave2 have (automatical) dependency bump (?) from the underlaying node-zwave-js components that are constantly updated and improved?
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.
The text was updated successfully, but these errors were encountered: