BaduFamily
Active Member
Hi Folks.
I just started exploring the Elk M1 'zt' command. There was a bit of a mention of it over in Automation, and I had a few moments to take it out for a spin.
it was, for me, a short trip.
when I ( programmatically, via a one-shot timer ) send
E: setting timeout function
Elk: Request Ethernet test code: XK data: 434411325031411000 at Tue Mar 25 2014 11:44:59 GMT-0700 (PDT)
timeout code executed. calling elk.setZone 032
the string 09zt03200B4
the logged, bold string you see above I get no response that I expect. Here's what I get. ( stripped the heartbeat )
Elk: Control output change update code: CC data: 010100 at Tue Mar 25 2014 11:45:05 GMT-0700 (PDT)
Elk: Control output change update code: CC data: 010000 at Tue Mar 25 2014 11:45:08 GMT-0700 (PDT)
which is an "Output Change Update." huh?
Triggering the zone 'manually' my stuff logs this response, so I know I am talking to a live zone, etc.:
Octo:ElkListener casey$ node --harmony ElkM1Listener.js
E2V: Conn OK. Tue Mar 25 2014 10:13:00 GMT-0700 (PDT)
EFinal: Zone 032 Development Button Violated Tue Mar 25 2014 10:13:12 GMT-0700 (PDT)
( the Development Button ) is an Ion Plunger. very handy. )
Did I miss something? Just for kicks I transmitted their example too, 09zt12300B3, with no response.
I just started exploring the Elk M1 'zt' command. There was a bit of a mention of it over in Automation, and I had a few moments to take it out for a spin.
it was, for me, a short trip.
when I ( programmatically, via a one-shot timer ) send
E: setting timeout function
Elk: Request Ethernet test code: XK data: 434411325031411000 at Tue Mar 25 2014 11:44:59 GMT-0700 (PDT)
timeout code executed. calling elk.setZone 032
the string 09zt03200B4
the logged, bold string you see above I get no response that I expect. Here's what I get. ( stripped the heartbeat )
Elk: Control output change update code: CC data: 010100 at Tue Mar 25 2014 11:45:05 GMT-0700 (PDT)
Elk: Control output change update code: CC data: 010000 at Tue Mar 25 2014 11:45:08 GMT-0700 (PDT)
which is an "Output Change Update." huh?
Triggering the zone 'manually' my stuff logs this response, so I know I am talking to a live zone, etc.:
Octo:ElkListener casey$ node --harmony ElkM1Listener.js
E2V: Conn OK. Tue Mar 25 2014 10:13:00 GMT-0700 (PDT)
EFinal: Zone 032 Development Button Violated Tue Mar 25 2014 10:13:12 GMT-0700 (PDT)
( the Development Button ) is an Ion Plunger. very handy. )
Did I miss something? Just for kicks I transmitted their example too, 09zt12300B3, with no response.