robl

I have problems with this latest ISY 5.x release, hue and polyglot, and using fade up/down/stop to control colors. > ISY becomes unresponsive, requiring AC hard reset. Error log says: System -170001 [UDSockets] HTTP:27 error:6 Here's the program: if remote control - D is switched fade up then repeat every 1 seconds $lauren_hue += 6000 set hue bridge/lauren1 set hue '$lauren_hue raw' set hue bridge/lauren2 set hue '$lauren_hue_raw' I have 2 other helper programs: If lauren_hue var grows too big, it resets it to 0. If fade stop is encountered, it kills the program. A few questions: Is this a poor way of going about this? Can you suggest an improvement? Perhaps main program starts a 3rd helper program that waits 15 seconds and then kills the fade up program, in case fade stop is missed? or perhaps I do a repeat 20 times and add a sleep 1 second statement? Any idea on how a once/second command can completely overwhelm all ISY resources requiring a hard reset / power unplug? This seems really fragile ... This fragility seems to have arrived with 5.x, 4.x seemed like it was consistently faster to respond and much more stable. Thanks for any help!

Hmm, it works with my ubiquiti stuff, but setting it up was a real pain. The wifi only worked with old clients, and I had to borrow an iphone. No go with my android phone or tablets. Bummer,. I'd hoped they'd fixed it by now!

I used both in conjunction with each other: Bulitin IR reader on the ISY, Harmony actions would send a special ir code to identify themselves so the isy could track IR blaster (wf2ir) to blast commands out to harmony and the other devices. I used a cgi-bin perl script and network commands from isy Harmony for the great remote control when there in person IR distribution repeater IR emitters in front of devices and raw IT into 2 receivers Some care was required to be sure the IR out from the blaster and from harmony could fee into the IR distribution and not also go through other emitters (which confuses devices) One of the more complex scenarios was to train Harmony to send an IR code to turn my 4k disk player on. Stupid thing only has power toggle. So with a current sensor, ISY is able to interpret the harmony created "fake ir on" to decide if the power toggle was needed or not. Another complex scenario is to power detect when the TV is manually turned on to then turn on all the other AV equipment. I had to disable the "tv off" turns everything off - sometimes false positives were really disappointing. :) With node services, I see a vast simplification of the stuff above. :) Much simpler to extend some of the AV node servers to understand my system and do the same as my cgi-bin perl scripts. Also, the Harmony node server on ISY makes my cgi-bin running harmony.py no longer necessary.