domoticz in synology as package! Available now.

[Gravityz]

thanks. no hurry and enjoy your sunday night

[gbuico]

@jumbotroll

Hi jumbotroll ... sorry if this may be a silly question but... I'm an old user of Domoticz on Raspberry and since a month I'm running your version on my Synology DS218j and,,, it's just great.
Now version 10717 is out and you aligned very quickly... but... what is the right procedure for the upgrade?
In a very simplicistic way I tried to use the normal update process from the Domoticz menu... I hope I did not corrupt anything in my Synology because it goes to the end of the update in a smooth and successful way... but then I still have the old version.
Can you be so kind an give me whatever advice?
Thanks for your work anyway
Giacomo

DSM 6.2

If your prev version is very old, you have to uninstall domoticz from package center, before you install the new version.
Most of the time, you only have to install over the old version.
Remember to take backup of domoticz database and if you have scripts or plugins.
I have never heard of any corrupt synology after installing these packages, so don't worry

Thanks for reassuring me... I was a little worried
To say the truth, I installed your package about a month ago, so I'm just upgrading from the last version
https://drive.google.com/file/d/1yRlRiV ... sp=sharing
The image above shows what I have on my screen before and after the update.
So, I start from version 4.9700 and it tells me that version 10717 is available.
I just press "Install now" and it first downloads, then installs the new version... and at the end it tells me that he is going to restart.
When the restart is finished I come again to this page.... again telling me that there is an update.
I think at this point I may uninstall/install but if you want I can do whatever test you need and may contribute.
Thanks for the quick answer you gave me

Giacomo

[jumbotroll]

Thanks for reassuring me... I was a little worried
To say the truth, I installed your package about a month ago, so I'm just upgrading from the last version
https://drive.google.com/file/d/1yRlRiV ... sp=sharing
The image above shows what I have on my screen before and after the update.
So, I start from version 4.9700 and it tells me that version 10717 is available.
I just press "Install now" and it first downloads, then installs the new version... and at the end it tells me that he is going to restart.
When the restart is finished I come again to this page.... again telling me that there is an update.
I think at this point I may uninstall/install but if you want I can do whatever test you need and may contribute.
Thanks for the quick answer you gave me

Giacomo

You can't update that way on synology!
You have to manually download the package and install in synology package center.
Download from my website http://www.jadahl.com/domoticz_stable_6.2/

Read wiki https://www.domoticz.com/wiki/Synology

[gbuico]

Silly me... I searched everywhere except the most obvious place.
I hope I didn't mess up by attempting that silly way of updating.
May be I should uninstall/install to be on the safe side...
Thanks again jumbotroll

Giacomo

[Gravityz]

tested v 740 but it seems to crash.

is starts but then stops again.

since i was about to go to bed i had to deinstall previous version and reinstall older version.

so probably zwave 1.6 related i think.

i can try again tomorrow but let me know where to look for errors

[jumbotroll]

tested v 740 but it seems to crash.

is starts but then stops again.

since i was about to go to bed i had to deinstall previous version and reinstall older version.

so probably zwave 1.6 related i think.

i can try again tomorrow but let me know where to look for errors

Running ok here, but only use 2 Zwave devices.

