Domoticz migration from x32 to x64 ubuntu 18.04 fails on ZWave

[gbonny]

Hello,

I'm currently running Domoticz v4.10726 (OZW 1.4-3335-g74e05982-dirty) on Ubuntu 18.04 x32 in a VM with 3 USB devices (Z-Wave/RFX-433/P1-meter), OWM, SolarEdge API, Panasonic TV, Kodi and Philips Hue.

Recently I created a new VM with Ubuntu 18.04 x64 and installed the Stable Linux tar file v4.10717 (OZW 1.4-3335-g74e05982-dirty) from the download page of domoticz.com
I've created a seperate user domoticz (previously I used root), granted access to the ttyUSB*, added again sendxmpp option and so on.

Today I exported the database from my x32 VM and imported it into the x64 VM. Did a reboot of the x64 VM. All worked perfectly out in Domoticz and resumes like SolarEdge, RFX-433, P1-meter etc. except for the ZWave part. The ZWave devices are populated but manufacturer and the + sign for ZWave+ don't appear on the nodes page.

When a door/window sensor (Vision) is triggered "last seen" is updated on the ZWave & devices page except for the status open/closed on the dashboard/switches panels/tabs. Same for wall plugs (Fibaro). I cannot trigger the smoke and temp/hum sensors. However only two temp/hum sensors (Philio) got updated status on the temperature panel/tab.

What I've done so far:
- I let it to run for a couple of hours;
- Did a ZWave network heal a couple of times;
- Did a ZWave node reset for each device;
- Upgraded to non-stable/beta v4.11334 with OZW 1.6;
- Checked the log for errors;
- Double checked the ZWave network security key.

When I shutdown the x64 VM and spin the x32 VM back up, all ZWave devices are restored in a couple of minutes. Also the "manufacturer" column and the Zwave "+" sign are populated nearly instantly in nodes.

What do I do wrong / what did I miss / can someone help me? Thanks
Btw, FWIW I'm running those VM's on ESXi 6.7 update 3.

[ben53252642]

Did you try copying the entire Domoticz directory instead of just the database?

I'm thinking try that and then possibly upgrade the x64 over the top of the x32 Domoticz installation.

[gbonny]

Did you try copying the entire Domoticz directory instead of just the database?

I'm thinking try that and then possibly upgrade the x64 over the top of the x32 Domoticz installation.

No, I haven't tried that yet.

Meanwhile this morning I powered off my x32 and powered on x64 VM and I've checked and corrected the permissions in /home/domoticz/domoticz, some files/folders were 2000:2000 (?!)
So I did "sudo chown -R domoticz:domoticz /home/domoticz/domoticz/". All permissions seems to be perfect now.

For two of my window/door sensor the status is now updated on the switches panel/tab! My other 20 ZWave+ devices are still not updated. Did a reboot after the permissions change as well.


Btw, these are my tty settings on both x32 and x64 VMs.
RFXCOM: /dev/ttyUSB0
P1 meter: /dev/ttyUSB1
Zwave.me: /dev/ttyACM0

I did "sudo usermod -a -G dialout domoticz"
Is ttyACM0 also a "dialout" device?


I found these messages in the log files:
Settings > Log > Status

Spoiler: show

2019-10-17 10:16:16.701 Status: OpenZWave: using config in: /home/domoticz/domoticz/Config/
2019-10-17 10:16:16.706 Status: OpenZWave: Starting...
2019-10-17 10:16:16.706 Status: OpenZWave: Version: 1.4-3335-g74e05982-dirty
2019-10-17 10:16:16.991 Status: OpenZWave: Driver Ready
2019-10-17 10:16:17.228 Status: RFXCOM: Using serial port: /dev/ttyUSB0
2019-10-17 10:16:17.442 Status: P1 Smart Meter: Meter reports as DSMR 5.0
2019-10-17 10:16:17.442 Status: P1 Smart Meter: Found gas meter on M-Bus channel 1
2019-10-17 10:16:22.703 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 43 (0x2b)
2019-10-17 10:16:25.704 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 44 (0x2c)
2019-10-17 10:16:28.705 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 45 (0x2d)
2019-10-17 10:16:31.795 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 44 (0x2c)
2019-10-17 10:16:34.810 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 42 (0x2a)
2019-10-17 10:16:37.810 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 43 (0x2b)
2019-10-17 10:16:40.822 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 31 (0x1f)
2019-10-17 10:16:43.822 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 31 (0x1f)
2019-10-17 10:16:46.823 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 31 (0x1f)
2019-10-17 10:16:49.823 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 32 (0x20)
2019-10-17 10:16:52.824 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 32 (0x20)
2019-10-17 10:16:55.824 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 32 (0x20)
2019-10-17 10:16:58.824 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 33 (0x21)
2019-10-17 10:17:01.826 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 33 (0x21)
2019-10-17 10:17:04.828 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 34 (0x22)
2019-10-17 10:17:07.830 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 34 (0x22)
2019-10-17 10:17:10.832 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 36 (0x24)
2019-10-17 10:17:13.877 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 45 (0x2d)
2019-10-17 10:17:16.878 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 45 (0x2d)
2019-10-17 10:17:19.879 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 44 (0x2c)
2019-10-17 10:17:22.882 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 44 (0x2c)
2019-10-17 10:17:24.343 Status: OpenZWave: Awake Nodes queried
2019-10-17 10:18:21.576 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 24 (0x18)
2019-10-17 10:18:31.945 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 24 (0x18)
2019-10-17 10:18:34.946 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 24 (0x18)
2019-10-17 10:18:38.553 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 24 (0x18)
2019-10-17 10:19:00.328 Status: Notification: Raamcontact Open
2019-10-17 10:21:20.609 Status: OpenZWave: Heal Network command initiated...
2019-10-17 10:22:09.931 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 32 (0x20)
2019-10-17 10:22:19.896 Status: OpenZWave: Received timeout notification from HomeID: 0022130300, NodeID: 43 (0x2b)

