robl

nevermind ... looks like attempting to connect to / via http fails with connection refused, but going to /login works. Of course, if I hadn't posted I'd still be stuck.

I haven't logged into the polisy device for several months. I decided to see if some new integrations were there (myq) but I couldn't connect to it via the web anymore. I power cycled the device, which has fixed this in the past, and still have the same issue. I looked up both the wifi and lan ip's and can ping them, but no web access. I'm able to login as the admin account - running ps -ef shows very little running on the device. Is there something I can do to further diagnose the problem and/or start things up? I tried running init 4 just in case, but admin account != root. Thanks for any help!

Thanks, filed! In the meantime, I replaces the SD card, and restored a backup, and the isy unit is behaving again. That was probably it! I had been using a regular SD card (samsung evo), and placed an order for a samsung pro endurance card. Any suggestions? Thanks @Michel Kohanim for the quick response & tip to apply the upgrade before the restore. (and not after)

Hmm, I swapped out the memory card, it booted, restored old backup. As usual, it takes a long time to process/finalize boot. When I came back to the PC, the admin console had lost connection. Killed it & ran again, and like before, it can't find the ISY. (isy finder) Refresh isn't finding it, but if this is like before, eventually something will pop up and then not work correctly.

I've been using 5.2.0 successfully for a few months. However, last night, the ISY was unresponsive again, requiring a reboot. Third time in 24 hours. It's hard to get the admin console to connect, and when it does, I'm getting this error: XML Parse Error: http://192.168...:80/desc Ideas? Is the unit fried? Maybe my SD card? Thank you for any help!!

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.

FYI, for others going down this route - it mostly works. A few notes: ssh to your polisy, go to the nodeserver dir for sense. sudo pkg install py37-aiohttp run install.sh and make sure it installs properly create custom parameters for email, password, and update_realtime. Not sure what update was supposed to be set to, I used 1 and nothing failed. I set it to 0 and no errors either. Email/password are what you use for the sense app on your phone/tablet. be patient, it creates drivers in ISY for all your sense devices. This can take a while. My ISY admin window hung when I attempted to ungroup the devices while it was updating. after I restarted the ISY admin window, all was good. for a little more info, look at the README.md file in the nodeserver dir. a query of a sense device or overview in ISY doesn't seem to do anything, you need to wait for the next poll. It'd be nice if this would force a poll on that device. A few gotchas / issues: when trying to debug by looking at the log window in polisy, I found it wasn't updating properly. I had to refresh the web page to get the new lines. I finally resorted to tail -f on the log file. like other nodeservers in polisy, after the devices had been created, I found some were grouped, some were not. I did an ungroup and group and got them in 1 spot. Here's my sense screen below. The per-device screens are a bit different, but tell ongoing energy load and on/off, etc. from the logfile I see it's "updating all drivers to ISY" for each device about once a minute. Likely the short poll? I'm not sure all the data values are correct - perhaps units are off or it needs to run for a bit. Daily usage = 8 watts? I don't think so. I'm usually about 33Kwh. But the current energy usage and current solar power look correct. The BIG item for me is the current usage and solar power generation. I had an inverter failure and took a while to notice - now I can write ISY rules to look for a few days of 0's and to let me know. I found the overall numbers (sense device attributes) only update during long poll, which I made faster to every 5 minutes. Oops, later on this seems to be stuck again, not sure why. Sense has a lot of promise, but not sure the devices are that reliable. It find things, sometimes 3-4 times, and doesn't always mark them on or off. I don't think it too reliable for actions on devices on/offs, but perhaps that works better for you. Also there will be a delay as the nodeserver is polling sense for updates, as opposed to event notifications. This means a device could go on, but you won't know until the next polling interval. (default 1 min later) Watching the log file there are some unexpected things: query, unable to retrieve Sense Monitor usage: 'Senseable' object has no attribute 'rate_limit' ./sense_poly.py:71: ResourceWarning: unclosed <socket.socket fd=8, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.x.x', 61651), raddr=('34.231.x.x', 443)> updateDevice: API call timed out So far these errors or warnings don't seem to affect me, YMMV.

Thank you!! It's installed now, on to the next step of configuring it.

Does anyone else use Sunrun? I was on hold for 2 hours with SolarEdge and they said they can't provide access to the Admin tab to get the API key and that I needed to ask SunRun instead. I purchased the system (not lease) from Sunrun. I called Sunrun, and the best way to describe their support is "confidently deliver complete mis information while frequently putting you on hold". After a wasted morning, they refused to enable to admin tab. Has anyone had success with them or know of the magic phrase?

Awesome - thank you! How will I know & get the libraries? Is it just checking for and installing updates from the Polisy web UI?

Hi Michel, SenseMonitoring needs multidict, TotalConnect needs lxml.etree. Both may need additional python packages, it's failing for me at this step of the process running install.sh. If you're able to build all the node servers on a spare polisy, it would help tremendously too! Rob

Just got the polisy unit today, installed sense energy from the nodeserver store via the ui and .... it doesn't easily work. Has anyone else gotten it to work? by default the log complains about missing libraries ssh to polisy for more details found that lots of python libraries are missing. the install.sh script attempts to install most? all? but runs into errors. latest one to give me grief is aiohttp python library. error message is cc (c complier) is not found on polisy. Anyone know how to get the C compiler on polisy? I can't seem to find yum or apt-get on the polisy system. Is there some other command I need to use? Ah - I see from the following post that universal devices is planning that no node servers need compilers, but that they weren't all properly checked. Does this mean that this sense nodeserver should get upgraded to no longer need cc? Looks like the command to install thinks is "pkg install". I'm not familiar with it, and trying cc fails. (not found). Running "pkg search cc" also doesn't find the C compiler. Stuck. Any suggestions? @Michel Kohanim? Looks like Total Connect (for thermostats) also has similar issues. I had to ssh to run its install.sh script, which loaded many missing dependencies, then failed on lxml.etree which also needs cc to compile. Polisy is a great device, but needs more polish before non-technical people try to use it ... Thanks!

@MWareman, thank you for the great explanation. Seems like a gap to me in the standard. I'd hope there would be workarounds where ISY could host a javascript file that creates the websocket, and then include that from my rPi dynamic html, but imagine even if it does work, it'd likely run afoul of the cross-site scripting checks. For me it's very dynamic content, html created from a perl script, after it's read all my ISY devices, and formatted the output into custom report tables. Beyond the capabilities of ISY. I sometimes wish ISY ran on a rPi open platform. I'll check out the reverse proxy, thank you for your help!