2019-05-12 20:42:29.663 Status: Domoticz V4.10740 (c)2012-2019 GizMoCuz
2019-05-12 20:42:29.663 Status: Build Hash: 34b73c1-modified, Date: 2019-05-12 18:47:31
2019-05-12 20:42:29.664 Status: Startup Path: /usr/local/domoticz/
2019-05-12 20:42:30.222 Status: PluginSystem: Started, Python version '3.5.1'.
2019-05-12 20:42:30.223 Status: Philips Hue: Using default poll interval of 10 secs.
2019-05-12 20:42:30.274 Status: WebServer(HTTP) started on address: :: with port 8084
2019-05-12 20:42:30.282 Status: WebServer(SSL) started on address: :: with port 8443
2019-05-12 20:42:30.289 Status: TCPServer: shared server started...
2019-05-12 20:42:30.289 Status: RxQueue: queue worker started...
2019-05-12 20:42:32.300 Status: Hardware Monitor: Started
2019-05-12 20:42:32.320 Status: Pinger: Worker started...
2019-05-12 20:42:32.326 Status: Philips Hue: Worker started...
2019-05-12 20:42:32.327 Status: RFXCOM: Worker started...
2019-05-12 20:42:32.331 Status: EventSystem: reset all events...
2019-05-12 20:42:32.332 Status: EventSystem: reset all device statuses...
2019-05-12 20:42:32.385 Status: PluginSystem: Entering work loop.
2019-05-12 20:42:32.709 Status: Python EventSystem: Initalizing event module.
2019-05-12 20:42:32.718 Status: EventSystem: Queue thread started...
2019-05-12 20:42:32.723 Status: EventSystem: Started
2019-05-12 20:42:32.823 Status: OpenZWave: using config in: /usr/local/domoticz/Config/
2019-05-12 20:42:32.892 Status: OpenZWave: Starting...
2019-05-12 20:42:32.892 Status: OpenZWave: Version: 1.6-158-ge4fb59d5-dirty
2019-05-12 20:42:33.343 Status: RFXCOM: Using serial port: /dev/ttyUSB0
2019-05-12 20:42:34.001 Status: RFXCOM: Async Disabled
2019-05-12 20:42:39.685 Status: OpenZWave: ManufacturerSpecificDB Ready
2019-05-12 20:42:39.920 Status: OpenZWave: Driver Ready
2019-05-12 20:42:40.007 Status: OpenZWave: Unhandled class: 0x2B (SCENE ACTIVATION), NodeID: 2 (0x02), Index: 0, Instance: 1
2019-05-12 20:42:40.007 Status: OpenZWave: Unhandled class: 0x2B (SCENE ACTIVATION), NodeID: 2 (0x02), Index: 1, Instance: 1
2019-05-12 20:42:41.158 Status: OpenZWave: All Nodes queried

[gbuico]

Hi @jumbotroll … me again
Am I mistaken or in the installation page of your site there is no 10717 version available for DS218J ?
Thanks again

Giacomo

[jumbotroll]

Hi @jumbotroll … me again
Am I mistaken or in the installation page of your site there is no 10717 version available for DS218J ?
Thanks again

Giacomo

The list was not updated, should be ok now
DS218j use arch-armada38x

[Gravityz]

tried again.
this time i installed v4.10741
That version seems to work.

i got some startup error messsages but i think these do not matter

@GizMoCuz

Here is the log in case these errors matter
should i enable new hardware, delete the zwcfg file and let it recreate for new devices?

Code: Select all