OZW_Log.txt

Spoiler: show

domoticz2:~$ cat /home/domoticz/domoticz/Config/OZW_Log.txt
2019-10-17 10:16:16.706 Always, OpenZwave Version 1.4.3335 Starting Up
2019-10-17 10:16:22.703 Error, Node043, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 10:16:22.703 Always,
2019-10-17 10:16:22.703 Always, Dumping queued log messages
2019-10-17 10:16:22.703 Always,
2019-10-17 10:16:22.703 Always,
2019-10-17 10:16:22.703 Always, End of queued log message dump
2019-10-17 10:16:22.703 Always,
2019-10-17 10:16:25.704 Error, Node044, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 10:16:25.704 Always,
2019-10-17 10:16:25.704 Always, Dumping queued log messages
2019-10-17 10:16:25.704 Always,
2019-10-17 10:16:25.704 Always,
2019-10-17 10:16:25.704 Always, End of queued log message dump
2019-10-17 10:16:25.704 Always,
2019-10-17 10:16:25.712 Error, Node045, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-10-17 10:16:25.712 Always,
2019-10-17 10:16:25.713 Always, Dumping queued log messages
2019-10-17 10:16:25.713 Always,
2019-10-17 10:16:25.713 Always,
2019-10-17 10:16:25.713 Always, End of queued log message dump
2019-10-17 10:16:25.713 Always,
2019-10-17 10:16:28.705 Error, Node045, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 10:16:28.705 Always,
2019-10-17 10:16:28.705 Always, Dumping queued log messages
2019-10-17 10:16:28.705 Always,
2019-10-17 10:16:28.705 Always,
2019-10-17 10:16:28.705 Always, End of queued log message dump
2019-10-17 10:16:28.705 Always,
2019-10-17 10:16:28.802 Error, Node044, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-10-17 10:16:28.802 Always,
2019-10-17 10:16:28.802 Always, Dumping queued log messages
2019-10-17 10:16:28.802 Always,
2019-10-17 10:16:28.802 Always,
2019-10-17 10:16:28.802 Always, End of queued log message dump
2019-10-17 10:16:28.802 Always,
2019-10-17 10:16:31.794 Error, Node044, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-17 10:16:31.795 Always,
2019-10-17 10:16:31.795 Always, Dumping queued log messages
2019-10-17 10:16:31.795 Always,
2019-10-17 10:16:31.795 Always,
2019-10-17 10:16:31.795 Always, End of queued log message dump
2019-10-17 10:16:31.795 Always,

Are these normal messages?

[gbonny]

Hmm.. I see similar messages in OZW_Log.txt on my x32 VM.

[gbonny]

I compared all files on both VM's. There were a lot of differences since the x32 is compiled from source.

However I found one notable file on the x32 VM which is missing on the x64 VM:

Code: Select all

134251 -rw-r-----  1 root   root      21891 May 18 21:19 ozwcp.poll.XXXXXX.xml

What is it for? The modify date is a while ago.. It contains a lot of information about my ZWave network.

[gbonny]

Btw, these are my tty settings on both x32 and x64 VMs.
RFXCOM: /dev/ttyUSB0
P1 meter: /dev/ttyUSB1
Zwave.me: /dev/ttyACM0

I did "sudo usermod -a -G dialout domoticz"
Is ttyACM0 also a "dialout" device?

I found myself an answer:

Code: Select all

domoticz2:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Oct 17 11:44 /dev/ttyACM0

[gbonny]

I've fixed a Python error based on the log file:

Code: Select all

sudo apt-get install libpython3.6-dev

But still the zwave sensors aren't adopted.. are there any other (OZW) requirements?

[gbonny]

I think I've figured it out, I've copied the contents of the zwcfg_0x......xml file from the x32 VM to the x64 VM. Now Z-Wave seems to be fully working!