AnonymousNovember 19, 2008 at 3:32 amPost count: 37
I’m thinking that there must be something very screwy when trying to work with Remote Lincs. I’ve been experimenting with Scenes today and have only gotten more and more confused.
I added the Remote Linc to the devices list. In this process, it appears that EZServe downloaded all the links from the Remote Link device. In the process of adding a Scene for my office lights, things just did not work out at all.
Just now, I used the Device Manager to remove a link to my Office Window Outletlinc. When I finished and it no longer showed the link (using the device manager), I pressed the button that was originally used for Office Window and it worked still. I would have expected it to fail since the link should have been gone.
All sorts of weirdness including the screwing up of links in another Remote Link even tho I did not change that device at all. I finally deleted my test scene and re-established my manual links in the remote links. All is back to good now.
I just now also deleted the remote link device and then re-added it. When I did, it now shows many duplicate links for this device. I don’t have a clue about what is broken, but EZServe certainly does not like to work with these particular devices.
LeeAnonymousNovember 19, 2008 at 5:22 amPost count: 1001
As in the other post you made regarding the Remotelinc, I would suggest downloading the Simplehomenet Utility Suite. You can use it to view the links in the OutletLinc devices as well as display the links in the RemoteLinc. Duplicate links can be established if you repeatedly create links without doing the necessary cleanup of the previous link processes. You can issue a SYNCH EZSERVE request against the device after deleting a particular link to see if more of the same links exist. If a duplicate link exists, delete it and issue another SYNCH EZSERVE until all the duplicate links are gone. If an Insteon device is responding to a Group command sequence it must have a responder link record for the hardware to look at when a command flows across the powerline. It needs the responder link record to know which commands to react to and which commands to ignore. That is the way Insteon hardware works. If a device is responding to a Group command without a corresponding responder link record the device is not working correctly.AnonymousNovember 19, 2008 at 5:33 amPost count: 29
How did you get the links from your remotelinc to show up? When I try to synch EZServe with my remotelinc I get a “Device did not respond” error message.AnonymousNovember 19, 2008 at 5:50 amPost count: 1001
The RemoteLinc turns its RF receiver off to save battery power. When you want EZSrve to talk to it (or any other product or device to talk to it) you have to put it in linking mode which will turn on the receiver for 4 minutes. The RemoteLinc will keep the receiver on beyond the 4 minutes if it is receiving constant communication such as the EZSrve reading the link database. That second time out interval is much shorter than 4 minutes (don’t remember the exact time) so it can time out if communication to the RemoteLinc is slow or intermittent.AnonymousNovember 19, 2008 at 5:51 amPost count: 256
Please keep in mind that the RemoteLinc “goes to sleep” when not in use. Therefore the following is true:
1) if you try to add it with the EZSrve trying to discover it, you’ll get a “device did not respond” error
2) if you delete links in the EZSrve, the records will be deleted from the EZSrve but not from the RemoLinc itself.
To get around 1) and 2) above, put the RemoteLinc in linking mode when you do any of these operations.
Regarding the “strangeness” observed: Links are 2-part animals; one part in the responder and another in the controller. To remove the effect of linking, both the responder and controller links need to be deleted. Removing the link from a responder only will still allow the controller to control the responder. This is because even though the responder no longer reacts to the group broadcast message from the controller, it still responds to the direct group cleanup message that the controller sends to the any responders it finds in its databse for the corresponding group.AnonymousNovember 19, 2008 at 4:22 pmPost count: 29
That works- thanks!AnonymousNovember 19, 2008 at 7:38 pmPost count: 37
OK, SYNCH does what??????
When you click on the SYNCH Button, the warning message is: “This will erase all links in the device and write the displayed list. Are you sure?
Click ‘OK’ to confirm”
This would indicate that you are synching FROM the web control page TO the device and not vice versa as indicated by the previous post. What is actually correct here?
Assumption #2 on my part: If you delete the device and then re-add it using NAME, and INSTEON Address, THEN The “Displayed List” of links will be re-loaded from the actual device.
What is happening to me:
#1: I SYNCHED to my Remote Link (successful/no errors) from my list of links after making modifications to delete unwanted links
#2: I then deleted the whole device and then re-added the device AND, I now see a huge long list of links with duplicates.
What gives???AnonymousNovember 19, 2008 at 8:06 pmPost count: 37
SYNCH EZServe button is DEVICE -> DISPLAYED LIST/EZServe
SYNCH Button is DEVICE <- DISPLAYED LIST/EZServe
PS: I cannot get the utilities to work. There are no installation instructions and no “SETUP”. I downloaded the .ZIP download as well as the required SMARTHOME support module which I installed first and that worked.
LeeAnonymousNovember 20, 2008 at 1:59 pmPost count: 1001
For those who are following this topic and may be confused by some of the terminology being used; on the Device Management screen, there is no SYNCH button. There is a SYNCH DEVICE button and a SYNCH EZSERVE button. The SYNCH DEVICE button uses the information in the EZSrve devices3.xml file to write the device link database. This is moving data from the xml file to the device to bring the two into synchronization. The SYNCH EZSERVE button uses the information in the device link database to update the devices3.xml file. This is moving data from the device to the xml file to bring the two into synchronization. The EZSrve Operating Guide covers the use of both the SYNCH DEVICE and SYNCH EZSERVE buttons.AnonymousNovember 20, 2008 at 7:00 pmPost count: 37
Understanding SYNCH does help a lot.
I did download and got installed the Simple Home Utility program. It is not clear which download you need but after a call to Al, it was the .MSI version that I needed to run in MS Windows. Being able to look at the real records in the devices and being able to play with the links in a more direct manner has clarified a lot of things for me. I now understand more fully GROUPS and LINKS too. Unfortunately, GROUPS is never referenced when you are working with the EZServe via its web interface. It is thus really difficult to understand what is really happening.
This may help others a bunch… GROUP Number + Insteon Address TOGETHER really define the specifics of what is controlling devices and what is controlled by devices. One item which surprised me and helps clarify things even more is to realize that GROUP NUMBER and UNIT NUMBER when referring to any of the multi-button link devices such as ICON Keypad Link, Remote Link, or anything multi-button. Thus, if you look at the links stored for a keypad device, you will find the group number maps perfectly to the keypad number. How GROUPs are defined for the EZServe itself seems a bit less understandable tho it is clear that multiple group numbers have to be assigned as you add devices.
Further, it is my opinion that the programming that is currently within EZServe is very buggy when it comes to adding and deleting SCENES. In fact, I would recommend against even trying to setup a SCENE using this software as I think it will only get you into trouble. I’ve had multiple situations where I’ve created a SCENE and then deleted it only to find the SCENE is not really gone. To explain a little bit. When you add a SCENE, the EZServe software has to appropriately add links to all the affected controllers and responders to make the SCENE really work. This is no different from doing a manual add of multiple devices to be controlled from a single controller. Where things get into trouble is that I don’t think that SCENE Delete actually works properly in that it really should completely remove all the links associated with the scene from the different devices. This process is complicated and unreliable at this time from what I can see.
I finally used the Simple Home Utility to clean up the links. I also used this utility to further examine and more closely examine stored links. This is generating other questions which I will post as new topics here. Hopefully, this will help all of us.
LeeAnonymousNovember 20, 2008 at 8:09 pmPost count: 29
I have had exactly the same experience with creating/deleting scenes using the EZServe web interface. One of the reasons I was so confused (still am confused on many things) early on was because I was trying to create scenes and then look at the links to see how it worked. The problem was that the software was not creating all of the links it was suppose to, so the scenes never worked and it just confused me. Once you understand what the links are suppose to look like, it is pretty easy to create scenes manually once you understand how to add links with the SHN utility. I also had the same problem with deleting scenes and ended up having to edit the devices3.xml and scenes.xml files to get rid of them.
- You must be logged in to reply to this topic.