zwavejs-ui - FAIL - how many of you did try & succeed?

[janpep]

OpenZwave -> zwavejs-ui
Please tell me about your attempts. Just to get an idea of succes rate.

I recognized the reponse of Tuinfluiter with a big smile.

When I first read about the migration to Zwavejs-UI and read the instruction, I thought: I'm not going to do this.
The second time when I read it, I thought the same.

I think I had feeling this even more than twice.
It did mean that I postponed it a few times and had to work up the courage to get started.
I recognize that several people had to overcome something. Especially because everything just worked.

My next thought was that this is definitely something that will turn off the novice hobbyist. In addition, you have to gather the information from different sources and the trick is to extract what applies to your situation and what not. I understand that it is all volunteer work, but the method to be followed is not crystal clear. You must be aware that not everyone has the same platform and therefore the working methods may differ.
For example, I wanted to install everything in my Ubuntu (virtual machine) without using Docker again under that.
All that makes it seem like something for advanced users.
At the end I just tried. I installed Domoticz with a copy of my database, MQTT and Zwave-js-ui one by one in a test environment and connected my Zwave stick to it.
Meanwhile the whole thing was further complicated by the fact that with the new version 7.2 of DSM on my Synology, the USB stick was only recognized by connecting it with an USB hub in between. (Has something to do with a solder point on old Gen 5 stick).
All this fiddling kept me busy for a few days. I can completely understand that many people would have already given up hope!
BUT through this experimenting and just doing, I got a better understanding how things work together.
At the end I have to say that it was easier than it seemed beforehand. Also I see that it is working very stable. At the moment only a few small things remaining, like batterylevel of Remotec scene master BW8510 that is visible in Devices, but not with dzVents.

[tlfriend1]

All of my devices are visible in the Z-wave js ui interface but not in Domoticz, can someone please share how you solved this issue? thanks !

[BartSr]

did you do all zwavejs setings according wiki?

[tlfriend1]

did you do all zwavejs setings according wiki?

Thanks it turned out the port was being blocked.
I see the devices in Domoticz (swtiches and a Fibaro "the button") the issue I have now is that when I press the button I get multiple duplicates of the device. Before I was able to define in the hardware tab for the button what happened with each kind of push (long push, pushing it several times, etc) and now I don't see that option anymore after migration.

[janpep]

It was so simple and so reliable in openzwave

Yes, the disadvantage of the new situation in my opinion is that it will be a longer chain with multiple packages, each with its own updates and dependencies.

[gizmocuz]

It was so simple and so reliable in openzwave

Yes, the disadvantage of the new situation in my opinion is that it will be a longer chain with multiple packages, each with its own updates and dependencies.

Before when there was a single change in OZW in its core code, or configuration, Domoticz had to be updated.
Now, you can choose what to update, independently of each other.

When your zwave network is working/running, there is no need to update zwavejs-ui, or MQTT

The advantage is also that you can use MQTT for other things.

But you can also create one docker-compose file containing all necessary services.
Then you can use one command line to update all in one go
(I would not recommend this, but it is possible)

[janpep]

That is true. But, I am always afraid of automatic updates having an unnoticed effect on one of the other packages under Linux.
This turned out to be the case for the Synology update regarding USB support. Something you don't expect, but it does have an effect on the whole thing. So far things have been going very well with MQTT and Zwave-js-ui and and afterwards it turned out better than expected.

[lost]

Before when there was a single change in OZW in its core code, or configuration, Domoticz had to be updated.

That's true for code, but on configuration side this is some xml in config tree with 1 device-config file to add to support a new device and another to edit, that makes the link between device ID and it's device-config file path.

In an ideal world, a stable protocol should mean a stable code base after development. So not so much updates (in theory, and zwave was undocumented for long). Not the same problem as Zigbee (less standardization/no certification process) IMO.

This brings me to python plugins can drain heavy dependencies: Zigbee4domoticz brings quite a lot for instance and pip installed in specific versions that may cause system wide issues (we somehow loose the coherency of system utilities/libraries ensured through what's available using apt-get when you stick to this and don't even install pip!).

Here at least we have the possibility to use python venv as a light alternative to containers & looks this work according to Pipiche:
https://github.com/zigbeefordomoticz/Do ... ssues/1724

But the consequence on setting a PYTHONHOME for Domoticz at startup means we can have only one venv shared for all plugins. When you don't have many/without the same dependencies that's OK, but even for plugins this can already become problematic!

[gizmocuz]

@lost, yeah but that's NOT a great idea!
This way other users cannot benefit from new configurations.

And docker containers are light and easy to setup once you know how they work.
Making a backup, checking out specific versions or transferring them to other systems is super easy.
And... You can also use other software that can work with MQTT-AD (HASS, google/apple homekit integrations etc)

[gizmocuz]

I will save you 1 google search

https://stackoverflow.com/questions/218 ... -container

Have a look at the IBM report.

Next to this, it is an extreme clean way to install/manage applications

[riom16]

Hi,

I Installed zwavejs-ui, MQTT, Docker on 3 Raspberry Pi 3B. First was a sandbox. It worked but painful first install. The next 2 were in real Life and easier. It crashed, it crashes, it will crash. The 2 configurations are not reliable.

Kernel crashes without logs. Sure when docker is updated. Sometime when Domoticz start. Sometime without reason...

In the tutorial we add a docker repository. This involve a lot of updates. Perhaps it should be better to prefer Docker form Raspberry Pi Os repos ?

All this for a console session talk in a USB virtual serial interface

I will try Home Assistant in sandbox. (I like Domoticz)

Regards.