2019-05-13 16:05:34.927 Status: Domoticz V4.10741 (c)2012-2019 GizMoCuz
2019-05-13 16:05:34.927 Status: Build Hash: 320cc8a-modified, Date: 2019-05-13 11:28:11
2019-05-13 16:05:34.927 Status: Startup Path: /usr/local/domoticz/
2019-05-13 16:05:35.531 Status: Philips Hue: Using poll interval of 1 secs.
2019-05-13 16:05:35.536 Status: WebServer(HTTP) started on address: :: with port 8084
2019-05-13 16:05:35.539 Status: WebServer(SSL) started on address: :: with port 8443
2019-05-13 16:05:35.541 Status: Camera: settings (re)loaded
2019-05-13 16:05:35.541 Status: TCPServer: shared server started...
2019-05-13 16:05:35.541 Status: RxQueue: queue worker started...
2019-05-13 16:05:37.542 Status: Hardware Monitor: Started
2019-05-13 16:05:37.546 Status: Philips Hue: Worker started...
2019-05-13 16:05:37.546 Status: RFXCOM: Worker started...
2019-05-13 16:05:37.547 Status: EventSystem: reset all events...
2019-05-13 16:05:37.548 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-Woonkamerlampen.lua
2019-05-13 16:05:37.548 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-Tuinsproeier.lua
2019-05-13 16:05:37.548 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-Zonneschermen-in.lua
2019-05-13 16:05:37.548 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-P1 meter.lua
2019-05-13 16:05:37.549 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-Woonkamer-lux.lua
2019-05-13 16:05:37.549 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-P1 meter-telegram.lua
2019-05-13 16:05:37.549 Status: dzVents: Write file: /usr/local/domoticz/var/scripts/dzVents/generated_scripts/global_data.lua
2019-05-13 16:05:37.549 Status: EventSystem: reset all device statuses...
2019-05-13 16:05:37.581 Status: EventSystem: Started
2019-05-13 16:05:37.581 Status: EventSystem: Queue thread started...
2019-05-13 16:05:38.046 Status: OpenZWave: using config in: /usr/local/domoticz/Config/
2019-05-13 16:05:38.055 Status: OpenZWave: Starting...
2019-05-13 16:05:38.055 Status: OpenZWave: Version: 1.6-158-ge4fb59d5-dirty
2019-05-13 16:05:38.547 Status: MQTT: Connecting to localhost:1883
2019-05-13 16:05:38.558 Status: RFXCOM: Using serial port: /dev/ttyUSB0
2019-05-13 16:05:38.649 Status: MQTT: connected to: localhost:1883
2019-05-13 16:05:38.749 Status: MQTT: Subscribed
2019-05-13 16:05:39.108 Status: P1 Smart Meter: Meter reports as DSMR 5.0
2019-05-13 16:05:39.185 Status: P1 Smart Meter: Found gas meter on M-Bus channel 1
2019-05-13 16:05:39.229 Status: OpenZWave: ManufacturerSpecificDB Ready
2019-05-13 16:05:39.269 Status: RFXCOM: Async mode set to: 'DSMR 4/5'
2019-05-13 16:05:39.397 Status: OpenZWave: Driver Ready
2019-05-13 16:05:39.398 Status: OpenZWave: New Node added. HomeID: 3467119363, NodeID: 1 (0x01)
2019-05-13 16:05:39.398 Status: OpenZWave: New Node added. HomeID: 3467119363, NodeID: 8 (0x08)
2019-05-13 16:05:39.398 Status: OpenZWave: New Node added. HomeID: 3467119363, NodeID: 11 (0x0b)
2019-05-13 16:05:39.398 Status: OpenZWave: New Node added. HomeID: 3467119363, NodeID: 16 (0x10)
2019-05-13 16:05:39.398 Status: OpenZWave: New Node added. HomeID: 3467119363, NodeID: 17 (0x11)
2019-05-13 16:05:39.398 Status: OpenZWave: New Node added. HomeID: 3467119363, NodeID: 18 (0x12)
[b]2019-05-13 16:05:40.530 Status: OpenZWave: Unhandled class: 0x2B (SCENE ACTIVATION), NodeID: 8 (0x08), Index: 0, Instance: 1
2019-05-13 16:05:40.530 Status: OpenZWave: Unhandled class: 0x2B (SCENE ACTIVATION), NodeID: 8 (0x08), Index: 1, Instance: 1[/b]
[b]2019-05-13 16:05:40.077 Error: OpenZWave: Exception, Invalid ValueID passed to GetValueLabel
2019-05-13 16:05:40.077 Error: OpenZWave: Exception, Invalid ValueID passed to GetValueLabel[/b]
2019-05-13 16:05:41.266 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Unknown, Instance: 1
2019-05-13 16:05:44.304 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 8 (0x08)
[b]2019-05-13 16:05:44.589 Error: OpenZWave: Exception, Invalid ValueID passed to GetValueLabel
2019-05-13 16:05:44.589 Error: OpenZWave: Exception, Invalid ValueID passed to GetValueLabel
2019-05-13 16:05:44.589 Error: OpenZWave: Exception, Invalid ValueID passed to GetValueLabel[/b]
2019-05-13 16:05:49.291 (RFXtrx433XL) P1 Smart Meter (Energie)
2019-05-13 16:05:49.294 (RFXtrx433XL) General/Voltage (Voltage)
2019-05-13 16:05:49.295 (RFXtrx433XL) Usage (Verbruik L1)
2019-05-13 16:05:49.296 (RFXtrx433XL) Usage (Verbruik L2)
2019-05-13 16:05:50.216 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 17 (0x11)
2019-05-13 16:05:53.253 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 18 (0x12)
2019-05-13 16:05:56.493 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Step Size, Instance: 2
2019-05-13 16:05:56.493 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Inc, Instance: 2
2019-05-13 16:05:56.493 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Dec, Instance: 2
2019-05-13 16:05:56.493 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Level, Instance: 2
2019-05-13 16:05:56.493 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Bright, Instance: 2
2019-05-13 16:05:56.493 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Dim, Instance: 2
2019-05-13 16:05:56.783 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
2019-05-13 16:05:57.185 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: METER, Label: Power, Instance: 1
2019-05-13 16:05:59.295 (RFXtrx433XL) P1 Smart Meter (Energie)
2019-05-13 16:05:59.298 (RFXtrx433XL) General/Voltage (Voltage)
2019-05-13 16:05:59.301 (RFXtrx433XL) Usage (Verbruik L1)
2019-05-13 16:05:59.303 (RFXtrx433XL) Usage (Verbruik L2)
2019-05-13 16:05:59.667 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: ALARM, Label: Instance 1: Previous Event Cleared, Instance: 1
2019-05-13 16:05:59.667 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: ALARM, Label: Instance 1: Power Management, Instance: 1
2019-05-13 16:05:59.903 (RFXtrx433XL) Temp (Slaapkamer)
2019-05-13 16:05:59.667 Status: OpenZWave: Value_Added: Unhandled Label: Instance 1: Previous Event Cleared, Unit:
2019-05-13 16:05:59.667 Status: OpenZWave: Value_Added: Unhandled Label: Instance 1: Power Management, Unit:
2019-05-13 16:06:00.897 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: ALARM, Label: Instance 2: Previous Event Cleared, Instance: 2
2019-05-13 16:06:00.897 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: ALARM, Label: Instance 2: Power Management, Instance: 2
2019-05-13 16:06:00.131 Status: EventSystem: Script event triggered: /usr/local/domoticz/dzVents/runtime/dzVents.lua
2019-05-13 16:06:00.456 Status: Incoming connection from: 192.168.1.1
2019-05-13 16:06:00.897 Status: OpenZWave: Value_Added: Unhandled Label: Instance 2: Previous Event Cleared, Unit:
2019-05-13 16:06:00.897 Status: OpenZWave: Value_Added: Unhandled Label: Instance 2: Power Management, Unit:
2019-05-13 16:06:08.500 (RFXtrx433XL) Temp (Tuin)
2019-05-13 16:06:08.815 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2019-05-13 16:06:08.935 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: METER, Label: Power, Instance: 1
2019-05-13 16:06:09.295 (RFXtrx433XL) P1 Smart Meter (Energie)
2019-05-13 16:06:09.298 (RFXtrx433XL) General/Voltage (Voltage)
2019-05-13 16:06:09.299 (RFXtrx433XL) Usage (Verbruik L1)
2019-05-13 16:06:09.301 (RFXtrx433XL) Usage (Verbruik L2)
2019-05-13 16:06:09.363 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1
2019-05-13 16:06:09.363 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: ALARM, Label: Power Management, Instance: 1
2019-05-13 16:06:09.363 Status: OpenZWave: Value_Added: Unhandled Label: Previous Event Cleared, Unit:
[b]2019-05-13 16:06:09.363 Error: OpenZWave: Exception, ValueID passed to GetValueAsByte is not a Byte Value[/b]
2019-05-13 16:06:13.233 (RFXtrx433XL) Temp (Slaapkamer Ryan)
2019-05-13 16:06:15.850 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2019-05-13 16:06:15.887 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Power, Instance: 1
2019-05-13 16:06:15.998 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1
2019-05-13 16:06:15.999 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: ALARM, Label: Power Management, Instance: 1
2019-05-13 16:06:15.521 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 17 (0x11)
2019-05-13 16:06:15.999 Status: OpenZWave: Value_Added: Unhandled Label: Previous Event Cleared, Unit:
[b]2019-05-13 16:06:15.999 Error: OpenZWave: Exception, ValueID passed to GetValueAsByte is not a Byte Value[/b]
2019-05-13 16:06:17.826 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: METER, Label: Power, Instance: 1
2019-05-13 16:06:17.977 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1
2019-05-13 16:06:17.978 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: ALARM, Label: Heat, Instance: 1
2019-05-13 16:06:17.977 Status: OpenZWave: Value_Added: Unhandled Label: Previous Event Cleared, Unit:
[b]2019-05-13 16:06:17.978 Error: OpenZWave: Exception, ValueID passed to GetValueAsByte is not a Byte Value[/b]
2019-05-13 16:06:18.015 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: ALARM, Label: Power Management, Instance: 1
2019-05-13 16:06:18.053 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: ALARM, Label: System, Instance: 1
[b]2019-05-13 16:06:18.016 Error: OpenZWave: Exception, ValueID passed to GetValueAsByte is not a Byte Value
2019-05-13 16:06:18.054 Error: OpenZWave: Exception, ValueID passed to GetValueAsByte is not a Byte Value[/b]
2019-05-13 16:06:19.284 (RFXtrx433XL) P1 Smart Meter (Energie)
2019-05-13 16:06:19.286 (RFXtrx433XL) General/Voltage (Voltage)
2019-05-13 16:06:19.288 (RFXtrx433XL) Usage (Verbruik L1)
2019-05-13 16:06:19.290 (RFXtrx433XL) Usage (Verbruik L2)
2019-05-13 16:06:20.823 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: METER, Label: Energy, Instance: 1
2019-05-13 16:06:20.825 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Tuinlampen)
2019-05-13 16:06:21.257 (Aeonlabs Z-wave stick Gen5) Usage (Watt Tuinlampen)
2019-05-13 16:06:21.260 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Tuinlampen)
2019-05-13 16:06:24.691 (Aeonlabs Z-wave stick Gen5) Usage (Watt Tuinsproeier)
2019-05-13 16:06:24.692 (Aeonlabs Z-wave stick Gen5) Usage (Power Meter pomp)
2019-05-13 16:06:24.813 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: METER, Label: Energy, Instance: 1
2019-05-13 16:06:24.815 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Tuinsproeier)
2019-05-13 16:06:24.966 (Aeonlabs Z-wave stick Gen5) Usage (Unknown3)
2019-05-13 16:06:24.969 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Tuinsproeier)
2019-05-13 16:06:24.257 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 17 (0x11)
2019-05-13 16:06:28.230 (Aeonlabs Z-wave stick Gen5) Usage (Watt Vitrinekast)
2019-05-13 16:06:28.230 (Aeonlabs Z-wave stick Gen5) Usage (Power Meter)
2019-05-13 16:06:28.267 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Energy, Instance: 1
2019-05-13 16:06:28.269 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Vitrinekast)
2019-05-13 16:06:28.305 (Aeonlabs Z-wave stick Gen5) Usage (Unknown2)
2019-05-13 16:06:28.308 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Vitrinekast)
2019-05-13 16:06:28.527 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Level, Instance: 2
2019-05-13 16:06:28.564 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2019-05-13 16:06:28.566 (Aeonlabs Z-wave stick Gen5) Usage (Watt Plafondspots)
2019-05-13 16:06:28.567 (Aeonlabs Z-wave stick Gen5) Usage (Power Meter)
2019-05-13 16:06:28.603 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: METER, Label: Energy, Instance: 1
2019-05-13 16:06:28.605 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Plafondspots)
2019-05-13 16:06:28.643 (Aeonlabs Z-wave stick Gen5) Usage (Unknown)
2019-05-13 16:06:28.646 (Aeonlabs Z-wave stick Gen5) General/kWh (kWh Plafondspots)
2019-05-13 16:06:28.119 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 18 (0x12)
2019-05-13 16:06:28.737 Status: OpenZWave: Awake Nodes queried

