wuench

Bump.... I am interested in this as well.

Yeah, thanks. Looks like noise issues, then. I unplugged my PLM and plugged it back in and was able to add one device. Unplugged a powerstrip in a nearby room and was able to add the other. I gotta say, in my experience, dual band is a BS gimmick. I have almost completed my dual band conversion and should have complete coverage now. But my network is now less reliable, especially since switching to a dual band PLM. I thought adding more devices would give me better coverage, but things are getting worse. My old V1 single band network was way more reliable...

I just installed to Switchlinc Dual Band Dimmers (2477D) and neither is discoverable by the ISY. The device versions are 6.6 and 6.7. No idea what firmware that is. I tried, Automatic, Device Reported, and I1 Only. The log is below, looks like there are ACKs, does that mean the devices are talking back?. I have been having a LOT of trouble lately adding new devices. It seems like all of them are responding in the Event Viewer but the ISY is ignoring the responses. All my other devices I was finally able to add through multiple retries and rebooting the ISY. This time no luck... Sat 11/17/2012 03:28:41 PM : [xx xx xx ] Added to list of devices to link to ISY Sat 11/17/2012 03:28:41 PM : [iNST-TX-I1 ] 02 62 xx xx xx 0F 0D 00 Sat 11/17/2012 03:28:41 PM : [iNST-ACK ] 02 62 xx.xx.xx 0F 0D 00 06 (00) Sat 11/17/2012 03:28:50 PM : [iNST-TX-I1 ] 02 62 xx xx xx 0F 0D 00 Sat 11/17/2012 03:28:50 PM : [iNST-ACK ] 02 62 xx.xx.xx 0F 0D 00 06 (00) Sat 11/17/2012 03:28:59 PM : [iNST-TX-I1 ] 02 62 xx xx xx 0F 0D 00 Sat 11/17/2012 03:28:59 PM : [iNST-ACK ] 02 62 xx.xx.xx 0F 0D 00 06 (00) Sat 11/17/2012 03:29:03 PM : [xx xx xx 0 ] Failed to add device

Would you please consider making them optional as a feature request for a future release...

Is there a way to turn off/prevent the popups at login (could not communicate with xxx)? My Insteon network is far from 100% reliable and I usually have to clear several popups on login. I would rather just check the log for this info.

I have not tried the event viewer I will take a lot at it. As far as the 3 busy dialogs, I didn't mean concurrently, I mean whenever communication fails I get multiple system busy dialogs in a row, and when there are links etc being tried it can be more and when there are multiple devices involved like in a PLM restore it is more still. I like the dialog where I drag several devices to a scene, it would be nice if the other types of tasks displayed a dialog like that, listing all the tasks. And if multiple attempts are made in failed comm what I did in my Insteon program was display (try 1 of 3) type info instead of repeating 3 dialogs in a row. So I would summarize my issues to being poorer performance from the new PLM and trying to do the restore under those conditions. I was able to solve most of the issues by putting a filter on a UPS with the same circuit as the PLM. It wasn't needed with the old one. Once I got communication working doing the replace PLM did nothing, things were in a bad state, I had to rebuild all my scenes from scratch. I also tried to replace two devices on one circuit after that (one dead Switchlinc and one 1000W Switchlinc exhibiting the flicker issue, old devices). I replaced the switchlinc with a dual-band model, after that I was have a hard time communicating on that circuit again. I found that switching from Automatic to Device Reported under advanced seems to "fingers crossed" have fixed the issues with that circuit. I don't really blame you guys or the ISY for this. There is definitely something different/worse about the dual-band PLM's powerline signal level. Like I said I wrote an Insteon program back in the early days, I abandoned it after struggling with all the effort involved to overcome all of Insteon's shortcomings with single byte communication, long delays, etc. So I really do understand and I think you've done a great job, best job so far, in overcoming those. Just if you see an opportunity to give the user a little more feedback when doing long/multiple operations it would be nice...

