bclarke01 Posted October 4, 2009 Posted October 4, 2009 My setup presently is around 97 devices controlled by 30 KPLs and a handful of SwitchLincs. Periodically I like to reload the devices to ensure that they and ISY have the same idea of what is real. For some reason, I frequently get stray devices picked up into scenes unexpectedly. To restore devices it appears one can either request all devices or do them one at a time. With this many devices, the 'all' restore runs all night and is still not done in the morning. And this is usually overkill; there are usually only a handful of misbehaving controllers and devices Is there a way to only get the controllers and devices involved in a particular scene to be restored? Lacking that, is there a way to specify a handful of devices get restored rather than the entire system? Finally, it would be really nice if there was a separate log kept during the "all" restore of only those devices / controllers which failed to accept their programming. Scanning the log containing thousands and thousands of Insteon transactions is difficult when one is not sure what one is looking for. Bruce Clarke Los Altos, CA
Michel Kohanim Posted October 4, 2009 Posted October 4, 2009 Hello Mr. Clarke, You are absolutely correct: you can either restore a device or all devices. I am going to have both of your requested features included in our requirements list. This said, however, I would be very interested to know why you would have unexpected links in your devices. With kind regards, Michel My setup presently is around 97 devices controlled by 30 KPLs and a handful of SwitchLincs. Periodically I like to reload the devices to ensure that they and ISY have the same idea of what is real. For some reason, I frequently get stray devices picked up into scenes unexpectedly. To restore devices it appears one can either request all devices or do them one at a time. With this many devices, the 'all' restore runs all night and is still not done in the morning. And this is usually overkill; there are usually only a handful of misbehaving controllers and devices Is there a way to only get the controllers and devices involved in a particular scene to be restored? Lacking that, is there a way to specify a handful of devices get restored rather than the entire system? Finally, it would be really nice if there was a separate log kept during the "all" restore of only those devices / controllers which failed to accept their programming. Scanning the log containing thousands and thousands of Insteon transactions is difficult when one is not sure what one is looking for. Bruce Clarke Los Altos, CA
bclarke01 Posted October 5, 2009 Author Posted October 5, 2009 I have absolutely no idea. I do know that after I factory reset all controllers and devices and then run "ISY Restore" on all devices, I then run "Show Device Links table" on an 8 switch KPL and ask it to compare to the PLM, I get LOTS of "Extra Record" items. Specifically, "Show" reports the KPL having a count of 63 items in the memory. "Compare" reports that the first 25 are "Identical", the next 35 are "Extra Record" and the last three are "Ignore" (but are not zeros). So there is pretty consistently one or two keys out of the 8 that are misdirected. ISY detected this KPL as a 2486S/WH6 keypadLinc relay v.33 if that helps any. Is there a thread on the Wiki that describes how to read the output of the various diagnostics? Bruce Clarke
Michel Kohanim Posted October 6, 2009 Posted October 6, 2009 Hello Mr. Clarke, We have had reports of defective devices where factory reset didn't clear out all the links. This said, however, I cannot be sure that your falls into this category. Did you import existing links when you added this device to your ISY? Here's a link to our Wiki: http://www.universal-devices.com/mwiki/ ... Tools_Menu ... please check the Diagnostics section and scroll down to read about different options. With kind regards, Michel I have absolutely no idea. I do know that after I factory reset all controllers and devices and then run "ISY Restore" on all devices, I then run "Show Device Links table" on an 8 switch KPL and ask it to compare to the PLM, I get LOTS of "Extra Record" items. Specifically, "Show" reports the KPL having a count of 63 items in the memory. "Compare" reports that the first 25 are "Identical", the next 35 are "Extra Record" and the last three are "Ignore" (but are not zeros). So there is pretty consistently one or two keys out of the 8 that are misdirected. ISY detected this KPL as a 2486S/WH6 keypadLinc relay v.33 if that helps any. Is there a thread on the Wiki that describes how to read the output of the various diagnostics? Bruce Clarke
bclarke01 Posted October 6, 2009 Author Posted October 6, 2009 I haven't had a chance to read the suggested link; will get there in a moment. Did just get the following display on the telnet session when I attempted to restore a KPL. http://192.168.0.9> LOGGER: -2 : n=[10 5 36 1] c=[ ] a=[ ] H_ERROR:-5012 : H_ERROR:-5012 : H_ERROR:-5012 : H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 H_ERROR:-5011 : uuid:00:21:b9:00:d1:49,1 LOGGER:-5012 : n=[null] c=[null] a=[null] LOGGER:-5012 : n=[null] c=[null] a=[null] LOGGER:-5012 : n=[null] c=[null] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] LOGGER:-5011 : n=[null] c=[uuid] a=[null] Does any of this suggest anything to you? Bruce Clarke
bclarke01 Posted October 6, 2009 Author Posted October 6, 2009 Unfortunately the suggested thread does not describe what interpretation to make for the output of the Compare command. That would be really helpful. Yes, some of the devices had links already in place when ISY "learned" them. But since then, all have been factory reset and restored by ISY. So if anything is now amiss in the device tables, ISY put it there. Bruce Clarke
Michel Kohanim Posted October 6, 2009 Posted October 6, 2009 Hello Bruce, The errors (5011, 5012) mean that the Admin Console was not closed but shutdown and thus ISY is expiring the subscriptions. The compare function only compares what ISY thinks a device should have and what the device actually has. So, it would be unlikely (unless a bug) that ISY programs things into the switch without first having it stored in its configuration file for that device. Now, with respect to interpretation, there are only four variations: [identical] ... the device has what it should have based on what ISY thinks [ignore] ... these records are after the high watermark (have 0 on the first byte) and even though they are there, ISY ignores them (and so does the device) [extra] ... these records are at a position where ISY considers the end of the database. They should NOT be there [mismatch] ... these records are completely at the wrong place With kind regards, Michel
bclarke01 Posted October 7, 2009 Author Posted October 7, 2009 I believe I got here by having used some of the Smarthome software to get started programming some scenes. I then made the mistake of bringing these into ISY without allowing it to clear the links. I went through a third of the switches and devices this morning first deleting all scenes defined for them, then removing them from ISY. I then did a factory reset on every single device. Next went through and allowed ISY to discover each of the products and went back through and created all the scenes just in ISY this time. I now have a solid implementation that seems to be complete and reliable. Had an interesting problem I'll pass on. Some devices, after being discovered by ISY, didn't want to accept programming. An error was returned during the programming and then then the diagnostic Show Device Links Table showed that it couldn't reach the device. Cure was to interrupt the power to these devices for a moment and return it. I'm guessing that they locked up for some reason and this was a form of soft reset. Whatever, it seemd to work. I have also found that subsequent corrective action pretty much must include deleting scenes and removing the device from ISY and then allowing it to learn it from scratch and clean the links table. Then scenes can be added or defined and will be clean and reliable. Apparently Insteon implementations are not quite standard and compatible at this point. I'm guessing that if I ask HCA or HouseLinc would probably not be very useful at this point (but frankly don't care to try). Thanks!
Michel Kohanim Posted October 7, 2009 Posted October 7, 2009 Hello again, Thanks so very much for the update. I am still a little concerned: you should not have to reboot devices for them to be reprogrammed. As such, may I humbly recommend making a list of all those devices that had this problem, with their firmware versions. If you have any SWL 35s, then that might explain some of this behavior. Otherwise, you might have to check the neutral cable going to these devices. With kind regards, Michel I believe I got here by having used some of the Smarthome software to get started programming some scenes. I then made the mistake of bringing these into ISY without allowing it to clear the links. I went through a third of the switches and devices this morning first deleting all scenes defined for them, then removing them from ISY. I then did a factory reset on every single device. Next went through and allowed ISY to discover each of the products and went back through and created all the scenes just in ISY this time. I now have a solid implementation that seems to be complete and reliable. Had an interesting problem I'll pass on. Some devices, after being discovered by ISY, didn't want to accept programming. An error was returned during the programming and then then the diagnostic Show Device Links Table showed that it couldn't reach the device. Cure was to interrupt the power to these devices for a moment and return it. I'm guessing that they locked up for some reason and this was a form of soft reset. Whatever, it seemd to work. I have also found that subsequent corrective action pretty much must include deleting scenes and removing the device from ISY and then allowing it to learn it from scratch and clean the links table. Then scenes can be added or defined and will be clean and reliable. Apparently Insteon implementations are not quite standard and compatible at this point. I'm guessing that if I ask HCA or HouseLinc would probably not be very useful at this point (but frankly don't care to try). Thanks!
Recommended Posts