[Gravityz]

it seems after zwave v1.6 implementation the HW configuration info of most devices is totally wrong
it looks like it is using motion sensor settings for every device.

i did delete the zwcfg file and let it recreate without succes.
also copying the old zwave config files and let it recreate did not work.

i found out because HW scenes on my FGD212 did not work anymore

The only file which seems correct is the FGMS001-ZW5


ZMNHADx

ZMNHADx.JPG (193.02 KiB) Viewed 2500 times

FGWPF

fgwpf.JPG (187.8 KiB) Viewed 2500 times

FGD212

fgd212.JPG (159.51 KiB) Viewed 2500 times

[Gravityz]

@jumbotroll

i would wait with compiling new beta builds unless somebody needs them for testing purposes
there seems to be a lot of problems regarding the new zwave v1.6 version.

the problem is affecting modules and config settings also so i think not an easy fix.

i am sticking with build 734 (openzwave v1.4) for now.

[olebpoulsen]

Version: 4.10717 upgrade from 4.9700
Device:ZHC5010 wall switch

After update to 10717 Domoticz switches a second switch when one switch of four belonging to the ZHC5010 device is toggled from within Domoticz. More details on this post viewtopic.php?f=6&t=27934#p214459
2019-05-14 18:13:04.947 OpenZWave: Domoticz has send a Switch command! NodeID: 12 (0x0c)
2019-05-14 18:13:04.951 (Z-stick) Light/Switch (KS4)
2019-05-14 18:13:04.998 (Z-stick) Light/Switch (KS3)
2019-05-14 18:13:04.946 Status: User: Admin initiated a switch command (313/KS4/On)
Anyone please.

