Easiest way to migrate Openzwave to ZWave-JS-UI

For Z-Wave related questions in Domoticz

Moderator: leecollings

MikeyMan
Posts: 237
Joined: Wednesday 17 October 2018 12:11
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by MikeyMan »

@Domoberry

- No there is no dependency on mosquitto version, this is just a message broker
- You can add a second MQTT gateway. Or even a third or a fourth per usage ;)
User avatar
Domoberry
Posts: 121
Joined: Tuesday 30 May 2017 19:00
Target OS: Raspberry Pi / ODroid
Domoticz version: 2024.7
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Domoberry »

Thanks @MikeyMan, Will take it from there
User avatar
Egregius
Posts: 2589
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: v2024.7
Location: Beitem, BE
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Egregius »

waltervl wrote: Tuesday 03 January 2023 16:06
Egregius wrote: Tuesday 03 January 2023 14:53 I have one small issue with zwave-js-ui instead of openzwave.
A lot of my dimmers don't respect the soft dimming time set to the minimum and use the factory default 3 sec. Because of that a lot of lights react slow.
Just tested by restoring an old snapshot of my domoticz server and the lights all switch on instantly. With zwavejs that takes 3 seconds.
This is issue seems to be related to this https://github.com/domoticz/domoticz/issues/5179
Tried another time today and found something interesting about this.
When in the zwave-js-ui on a dimmer:
clicking at ON under "Binary Switch v1" turns on the light instantly.
Using "Target value"=99 under "Multilevel Sitch v3" turns on the light with a 3 second slow fade.
Because all the lights are turned on dimmed here the 3 seconds delay is a real showstopper for me.
rron
Posts: 247
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by rron »

JackD wrote: Monday 07 November 2022 19:30 After almost a year of not updating Domoticz, and the fear of the loss of Open Z-wave support in future releases, I updated Domoticz yesterday to beta14599. And can report that in beta14599 the open z-wave is still functional, but in the log there is a note that tells it is depreciated.

Perhaps make a super Domoticz docker container which has it all, Domoticz, ZWave-JS-UI, Mosquitto and everything else you need, including a very detailed and up to date step by step installation manual. Then you again have the "one stop shop" and would make it a lot easier for us not IT specialists. Just a suggestion, don't know it this is technically possible :oops:

Sorry for the bit of nagging, of course I appreciate all you who spent there time in building and maintaining Domoticz.
Is what JackD suggested everything in one container or one “image” not possible? I think that this suggestion make life for some off us more easier. :?:
Rpi, RFXcom, klikaan klikuit switch,thermosmart, z-wave, espeasy, smartevse
BartSr
Posts: 395
Joined: Sunday 03 July 2016 16:16
Target OS: Raspberry Pi / ODroid
Domoticz version: V2024.7
Location: Netherlands
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by BartSr »

Fully agreed. Domoticz is great but more and more difficult to set up to get all features available. Be aware that this might force others to move to other well known home automation systems.
Raspberry pi 3b
Arduino
KAKU
RfxCom
Zwave2MQTT
OTGW
Chinese sensors temp (Dallas),movement
Tasmota
Esp8266 / 32 espeasy
Zigbee2MQTT
rron
Posts: 247
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by rron »

I know in hass it is possible to do a one click install
Rpi, RFXcom, klikaan klikuit switch,thermosmart, z-wave, espeasy, smartevse
thomasbaetge
Posts: 153
Joined: Wednesday 02 October 2019 11:47
Target OS: Linux
Domoticz version: 2023.1
Location: DE / BY / LT
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by thomasbaetge »

I am kind of 'ready to migrate' with everything set up and running.
Just, how will I be able to identify the new devices?
will they have the same node ID as before or how do I identify them?
Benneton
Posts: 111
Joined: Thursday 08 December 2016 9:46
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Benneton »

I am at the same stage as you are, more or less ready to take the plunge in the deep end...
My guess is that current devices will have to be migrated to the new ID's found by Zwave-JS-UI.
Done via the replace option on devices. At least that is what I had in mind to do.
MikeyMan
Posts: 237
Joined: Wednesday 17 October 2018 12:11
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by MikeyMan »

Benneton wrote: Monday 13 March 2023 20:37 I am at the same stage as you are, more or less ready to take the plunge in the deep end...
My guess is that current devices will have to be migrated to the new ID's found by Zwave-JS-UI.
Done via the replace option on devices. At least that is what I had in mind to do.

Let me know if you got that to work in any way ;)
thomasbaetge
Posts: 153
Joined: Wednesday 02 October 2019 11:47
Target OS: Linux
Domoticz version: 2023.1
Location: DE / BY / LT
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by thomasbaetge »

Benneton wrote: Monday 13 March 2023 20:37 I am at the same stage as you are, more or less ready to take the plunge in the deep end...
My guess is that current devices will have to be migrated to the new ID's found by Zwave-JS-UI.
Done via the replace option on devices. At least that is what I had in mind to do.
Yes, that much is clear, the question is, will I be able to identify the new devices.
For example, I have 6 Z-Wave window sensors, all the same. I the OZW control panel they have meaningful names like 'Window Kitchen'.
Will I be able to identify the newly created devices accordingly?
Same goes for my bunch of double relays. it would be really awkward if I want to switch on the livingroom floor heating and start the outdoor alarm siren instead, because they are running on the same device type.
Benneton
Posts: 111
Joined: Thursday 08 December 2016 9:46
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Benneton »

