HM-TS001 temp sensor Options

[johnlaroux]

Hey there

Does anyone happen to know the wakeup parameter for this temp sensor???
I want to be able to change it so I can get the battery status other then every hour.

[garylm]

See parameter 6 on page 6 here.

[johnlaroux]

See parameter 6 on page 6 here.

Oooops I meant sleep time interval. I want it to sleep for as long as possible because my automation software sends the N*SE49,4 and the N*SE128,2 every time it wakes up and I dont want that because im already setting the auto report in Parameter 6.

[garylm]

Wakeup Set: N*SE132,4,BYTE,BYTE,BYTE,BYTE //sec1(MSB),sec2,sec3(LSB),nodeIDtoBeNotified
Wakeup Get: N*SE132,5
Wakeup Report: N*SE132,6,BYTE,BYTE,BYTE,BYTE //sec1(MSB),sec2,sec3(LSB),nodeIDtoBeNotified
Wakeup Notification: N*SE132,7

[johnlaroux]

Wakeup Set: N*SE132,4,BYTE,BYTE,BYTE,BYTE //sec1(MSB),sec2,sec3(LSB),nodeIDtoBeNotified
Wakeup Get: N*SE132,5
Wakeup Report: N*SE132,6,BYTE,BYTE,BYTE,BYTE //sec1(MSB),sec2,sec3(LSB),nodeIDtoBeNotified
Wakeup Notification: N*SE132,7

I really appreciate the quick responses Garylm. Im a complete noobie on this stuff so the most and least siginificant bit thing is probably beyond my understanding.

I did the N*SE132,5 command and it returned 132,006,000,014,016,255 Not sure what that means.

Do you think there is a parameter for the Sleep interval descibed on page 7 paragraph 2-2-2
That is the one I would like to change.

[garylm]

2-2-2 Sleep Time Interval
The sleep interval can be set from 1 minute to 4660 hours (about 194 days). The unit of time is in seconds. The preset sleep time interval is 1 hour.

Wakeup Set: N*SE132,4,BYTE,BYTE,BYTE,BYTE is the setting you need.

Bytes consist of 8 binary bits and can take a value from 0 to 255 (00000000 to 11111111)

The least significant byte (LSB) has a weight (or multiplier) of 1 (or 256^0).
The middle byte has a weight of 256 (or 256^1).
The most significant byte (MSB) has a weight of 65536 (or 256^2).


132,006,000,014,016,255 is probably the default setting

That would translate into (0*65536) + (14*256) + (16*1) or 3600 seconds or 1 hour. "255"would be the target node for the wakeup notification. You'll want to change that to the node ID of your Z-Wave dongle (RZC0P?). Maybe "255" means "all" nodes or "any" node. I'm not sure how that works.

Like section 2-2-2 says, you can go all the way up to 4660 hours.

N*SE132,4,255,255,255,??? would give you (255*65536) + (255*256) + 255 seconds or 16777215 seconds or 4660.3375 hours. Just remember to replace the question marks with your dongle's node number.

[johnlaroux]

Wakeup Set: N*SE132,4,BYTE,BYTE,BYTE,BYTE is the setting you need.

Bytes consist of 8 binary bits and can take a value from 0 to 255 (00000000 to 11111111)

The least significant byte (LSB) has a weight (or multiplier) of 1 (or 256^0).
The middle byte has a weight of 256 (or 256^1).
The most significant byte (MSB) has a weight of 65536 (or 256^2).


132,006,000,014,016,255 is probably the default setting

That would translate into (0*65536) + (14*256) + (16*1) or 3600 seconds or 1 hour. "255"would be the target node for the wakeup notification. You'll want to change that to the node ID of your Z-Wave dongle (RZC0P?). Maybe "255" means "all" nodes or "any" node. I'm not sure how that works.

Like section 2-2-2 says, you can go all the way up to 4660 hours.

N*SE132,4,255,255,255,??? would give you (255*65536) + (255*256) + 255 seconds or 16777215 seconds or 4660.3375 hours. Just remember to replace the question marks with your dongle's node number.

WOW thanks, that was an excellent lesson. Now I understand how this works. Thanks again. This sensor does send to my VRCOP when it awakens so ill guess that the 255 in the node position is all nodes.