UCM/Z-wave

[juwi_uk]

Hi Chiu,

 

Received the UCM/Z-wave and other bits today (25/03/09) and I must say that setting up the UCM was really easy and I was turning switches on/off within 15 minutes via the on/off buttons on the UCM Z-wave configuration page.

 

Setup some responses and added to the control menu and can do the same there as well.

 

Some initial observations and issues:

 

(1)     Probably the most important is that I can’t get the mapped counters to show any value change.  I’ve set the poll interval to 1 (which is 10 secs) and mapped the counters; do I need to do anything else?   As far as I can see right now is that polling doesn’t work but I’m sure there’s a reason. My ZWave switches are ZRW230’s as you know.

(2)     The polling frequency in 10sec intervals seems strange; why not set to 1sec intervals?  Reading the Z-wave forums people seem to set polling frequency to 2 secs which obviously we can’t do here.

(3)     The D1 LED on the daughterboard worried me for a while as it’s always RED which I took to mean ERROR.  Could do with something in the manual to describe state of this LED as I couldn’t see anything (page 6 is the obvious place for this).

(4)     Page 8, paragraph 5 says that D2 and D3 LED go RED at first start up; I’m sure mine were D2 and D4.

(5)     When you associate a counter with a Z-wave ID the counter list does not show this under “Show References”.

 

Any help on the statuses (1) appreciated.

 

Regards

 

Julian

[leonchue]

Hi,

(1)  Did you \"Write to EEPROM\" after the counters mapping?  You can \"Read from EEPROM\" to verify if the settings are correct.  These operations can be found in the UCM/ZWave page of Comfigurator.

(2)  Polling in short intervals can \"jam\" the air traffic, especially if there are many devices in the network.

(3)  That red LED is to indicate daughterboard power status.

(4)  That is correct.  Should be D2 and D4. 

(5)  We will look into this.

Thanks for your feedback.

[juwi_uk]

Ok,

Thanks for the help;  I\'ve made some progress.

No I didnt write to EEPROM after changing the counter mappings;  I didnt know I needed to do this as I only thought that was needed when you want to update the ID list.   (It\'s a part of the training at Heathrow that Chiu couldnt show us last week as the UCM didnt have an EEPROM fitted).

So now when I switch on/off the light from a response or comfigurator it is now showing the counter value.  But....

If I turn on the light via the ZTH200 or switch then it does not automatically update the counter UNLESS i request the status of the ID directly.   Is that correct; ie that I have to poll each device myself via some sort of looping response?  If so do you have an example.   If this is the case what does the polling value do on the UCM Zwave setup page as this still seems to be doing nothing despite being set to 1 (10 secs); I wait and nothing happens!!

Regards

Julian

[leonchue]

How about resetting the UCM/ZWave board?  The D3 LED should blink every 10 seconds...

[juwi_uk]

OK, that worked better.

Checked before reset and it wasnt blinking.  Did a reset and it did then blink every 10 secs as per my setting of \"1\". When do you need to reset then as I did a full system reset after config upload so would have thought that would have reset the UCM too.

I\'m not finding it very reliable though right now; sometimes the status is reflected in the counter, sometimes it isn\'t.    Maybe it\'s a reception thing as my comfort is installed upstairs and the switch I\'m controlling is downstairs.  Will help when I have zwave devices closer to comfort so the mesh will work i guess.

That\'s of course if the reliability thing doesn\'t turn out to be on the Comfort side.

Still think the 10 secs minimum granularity is too large though.

Julian

[juwi_uk]

Another observation from more testing today.

The bus is sending a Counter chnage report every time the zwave bus is polled.  This is irrespective of whether the value has changed or not.  Below is an extract from my monitor window in my Client to demo what I\'m seeing:

 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT32FF
 < CT184E
 < CT32FF

This seems different to normal counter activity where you only get a status report when the value changes.

Is it doing this by design?

Julian

 

 

 

[juwi_uk]

Actually the counter status reports working like this is quite useful so hope it\'s not a bug.

[admin]

[user=73]leonchue[/user] wrote:

Hi,

(1)  Did you \"Write to EEPROM\" after the counters mapping?  You can \"Read from EEPROM\" to verify if the settings are correct.  These operations can be found in the UCM/ZWave page of Comfigurator.

The UCM/Zwave manual (1.1.3)  has now been updated to include these instructions, see UCM/Zwave page

[admin]

[user=876]juwi_uk[/user] wrote:

Actually the counter status reports working like this is quite useful so hope it\'s not a bug.

Actually it is a bug. The counters which are unchanged should not be updated again as that would cause additional communications traffic on the Comfort Bus
Why do you find it so useful?

[juwi_uk]

It\'s useful because when I start up my Client I always need to do an initial poll to set all counter values as Comfort wont report them at that point because the havent changed in it\'s view (which is true).

Not a problem if it is a bug; I\'ll just need to poll all of the light counters as well.

Julian