[bruch05]

Hello Jumbotroll,

Since the update to

Version: 4.10742
Build Hash: 0a29291-modified
Compile Date: 2019-05-13 13:20:40
dzVents Version: 2.4.20
Python Version: None

the device updates are not performed from z-wave stack. The debug mode shows this message.

2019-05-15 20:39:03.787 Detail, Node016, Notification: ValueChanged
2019-05-15 20:39:03.787 [7fb7ceffd700] OpenZWave: Value_Added: Node: 16 (0x10), CommandClass: SENSOR MULTILEVEL, Label: Instance 2: Temperature, Instance: 2
2019-05-15 20:39:03.787 [7fb7ceffd700] Status: OpenZWave: Value_Added: Unhandled Label: Instance 2: Temperature, Unit: C
2019-05-15 20:39:03.807 Detail, Node016, Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x10, 0x0c, 0x60, 0x0d, 0x05, 0x05, 0x31, 0x05, 0x01, 0x44, 0xff, 0xff, 0xf4, 0x61, 0x7c

Thx by advance for your help.
Regards
Christophe

[Gravityz]

i think everybody should stop installing the latest versions
serious problems because of zwave v1.6

unless you know what you are doing go back to version 717 or 734

this is not caused by jumbotroll but by the latest builds on github.

trust me, you do not want to test out versions unless you really know what you are doing and know how to make backups and downgrade to earlier versions

