OZW 1.6 RELEASED !!

[Doler]

...and it fails (https://www.domoticz.com/forum/viewtopi ... =6&t=27919)

[antwan]

No problems here with ...741

[emme]

1.6 messed up fibaro FGS222 double relay sqitch (2x1.5kW) that now show the parameters for the multisensor device

[Holland]

Just updated to 4.10751

And openzwave 1.6 returns the following

2019-05-14 21:38:23.826 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)
2019-05-14 21:38:33.013 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)
2019-05-14 21:38:33.203 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)
2019-05-14 21:38:33.393 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)

[Skippiemanz]

Just updated to 4.10751

And openzwave 1.6 returns the following

2019-05-14 21:38:23.826 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)
2019-05-14 21:38:33.013 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)
2019-05-14 21:38:33.203 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)
2019-05-14 21:38:33.393 Error: OpenZWave: Exception. Type: 102, Msg: ValueID passed to GetValueAsByte is not a Byte Value, File: /home/pi/open-zwave-read-only/cpp/src/Manager.cpp (Line 2192)

Same problem here.

It works thought but just some error messages.

[pvm]

I'm very happy the integration of 1.6 is ongoing, hope we get over the first issues soon. Thanks for putting in the effort

[JohnnyJohnny]

I am getting the Exception as well, while everything else work it seems to screw up a sensative strip I added, everytime I try activating the strip it notices it and tries to add it's devices, but then I get the exception and nothing is added. So I hope this can be sorted out.

[zedd]

Seems to be solved in Domoticz 4.10798.
Had the same errors from my sensitive strip, not anymore since this version.
Thanks!

[Gravityz]

i still get the same errors with 10798.
i am using the jumbotroll build for synology

[subtrEM]

Domoticz 4.10806 on Raspi 3.
Z-Stick AEON Gen 5

Qbino Smart Plug ZMNHYD1 not functional after upgrade to 4.10806 from latest stable: activating switch gives error dialog (check hardware), switches are no longer accessible, do not report status. Log file has many "Error: OpenZWave: Exception. Type: 102..." events logged.
Reverting to 4.10717 resolves that issue.

Edit: could this be related to https://github.com/OpenZWave/open-zwave/issues/1820?

[Piacco]

After the update from ozw from 1.4 to 1.6 the double click function of my fibaro FGD212 Dimmer 2+ is not working anymore
With the double click action i trigger a script, so that the lights in my house all go off. Could this be fixed in a update?

Piacco

[jake]

I finally dared to update Domoticz from the latest stable to the most recent beta, this because of the OZW 1.6 horror stories. To my surprise all devices were instant available, no fiddling by healing nodes etc:
FIBARO System FGWPE/F Wall Plug
FIBARO System FGMS001 Motion Sensor
Danfoss Popp Radiator Thermostat
FIBARO System FGS222 Double Relay Switch 2x1.5kW
Aeotec DSA02203 Z-Stick S2

well done!

[paolone919191]

after update from stable to latest beta... everything is broken for me. I needed to fall back to latest stable.

On domoticz, prior to the complete death, I can see the message:

"Not all Nodes have been Queried yet, OpenZWave not fully initialized yet!"

on Openzwave, I can see a lot of

2019-11-08 13:11:30.755 Error, ERROR: Not enough space in stream buffer
2019-11-08 13:11:30.756 Always,
2019-11-08 13:11:30.756 Always, Dumping queued log messages
2019-11-08 13:11:30.756 Always,
2019-11-08 13:11:30.756 Always,
2019-11-08 13:11:30.756 Always, End of queued log message dump
2019-11-08 13:11:30.756 Always,

in my house I have an AEON Labs ZW090 Z-Stick Gen5 EU gateway, some eurotronics SPIRITZ valves and 3 zwave repeaters.

[wawrion]

Am I the only one having empty OZW control panel? I am having that due to some....

Does anyone know how to solve that issue?