Home Automation Domotica Forum Europe, Bwired Forum

I've only got 7 nodes on my zwave network right now.

I'm simply calling openzwave's InitZWave function and watching till the debug output stops scrolling stuff past.
It does it all asynchronously in a thread on the c++ side.

It does send a message almost immediately once the driver is ready.
Watching the debug spew I can see it gathering all sorts of information about the capabilities of all the nodes.

Looking closer I see that it has a command queue that it works through. So maybe it'll be ok for us to start sending commands even if there may initially be a delay before they are processed.

I now have a decent chunk of CZWave.class replaced by calls into openzwave.
It turns out that my switches aren't associated after all.
They are simply sending a few updates of their dim level as they are being turned off.
So I'll be able to catch whatever they send, but they aren't notifying the controller that they were turned off, which was my original goal.

Polling and some smart requests for Basic Reports may be what I need with or without openzwave.

Is it still worthwhile to others if I continue trying to work openzwave into DomotiGa?

As for me, I'm satisfied with a polling routine ala plcbus, but wery happy with the effort you are making in getting z-wave support a bit further in domotiga.
With som many variations between switches and manufacturers implementation of z-wave, polling is probably the only way we can get consistent results from all nodes?

I think its good to integrate your openzwave interface code ( or optional ) because it supportsbattery powered sensors etc and polling is not easy from gambas for zwave as each send/ received msg needs to be acked within a certain time. Which is not easy to do.

Great to see there are more people using domotiga with zwave.
If it is not to much work, I think it will be nice to be able choose between the traditional and openzwave method.
At least for the beginning until the new method has proved it's stable enough for production environments.

I've spent the past few days cleaning up both the openzwave wrapper library and my changes to Domotiga.
I add some thread safety code to the wrapper and that significantly slowed down the startup, so I'm still looking at that.

Without the thread safety the system was a little fragile as it started up. If someone flipped a switch while the initial queries were happening sometimes some of the devices wouldn't get fully initialized and ready to go.

If I can track that down without having such a long startup (with thread safety it is like 1 minute 30 seconds for my 7 devices) then I'll see what I can do to push the code back up.

One other thing, I hadn't been planning on supporting both methods. I'll see if I can get the old method back in with a toggle. I agree that it'd be bad to force people to use the new library if it isn't going to work for them.

I installed update 0.1.194 and everything works great.

I've got this set up so you can toggle a column in the db to switch between built in and open zwave support.
What is the best way for me to submit it for review?

You can e-mail me the changed files and db field description.
Or your whole code tree if you don't want to bother sorting out stuff, I have become very handy with diff

Pls include needed setup details if possible...
See DomotiGa's README file for e-mail address...

Thanks in advance!

Any News on the subject?
I would love to test the new zwave code.

Status is that I got the code from Jaren, have it merged with my development version 0.1.195, there is an issue with it, and I need to sent debug info to Jaren.
Due to my busy work week I didn't have the time collect and sent it, will do it this morning...

I have just commited Jaren's open-zwave wrapper.
So you can update your DomotiGa code from svn, and read the README in domotiga/wrappers/domozwave to get it going.
Please report your experiences, bug reports and ideas!

quick note for other people like luria:

ACT devices do support the instant update notification, but you have to associate the devices with your USB controller in Association group 1.

This is (as far as I could find out) to get around the Lutron patent.

Hopefully this helps others with getting more out of there devices

ps. With a single threaded PHP script, my 7 devices report their status in < 1 sec, all devices are within range of the controller.

I followed the instructions.
The make command in the domozwave directory gives this error:

make: *** Er is geen regel om doel '-lxmlrpc_xmlparse' te maken, nodig voor
'libdomozwave.so'. Gestopt.

This is on an opensuse 11.3 x64 system.
Does anyone have an idea abou what's wrong.