fw 1.57 setting macro for EZSnsRF

[Anonymous]

#42334

Looks like hacking the devices file got me working, or at least able to retrieve the device links. Will work on actually using it tomorrow. Thanks grif – they should be paying you.

[Anonymous]

#42335

I went ahead and used EZSrve Scene Management to create a new link from the EZIO8SA Input 3 to EZSrve. SDM3 trace showed it was written to the correct location. To double check I defined a Macro triggered by the EZIO8SA Input 3. Worked as expected. Please post back results of your next tests. Thanks.

[Anonymous]

#42336

For a lot of devices when you add it to EZServ it creates a link so the device can be monitored by EZServ. Since I modified the XML entry for the EZSnsRF after adding it without creating the link I don’t currently have such a link in place. Is there any way to get EZServ to create that same link now that the device definition has been corrected?

[Anonymous]

#42337

With the MSB change you now can create a controller link in the EZSnsRF for each of the Virtual Inputs that are active. The EZSnsRF uses Group commands to signal the On or Off of each Virtual Input. A Controller Of link in the EZSnsRF is required for each active Virtual Input so the Group protocol will know where to send the On and Off commands. In this case I assume it would be the EZSrve as the responder so macros could be defined to accomplish other activities. More than one controller of link can be established in the EZSnsRF for each Virtual Input so that direct control of one or more Insteon devices are possible along with notifying the EZSrve that the On/Off has occurred. I single link established at device add time does not work for the EZSnsRF where each Virtual Input requires a link.

[Author]

Posts