Domoticz

heggink wrote: ↑Wednesday 25 August 2021 14:18
I added quite a bit to the readme so it should be pretty close to a how to move from OZW. Let me know if this is good enough or whether anything is missing.

If you migrate from OZW, this will be a new plugin with new devices. Once you delete OZW in domoticz, your old devices are gone. If you need to retain history then you need to replace the old device with the new one if identical devices are created. New devices will be (automatically) added to domoticz (new names, new IDX) on the first status change.

heggink wrote: ↑Wednesday 25 August 2021 11:59

hestia wrote:Other questions:
In which way does it work? I've set a name for a node in the control panel (ZWave To MQTT) and it didn't arrive in domoticz. Do I have to do somethings?

Where are located the ZWave To MQTT data (and other stuff). To backup them...

The best way is to, before you install the plugin, name all your devices in zwavejs2mqtt. They will all then be created with that name in domoticz. I would need to check myself what happens if you change the name of an existing device in zwavejs2mqtt. Don't know really.
[...]

hestia wrote: ↑Wednesday 25 August 2021 18:06 Some answers to me
Control Panel / Actions / Advanced / Export => export the nodes with the the names

Code: Select all

{
  "1": {
    "name": "Z-Stick Gen5"
  },
  "11": {
    "name": "Portail SN 16056DR384 PN ZMNHSD1 H1S1P2"
  },
  "17": {
    "name": "Terrasse !!!!!"
  },
  "30": {
    "name": "Smart Plug HKZW-SO05"
  },

Control Panel / Actions / Advanced / Import => export the nodes withe the names.
So if I remove the container, I could do it several times
And also import it on the production env.

(if we could have the same export from dz, no need to do it manually!)

hestia wrote: ↑Wednesday 25 August 2021 17:57 I've copied/pasted the name off all the 37 nodes from dz to zwave.js2mqtt.
About 1/2 hours.
Do I push them right now in dz, or do I wait for a fix about the names of the other devices?

hestia wrote: ↑Wednesday 25 August 2021 18:46 Yes!
in the picture just above (18:34) some devices are created without the name set in zwavejs2mqtt.
It's Screenshot 2021-08-25 182854.png"random" because for a node, some devices are ok and others are ko
Also, possible to remove the "ZwaveMQTT" from the device name, not very user friendly

waltervl wrote: ↑Wednesday 25 August 2021 16:09

heggink wrote: ↑Wednesday 25 August 2021 14:18
I added quite a bit to the readme so it should be pretty close to a how to move from OZW. Let me know if this is good enough or whether anything is missing.

Perhaps for docker just refer to the docker installation manual https://github.com/zwave-js/zwavejs2mqt ... ter/docker
I miss for example the "Add -e TZ=Europe/Stockholm to the docker run command to set the correct timezone in container" note.
On that page there is also the reference to the docker-compose.yml

If you migrate from OZW, this will be a new plugin with new devices. Once you delete OZW in domoticz, your old devices are gone. If you need to retain history then you need to replace the old device with the new one if identical devices are created. New devices will be (automatically) added to domoticz (new names, new IDX) on the first status change.

I think you should warn not to use OZW and ZwaveJS together.
So a possible migration scenario:
1. Document current OZW/Domoticz configuration (How?)
2. Disable (or delete?) OZW from Domoticz. Reboot system or restart Domoticz
3. Install ZwaveJS2MQTT (Docker)
4. Install Plugin
5. Reboot system or restart Domoticz
6. Activate plugin and wait for all New devices to appear in Domoticz
7. Rename new devices to old names if used in scripts or modify scripts to use new names. If OZW was disabled, devices with the same name will give errors in dzVents so delete the old device from OZW after renaming the new device. Is function replace device (wiki https://www.domoticz.com/wiki/Managing_ ... ace_device )a good alternative method as it will also keep the device history logging if present.
8. Remove OZW hardware (if not done in step 2)

heggink wrote: ↑Thursday 26 August 2021 13:03 Difficult to say. There should be no need to pull any docker image since it should do that automatically when you issue "docker run".

The command you run subsequently (docker run --rm -it -p ...) starts the container in interactive mode with a terminal attached. Does it stop immediately or does it keep running (and you can access the web interface)? Is your device (/dev/ttyAMA0) the correct one (ie used by OZW)?

H

heggink wrote: ↑Thursday 26 August 2021 15:19 Ok, so you need to tell the docker container what device to map in the container and then you need to select that device from the zwavejs2mqtt web interface. If the correct device has been passed to the container, it should all work without a problem.


Sent from my SM-G980F using Tapatalk