I have no wireless devices, firmware is 3.1.14. I have had occasional issues where a device didn't respond so I my plan was to start putting in dual-band devices from now on to help reliability, ha. The plugin point is the same for the PLM. The only thing I can think of is it is more prone to noise or has a weaker signal than the original PLM. The devices that are not responding are on both circuit legs, but a lot of them are on the same circuit. I am in the process of moving my access points around to see if I can fix the issues. I also have a couple of dual band switchlincs that I could use to replace some switches, but I a little leary of doing anything right now until I get all the current devices to at least get their links updated from the new PLM. I don't blame the ISY at this point, it seems to be Insteon signal issues with new PLM. But I do blame the ISY for being so poor at telling me what is going on. If I query it should display one busy dialog, not 3. And if it is gonna query all the devices then it should list all of it's outstanding tasks, instead of the busy dialog over and over. There is huge room for improvement there.

Well I have been a happy ISY users for years. I have around 3 dozen devices. Having written my own app for Insteon I understand the "quirkiness" of the protocol and how hard is must be to support for UDI. Today I decided to replace my PLM with a dual band model. I came to the forum first and looked for any gotchas, read the wiki and it all sounded easy enough. Well after replacing the PLM according to the Wiki instructions I logged in to find the ever scrolling dialog. System busy 0...100, system busy 0...100, system busy 0...100 and over and over and over. No indication what it is trying to do. Finally it started throwing errors can't talk to device 1, can't talk to device 2, and on and on. Ok that seems reasonable. So once it seemed to settle down, I did the Restore PLM. Now I am in this boat where some of my devices still can't communicate, it's hard to tell some have the little 1011 icon, some exclamation marks, some seem ok. This has been going on for a couple of hours now. Like I said I understand that Smarthome jacked up the protocol in myriad of ways. UDI is doing their best. But the one thing that would be nice, is if when the ISY has a ton of stuff to do to list it out instead of popping up endless System Busy dialogs over and over and over and over and over.... It's really frustrating to not know what is going on. I am not sure what my next steps are or where I end up. Right now I am thinking I may have to just rebuild everything from scratch and/or return the PLM and maybe even consider switching to UPB cause I am kinda getting sick of all the Insteon issues.

I reported this not working in the 3.1.12 thread although I did see my rule fire once, when I disconnected from the Elk using ElkRP. I have two rules, one to email upone Elk System is Connect and one for Elk System is NOT connected. Never saw the NOT rule fire...

Another change from using Elk rules... When I set a rule with an If "Arm Up State" it triggers when the system is armed and after any zone state changed thereafter. I have the following rule that I would like to shut off lights after my exit timer expires. It works but in the logs you can see it triggering over and over as my internal motion detectors are triggered. I could get around it by setting a flag with variables, but it is unexpected behavior.... If Elk Area 'Area1' 'Arm Up State' is Armed Fully Then Set Scene 'Scenes / Outside Front' Off Set Scene 'Scenes / Downstairs All' Off Set Scene 'Scenes / Tree Lights' Off Else - No Actions - (To add one, press 'Action')

Yeah, thanks. Converting these rules from Elk format to ISY is a little tricky. Would've been nice to just have an isNight, isDay like the Elk. I duplicated it with variables though and replaced the code above. Hopefully it'll work, we'll see over the next few days....

The act of closing the door is causing the program to re-evaluate during the wait period. You will have to break this program into two programs. Have this program turn the scenes on when the conditions are met. Have the second program turn off the scenes after 10 minutes. Tim Thanks Tim. That worked.

I have an issues in 3.1.12 with programs not completing. I have a program that, based on a zone trigger on the elk, turns some lights on, waits 10 minutes, then turns the lights off. When running the rule via the Run Then it works as designed. But when I open the door and close it, the program turns the lights on but does not continue, the lights stay on indefinitely. When viewed in the program summary it runs in 1 second. If ( Elk Zone 'Front Door' is Violated Or Elk Zone 'Garage Side Door' is Violated ) And From Sunrise To Sunset (next day) Then Set Scene 'Scenes / All Landscape' On Set Scene 'Scenes / Outside Front' On Wait 10 minutes Set Scene 'Scenes / Outside Front' Off Else - No Actions - (To add one, press 'Action')

How do we access the 1_fam.xml file? What is the URI for it?

You can also configure any windows pc to serve time. http://support.microsoft.com/kb/314054