11-15-2009, 06:21 PM
Hi
I\'m using the latest posted Comfort Ultra Beta firmware.
I\'ve had a problem with my ZWave lights for a while, getting spurious lockups, as described in another thread.
Montoring the comfort bus I\'m now noticing spurious counter values.
Only reason I have spotetd is because i\'m using my Comfort Client with sounds on for the lights so I hear the lights switch state.
An example, all my zwaves are straight switches (no dimmer versions) as I use CFL\'s; so I expect to send \"00\" for off and \"FF\" for on.
Just got a counter report from Comfort that went like this when the light is already ON (ie CT32FF)
CT32FA <- What\'s this!!
CT32FF
Another example
CT3501 <- What\'s this!!
These arent valid on/off counter responses. CTxxFF and CTxx00 are the only valid responses I should be getting.
Any ideas. Are the counters right and it\'s the logic on the UCM/Zwave that\'s causing. Dont know how to get to the bottom of this.
Regards
Julian
I\'m using the latest posted Comfort Ultra Beta firmware.
I\'ve had a problem with my ZWave lights for a while, getting spurious lockups, as described in another thread.
Montoring the comfort bus I\'m now noticing spurious counter values.
Only reason I have spotetd is because i\'m using my Comfort Client with sounds on for the lights so I hear the lights switch state.
An example, all my zwaves are straight switches (no dimmer versions) as I use CFL\'s; so I expect to send \"00\" for off and \"FF\" for on.
Just got a counter report from Comfort that went like this when the light is already ON (ie CT32FF)
CT32FA <- What\'s this!!
CT32FF
Another example
CT3501 <- What\'s this!!
These arent valid on/off counter responses. CTxxFF and CTxx00 are the only valid responses I should be getting.
Any ideas. Are the counters right and it\'s the logic on the UCM/Zwave that\'s causing. Dont know how to get to the bottom of this.
Regards
Julian
