2.0 Beta+ Released 2009-04-18T16:02:18+00:00

HOME Forums Gateways EZSrve 2.0 Beta+ Released

Viewing 5 posts - 31 through 35 (of 35 total)
  • Author
    Posts
  • Anonymous
    Post count: 1001

    Define Condition 1 with an Attribute Value of 1101 (Group 1 On) and Condition 2 that is ANDed to Condition 1, with Condition 2 time based using SunsettoSunrise option. I think that will give you what you are looking for. You will have to create a Scene with the EZSnsRF Unit 01 as the Controller with the EZSrve as the responder so that EZSrve will receive the Group 1 On/Off commands. I’ve got a glitch in my system for the moment that is preventing me from doing screen captures of V2. Once that is resolved I’ll try to past a screen capture of a working example.

    Anonymous
    Post count: 9

    For the EzSnsRF, there are no attributes in the drop down box.
    I didn’t see EZsnsRF in then list when I added the device, so I used EZsns1W-interface, was that correct?

    Also what attribute would I use for a OFF being sent to a group?

    Thanks

    Anonymous
    Post count: 1001

    That is not the correct device type. The fact that there are no attributes in the pulldown indicates the wrong device type. Unfortunately my V2 system has a glitch so I cannot say with certainty which type you should be using. When you have the correct type there will be a Status entry in the pulldown that should be selected. An Attribute Value of 1301 is for a Group 1 Off being received from the device. The 0x13 is for an Off command and the 0x01 is for Group 1. If there is no entry for the EZSnsRF, (I think there was an extra character in there somewhere on V1) you can temporarily define it as a RemoteLinc which will give you a Status entry in the pulldown.

    Be sure you have uploaded the DevClusters.xml file that applies to the image you are running. The.zip file which includes the image.bin has the DevClusters.xml file for that image. The Java Discovery tool does not upload the DevClusters.xml file. After uploading the DevClusters.xml file be sure to do a Restart (not Reset).

    EDIT: if you do decide to try a different device type, you will have to delect the device entry. Select NO when it asks if the device is available so that nothing is done with the links in the device. When you readd the device the links will be read again.

    Anonymous
    Post count: 9

    Thanks Gif091,

    It seems to be working by using Remotelink. I’m suprised that there is no device type entry for EZsnsRF.

    If you have several effects, do you need to offset them by a couple of seconds each?

    Thanks

    Anonymous
    Post count: 1001

    I finally figured out what I had done with my V2 system and now see that there is no EZSnsRF device entry yet in V2. The device types are closely tied to the information in the DevClusters.xml file (new to V2). It looks like the DevClusters file does not yet have a definition for an EZSnsRF. The RemoteLinc should give you access to the Status attribute and trigger off whatever group number you want to use.

    I would add a second or two for multiple Events. I really depends on what they are. For a Group that has multiple responders there are multiple Insteon commands that have to go out on the powerline and be ACKed. Probably a good idea to allow a little more time for those. A single Direct command to a device is quick but V2 does a query of the device to check it’s On/Off status which could be interfered with if another Event was to follow too quickly. You can try it with no delay but if there are any problems then add a couple of seconds delay.

Viewing 5 posts - 31 through 35 (of 35 total)
  • You must be logged in to reply to this topic.