That is a good question, I thought that my network would keep the same node ID which in OZW can be found under Hardware settings of z-wave device for domoticz. From there I was planning to name my devices again into something logical like kitchen light etc.
Can someone that has made the move already confirm my thought?
Thanks!
MikeyMan
Posts: 237
Joined: Wednesday 17 October 2018 12:11
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by MikeyMan »

You can give it a try. It's easy to revert to old situation.
thomasbaetge
Posts: 153
Joined: Wednesday 02 October 2019 11:47
Target OS: Linux
Domoticz version: 2023.1
Location: DE / BY / LT
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by thomasbaetge »

Just try is not an option for me.
I just migrated to a different HW (from RPI to NUC) and that alone took me 2 weeks because I carefully test and migrate everything.
my current device count is closing in to 600 and my house relies very much on a stable and reliable system (heating, Solar, PV, alamr system etc.) plus it has to sustain regularily longer periods of absence.
With that being said, I don't do trial and error if I can avoid it.
MikeyMan
Posts: 237
Joined: Wednesday 17 October 2018 12:11
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by MikeyMan »

It's not trial and error. It's just switching one thing off and the other on. No harm no foul.
thomasbaetge
Posts: 153
Joined: Wednesday 02 October 2019 11:47
Target OS: Linux
Domoticz version: 2023.1
Location: DE / BY / LT
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by thomasbaetge »

I agree for that part and I already did this with a spare controller stick to test the zwjs installation.

my 'issue' is the proper migration path in replacing the 'old' devices with the new ones, where I see the question I asked before. (not how to do it in domoticz, I am clear about that)
if that turns out to be trial and error because I can not clearly identify and assign the new devices, I may get myself into some trouble.
That's the only open point I'm having, everything else is already 'locked and loaded' and ready to go.

The question should be easy to answer for everyone, who already did it.
User avatar
Egregius
Posts: 2589
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: v2024.7
Location: Beitem, BE
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Egregius »

New devices will have the node id in their name. Make a screenshot of your nodelist with the names in the openzwave hardware screen.
Once you have that it should be possible to identify them, but still then it's a huge work on that number of devices. I have 70 nodes, did the change once but returned to openzwave because of delay on my dimmers. Don't know if and when I'll try again.
thomasbaetge
Posts: 153
Joined: Wednesday 02 October 2019 11:47
Target OS: Linux
Domoticz version: 2023.1
Location: DE / BY / LT
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by thomasbaetge »

thanks a lot, that is the information I needed.

I know it will be a lot of work, but I will do this on a rainy weekend day (of which we have too many anyway).
I will report back with the results and any issues I may encounter during the process.
Dave47
Posts: 136
Joined: Thursday 19 July 2018 14:36
Target OS: -
Domoticz version: 2023.1
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Dave47 »

Hi. We have a problem from the beginning.
First we install docker compose

Code: Select all

version: '3.3'

services:
  domoticz:
    image: domoticz/domoticz:stable
    container_name: domoticz
    restart: unless-stopped
    # Pass devices to container
    devices:
     - "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0"
    ports:
      - "8080:8080"
    volumes:
      - ./config:/opt/domoticz/userdata
    environment:
      - TZ=Europe/Amsterdam
      #- LOG_PATH=/opt/domoticz/userdata/domoticz.log
docker composer up -d the output is:
pi@raspberrypi:/opt/domoticz $ sudo docker compose up -d
yaml: line 8: did not find expected key
pi@raspberrypi:/opt/domoticz $

We have pair all devices in secure mode. Is that maybe the problem.
How can we fix this?
Possible to write a key rule in version 3.3 and how can we do that?
What will be the right path for device if:

pi@raspberrypi:/opt/domoticz $ ls -al /dev/serial/by-id
total 0
drwxr-xr-x 2 root root 60 Mar 15 18:30 .
drwxr-xr-x 4 root root 80 Mar 15 18:30 ..
lrwxrwxrwx 1 root root 13 Mar 15 18:30 usb-0658_0200-if00 -> ../../ttyACM0
sailmich
Posts: 245
Joined: Wednesday 17 February 2016 22:55
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Germany
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by sailmich »

Dave47 wrote: Friday 17 March 2023 7:46 Hi. We have a problem from the beginning.
First we install docker compose

Code: Select all

version: '3.3'

services:
  domoticz:
    image: domoticz/domoticz:stable
    container_name: domoticz
    restart: unless-stopped
    # Pass devices to container
    devices:
     - "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0"
    ports:
      - "8080:8080"
    volumes:
      - ./config:/opt/domoticz/userdata
    environment:
      - TZ=Europe/Amsterdam
      #- LOG_PATH=/opt/domoticz/userdata/domoticz.log
docker composer up -d the output is:
pi@raspberrypi:/opt/domoticz $ sudo docker compose up -d
yaml: line 8: did not find expected key
pi@raspberrypi:/opt/domoticz $

We have pair all devices in secure mode. Is that maybe the problem.
How can we fix this?
Possible to write a key rule in version 3.3 and how can we do that?
What will be the right path for device if:

pi@raspberrypi:/opt/domoticz $ ls -al /dev/serial/by-id
total 0
drwxr-xr-x 2 root root 60 Mar 15 18:30 .
drwxr-xr-x 4 root root 80 Mar 15 18:30 ..
lrwxrwxrwx 1 root root 13 Mar 15 18:30 usb-0658_0200-if00 -> ../../ttyACM0
Change your docker compose.yml to dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0.
Dave47
Posts: 136
Joined: Thursday 19 July 2018 14:36
Target OS: -
Domoticz version: 2023.1
Contact:

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Post by Dave47 »

Did not work. "dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0"
Is that with " or only ' and /dev or dev?
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest