Aeon Labs Z-Stick Series 2

[jaretselinger]

I'm trying Domotiga 0.1.191 with a Z-Stick S2 with the most current update, Windows Static Library 5.02 P3 USA. When I look at Z-Wave Commander all that is shown is "Unknown" for Mode, and "0" for Controller ID. The Z-stick does work as it is functional in Homeseer.

Any idea what the problem might be?

The stick is being found as this is in the main log:
2010/12/01 20:58:12 Z-Wave support enabled.
2010/12/01 20:58:12 Z-Wave interface connected to Port /dev/ttyS0

This is the debug output:
2010/12/01 20:58:12 [Z-Wave] > 15
2010/12/01 20:58:12 [Z-Wave] Get controller info
2010/12/01 20:58:12 [Z-Wave] > 01 03 00 15 E9
2010/12/01 20:58:12 [Z-Wave] Get home & controller IDs
2010/12/01 20:58:12 [Z-Wave] > 01 03 00 20 DC
2010/12/01 20:58:12 [Z-Wave] Get capabilities
2010/12/01 20:58:12 [Z-Wave] > 01 03 00 07 FB
2010/12/01 20:58:12 [Z-Wave] Get SUC node ID
2010/12/01 20:58:12 [Z-Wave] > 01 03 00 56 AA
2010/12/01 20:58:13 [Z-Wave] Get init data
2010/12/01 20:58:13 [Z-Wave] > 01 03 00 02 FE
2010/12/01 20:58:13 [Z-Wave] No nodes found to sent query!
2010/12/01 20:58:13 [Z-Wave] Requesting basic report for Node 255
2010/12/01 20:58:13 [Z-Wave] > 01 09 00 13 FF 02 20 02 05 06 39
2010/12/01 20:58:23 [Z-Wave] Requesting version report for Node 0
2010/12/01 20:58:23 [Z-Wave] > 01 09 00 13 00 02 86 11 05 07 72
2010/12/01 20:58:36 [Z-Wave] Requesting basic report for Node 255
2010/12/01 20:58:36 [Z-Wave] > 01 09 00 13 FF 02 20 02 05 08 37
2010/12/01 20:58:40 [Z-Wave] > 01 0A 00 13 00 03 26 01 00 05 09 CE
2010/12/01 20:58:40 [Z-Wave] Requesting basic report for Node 0
etc....

[RDNZL]

Ok will have to get some more info on this stick version...
Does it run on same baudrate to begin with?
Anyone has more info on differences between this one and the older version?

[jaretselinger]

I'm not sure what the baudrate was on homeseer, my trial has expired, so I can't try it with that again.

[RDNZL]

Ok, this series 2 is nothing special I think, it's looks like the same version I'm using.

But you are using the wrong serial port setting!

Code: Select all

2010/12/01 20:58:12 Z-Wave interface connected to Port /dev/ttyS0

You are using an onboard serial port in DomotiGa's Z-Wave settings, (/dev/ttyS0) not an USB serial port.

It should be something like /dev/ttyUSB0 ... /dev/ttyUSB9, see dmesg command output after inserting the stick.

[luria]

I'm having the same problem, but my controller is connected to the right port (/dev/ttyUSB4)

Code: Select all

[   30.371118] usb 2-6: cp210x converter now attached to ttyUSB4

I'm able to control my z-wave devices, but local changes is not updated in Domotiga.

[RDNZL]

So it fetches the dongles learned device table, it switches but status isn't coming back, correct?

Can you mail me the debug output of ZWave module?

I guess there is a serial code/timing problem.
Since I have learned a better way to write and read data, I will try to implement that for ZWave too.
I'm also thinking about using the open-zwave library instead to talk to the hw.

[RDNZL]

Because of a Gambas bug, where the == operand returned true always, the checksum check was incorrect.

I have fixed checking the checksum for received packets now, I had those errors in my log but didn't see them in yours.
Are you all running the USA firmware? I'm running the EU version.

[luria]

Thanks! I'm running the latest EU version.

Edit: After a quick svn and a recompile, everything works like a charm!

[Jaren]

Because of a Gambas bug, where the == operand returned true always, the checksum check was incorrect.

What did you do to get around the == bug?
I pulled latest svn today and in the debugger I'm seeing the == always return false even when the values were equal.
The debug logs are full of:
2011/01/13 22:25:57 [Z-Wave] Packet Length = 5
2011/01/13 22:25:57 [Z-Wave] < 01 05 00 13 0D 00 E4
2011/01/13 22:25:57 [Z-Wave] Checksum incorrect - sending an NAK


I replaced the == clause with a NOT ( > OR < ) clause ( lame I know ) and that seemed to do the comparison right and I stopped getting the failed checksum errors in the debug.

But if I manually walk across the room and flip a Z-Wave switch the status still doesn't update for me in DomotiGa.
I'm using the Z-Stick2 USA firmware. I just updated it tonight to see if that made a difference.
I'm using GE dimmer switches. ( 45606 - Dimmer, 45613 - 3-way Dimmer )

[luria]

I was a bit too quick, same problem too: No status update when I operate switch locally.

[RDNZL]

The == in CZwave.class needs to be replaced by an =
I had that done in newer code, but it got overwritten by another patch.
== is case insensitive compare which is useless when comparing bytes.

To get rid of the == false behavior in Gambas console/debugger, you need to update your Gambas version to the latest stable code.
(best to compile from svn like described here http://www.domotiga.nl/wiki/Gambas/Install)

I read that you have done that already. Strange as in my Gambas 2.21 console it works as expected:

Code: Select all

? "e" == "e"
True
? "E" == "e"
True
? "E" == "a"
False

I will try to debug CZwave some more, it sure does seem to work not 100% correct with latest dongle updates, or another cause.

[RDNZL]

Regarding not receiving updates of manually switched switches, this does not work straight away and not with all types of devices.
Yes you have read it correct, even ZWave sucks...

Do you get packets in when you switch a switch? I guess not.

There are some tricks needed like supporting and configuring "associations"

Reed more about it here:
http://www.homeseer.com/wiki/index.php/ZWave

Can you check if your devices support it?
I haven't done anything regarding this with DomotiGa yet, so we have to find out whats needed to get this working...

[Jaren]

I placed breakpoints in the DecodeFrame function trying to see what sorts of messages I am receiving.
I never get into the CASE COMMAND_CLASS_BASIC which I think is where the status is supposed to be updated when you switch a switch locally.

According to this thread:
http://forums.homeseer.com/showthread.php?t=144994
my GE switches don't support associations.

Can you think of a simple way I could tag those specific switches to have their status polled every x seconds?
The Poll Status button in the Z-Wave commander seems to work just fine.

This certainly won't be as nice as getting direct status updates, but it sounds like it may be the best that can be done with devices that don't support associations.

[luria]

Sorry for not rtfm, I just dived into this again after a long break from HA.

My ACT ZDW232 dimmer supports associations, (groups 1-4), but apparently no direct feedback: http://www.act-remote.com/HPW/Inst/ZDW232_instr.pdf
Classes:

Code: Select all

COMMAND_CLASS_SWITCH_MULTILEVEL 
COMMAND_CLASS_SWITCH_ALL 
COMMAND_CLASS_ASSOCIATION 
COMMAND_CLASS_POWERLEVEL 
COMMAND_CLASS_CONFIGURATION 
COMMAND_CLASS_VERSION 
COMMAND_CLASS_MANUFACTURER_SPECIFIC 
COMMAND_CLASS_MARK 
COMMAND_CLASS_BASIC 
COMMAND_CLASS_SWITCH_MULTILEVEL 
COMMAND_CLASS_BASIC_WINDOW_COVERING 

Shows up in Z-wave Commander as Manufacturer

Code: Select all

Act

product

Code: Select all

Unknown (44 47)

[RDNZL]

I will add a polltimer to zwave code to see if thats helpful.
You can always disable it if it's not needed.
Would be nice if i could see which devices i need to poll and which not.
Looking for class_associaton for each device is not enough.