i am sticking with 734 unless somebody asks me to test out new versions

@jumbotroll, better block those versions after 734(using zwave v1.6)

[bruch05]

Hello Gravtiz, All,

i've another instance of Domoticz with this version without trouble.

Version: 4.10734
Build Hash: 3ac5b23-modified
Compile Date: 2019-05-12 08:06:25
dzVents Version: 2.4.19
Python Version: None

What is the best way to rollback the previous version, i've attemped to install stable APK, but the Syno refuse to install a previous version.

Thx
Christophe

[bruch05]

Hello,

Restoration of domoticz.tar.gz to previous version works fine.

Christophe

[bruch05]

Hello,

The upgrade to

Version: 4.10763
Build Hash: 792e9a6-modified
Compile Date: 2019-05-16 09:00:25
dzVents Version: 2.4.20
Python Version: None

solves the issue.

Thx JumbroTroll
Christophe

[Gravityz]

@jumbotroll
i installed v785, much better but still there are some errors

are these related to the way you build the packages or is it related to a zwave module

Code: Select all

2019-05-18 19:50:10.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:10.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:11.141 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: METER, Label: Unknown, Instance: 1
2019-05-18 19:50:11.141 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SCENE ACTIVATION, Label: Scene, Instance: 1
2019-05-18 19:50:11.141 OpenZWave: Value_Added: Node: 8 (0x08), CommandClass: SCENE ACTIVATION, Label: Duration, Instance: 1
2019-05-18 19:50:11.295 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: METER, Label: Unknown, Instance: 1
2019-05-18 19:50:11.495 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: METER, Label: Unknown, Instance: 1
2019-05-18 19:50:11.601 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Unknown, Instance: 1
2019-05-18 19:50:11.141 Status: OpenZWave: Unhandled class: 0x2B (SCENE ACTIVATION), NodeID: 8 (0x08), Index: 0, Instance: 1
2019-05-18 19:50:11.142 Status: OpenZWave: Unhandled class: 0x2B (SCENE ACTIVATION), NodeID: 8 (0x08), Index: 1, Instance: 1
2019-05-18 19:50:14.639 Status: OpenZWave: Received timeout notification from HomeID: 3467119363, NodeID: 8 (0x08)
2019-05-18 19:50:14.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:14.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:14.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)

2019-05-18 19:50:10.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:10.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:14.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:14.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)
2019-05-18 19:50:14.786 Error: OpenZWave: Exception. Type: 101, Msg: Invalid ValueID passed to GetValueLabel, File: /home/dahl/spksrc-master/spk/domoticz/work-apollolake-6.2/open-zwave-read-only/cpp/src/Manager.cpp (Line 1768)

[jumbotroll]

@jumbotroll
i installed v785, much better but still there are some errors
are these related to the way you build the packages or is it related to a zwave module

There is no another way for me to crosscompile openzwave, so I think it is related to a zwave module..

[Gravityz]

ok thanks Jumbotroll.

i already posted the problems on github
one is related to the earthquake sensor inside the fgms-001 which never worked in 1.4 and thus not on 1.6

The other one is related to scene functionality which is available and working in 1.4 but apparently not in 1.6.

can you create a new build with todays changes so i can do a test again?

questions regarding restoring:
i always go back to a previous working backup instead of restoring let's say a 785 build backup to a 734 version
is this true or does it not matter as long as the HW devices have not changed in the newer build (eg accept new hardware is always off)