OZW 1.6 RELEASED !!

[Ricard1]

Yeehaa... better than Christmas, way better!

https://groups.google.com/forum/#!topic ... 26mAKMam58

The 1.6 version will improve Z-Wave functionality and stability a lot for all Domoticz Z-Wave users.

Big thanks Justin Hammond and all Contributors at OpenZWave!!

Kind regards,
Ricard

[pvm]

Nice, but this is not yet integrated into Domoticz is it?

[dressie]

What does this mean for Domoticz? Is it necessary to install this or does the new stable has this already on board?

Verstuurd vanaf mijn SM-G950F met Tapatalk

[waaren]

[WARNING] make sure you backup your current libopenzwave.a before trying this. You will need this file in open-zwave-read-only directory to complete a successful creation of domoticz executable from source.

I just tried to compile /link domoticz from source on my RPI (Debian stretch) with the new OZW version (got it with git pull). Created the new libopenzwave.a with make and then did a make in the domoticz source directory.

During the link step I get

Code: Select all

BasicWindowCovering.cpp:undefined reference to `OpenZWave::Node::CreateValueButton(OpenZWave::ValueID...
Group.cpp:undefined reference to `OpenZWave::Node::GetCommandClass(unsigned char) const'
OpenZWave.cpp:undefined reference to `OpenZWave::Manager::GetValueHelp[abi:cxx11](OpenZWave::ValueID const&)'
OpenZWave.cpp:undefined reference to `OpenZWave::Manager::GetValueLabel[abi:cxx11](OpenZWave::ValueID const&)'
ozwcp.cpp:undefined reference to `OpenZWave::Manager::GetValueHelp[abi:cxx11](OpenZWave::ValueID const&)'
ozwcp.cpp:undefined reference to `OpenZWave::Manager::GetValueLabel[abi:cxx11](OpenZWave::ValueID const&)'

After restoring the 'old' libopenzwave.a , the link process works without problems and domoticz is created.

[gcoupe]

Thanks, but I'll wait until this has been integrated into a stable version of Domoticz. The risk of destroying my production version of Domoticz is too high for me.

[Ricard1]

Hi all!

I could have pointed out that 1.6 has not yet been integrated with Domoticz. Regardless, it is probably a good idea to wait some weeks before switch over to 1.6 as all major code changes will include glitches not showing up prior real usage...

Cheers!

[vinisz]

Ok, so, can I run this with domoticz or not ? I saw it is not in the latest stable

[pvm]

Now : you cannot unless you are a programmer and able to integrate it

[Gravityz]

why making a big fuzz out of this.

openzwave v1.5 was the previous version but domoticz is still on v1.4

this tells me things are going slow with domoticz(probably for a good reason)

[Ricard1]

why making a big fuzz out of this.

openzwave v1.5 was the previous version but domoticz is still on v1.4

this tells me things are going slow with domoticz(probably for a good reason)

1.5 was a developer thing and never released, 1.4 is the previous version so Domoticz is doing very well I believe.

[febalci]

[WARNING] make sure you backup your current libopenzwave.a before trying this. You will need this file in open-zwave-read-only directory to complete a successful creation of domoticz executable from source.

I just tried to compile /link domoticz from source on my RPI (Debian stretch) with the new OZW version (got it with git pull). Created the new libopenzwave.a with make and then did a make in the domoticz source directory.

After restoring the 'old' libopenzwave.a , the link process works without problems and domoticz is created.

@warren
Does that mean you are using libopenzwave.a from 1.4? So again, does that mean you are using the openzwave 1.4 after all, not 1.6?

[waaren]

@waaren
Does that mean you are using libopenzwave.a from 1.4? So again, does that mean you are using the openzwave 1.4 after all, not 1.6?

Yes. Compiling to OZW 1.6 was just a test. If it compiled with domoticz, I would have started to test it but for now I am completely happy with 1.4

[svde]

I run domoticz on a Fedora server. Fedora moved to openzwave 1.5 in july 2017. I try to only run packaged software, so I ended up maintaining openzwave 1.4 packages in order to build domoticz, which has worked.

In the mean time Fedora managed to package the previous stable release against openzwave 1.5, but the patches stopped applying with the domoticz beta releases.

It seems that the openzwave project has been quite active recently, with both their github and http://openzwave.com/downloads containing new releases.

[hestia]

I have this version: 1.4-3335-g74e05982-dirty
do you have the same?
dirty doesn’t seem good to me...

[febalci]

I have the 1.4-3254 that comes with the precompiled version on ubuntu.I never had a satisfactory setup with zwave, so i tried to use ozw 1.6 with compiling both ozw and domoticz. Nonetheless, domoticz compiles but gives a lot of undefined references after 100% compilation when on linking phase. So, domoticz is not ready for this, i keep on waiting...

[thelbekk]

I am sure there are changes that need to be made to Domoticz before it can use Openzwave 1.6, but looking at the actual error messages generated during linking made me notice something strange:

There's a copy of the header files from Openzwave sitting in hardware/openzwave/, seemingly placed there as part of a modified copy of the Openzwave control panel, another project from them. These header files get used when Domoticz is built, instead of the ones installed with Openzwave, and I assume that any discrepancy between them and the installed version of Openzwave is a potential source of trouble. They are currently up-to-date copies of the header files from Openzwave 1.4.

In this case, all the error messages while linking Domoticz after installing Openzwave 1.6 are caused by a couple of changed declarations - and if these are adjusted in the copies in hardware/openzwave/, and Domoticz rebuilt, there are no complaints, and the resulting binary runs. I certainly wouldn't try to use it in production, as I'm sure there will be disagreements between Domoticz and Openzwave about actual data contents, and the semantics of using the Openzwave 1.6 API. I also haven't tried completely replacing the copies with ones from 1.6 - as I said, I expect there to be API changes that Domoticz will need to adapt to before things will work reliably.

Still, just having those copies in the main Domoticz source distribution feels somewhat wrong.

[waaren]

All the error messages while linking Domoticz after installing Openzwave 1.6 are caused by a couple of changed declarations - and if these are adjusted in the copies in hardware/openzwave/, and Domoticz rebuilt, there are no complaints, and the resulting binary runs.

Can you please share these adjustments ? I have a test-system and I am curious to see if I notice any changes in domoticz / Zwave behavior.
Thx !

[thelbekk]

Ah, I don't have the changes any more - it was just a quick test. However, it's just differences in the declaration of the functions in question: during the compilation of Domoticz, the local declaration is used, and if its parameter list doesn't agree with the one in Openzwave, it'll fail during linking. So, just to pick one example:

domoticz/hardware/openzwave/Manager.h: string GetValueLabel( ValueID const& _id );
open-zwave/cpp/src/Manager.h: string GetValueLabel( ValueID const& _id, int32 _pos = -1 );

I just replaced the declaration in the copy of the file in Domoticz with the one from Openzwave 1.6. Same for the other errors.

Again, note that while these changes let Domoticz build and run with Openzwave 1.6, I certainly don't expect it to work correctly!

[waaren]

Again, note that while these changes let Domoticz build and run with Openzwave 1.6, I certainly don't expect it to work correctly!

Thx. Will try and see where I get on my test-system.

[thelbekk]

...and now the industrious gizmocuz has updated Domoticz for Openzwave 1.6!