Ross

I'm just memorializing the current versions based on what I've gleaned above: 994 - 5.3.4 for those using 500 series Z-Wave 994 - 5.0.16c for those using 300 series Z-Wave Polisy IoP - 5.5.5 Polisy PG3 - 3.1.17 Eisy IoX - 5.5.5 Eisy PG3x - 3.1.22

@Geddy To recap, the latest versions are: 994 - 5.3.4 for those using 500 series Z-Wave 994 - 5.0.16c for those using 300 series Z-Wave 5.5.5 for Polisy and EISY. You then asked what version of PG3 he was using. Is that different from the Polisy version (5.5.5)? If so, what version of PG3 is the latest? Thank you, Ross

I also had issues with the wireless tags. Kept dropping connection and I had to keep resetting them. I've had no trouble with YoLink temp sensors. However, I wish the probe for the weatherproof temp sensor was about a foot or two longer. Is that something I could splice or would a DS18B20 (preferred) work? I haven't opened one up (yet). Thanks, Ross

@MrBill I assume your program will work with both motion sensors, though? Thanks.

@PB11 There appear to be a few mini-remotes for sale on eBay if you don't find a good substitute.

@bpwwer Thank you for the response Bob. I understand that this node server is not trying to duplicate or replace a monitoring solution. However, SolarEdge has other APIs which do. I mention one in my other topic located here. But my real questions are 1) How do I go about getting a node server to do its magic on one of the other APIs? 2) If I find one on Github, can I use that on a Polisy? or 3) Can I hire someone to create a node server for me? If so, whom? I thought I read on this forum that if a company or service has an API, a node server could be written for it. These are generic questions not really focusing on SolarEdge. I have a ton of ideas for node servers, but I'm just trying to figure out the best way for me to bring them into existence (I still want my Sonos speakers to give a shout out whenever my Padres win!) I'm not ruling out creating them myself, but I'm not a(n adept) programmer. I understand that the home automation angle might not be readily apparent, however, knowing how much my solar panels generated the previous day/month might play into whether the ISY changes the thermostat setting on my air conditioning in the future to compensate. BTW, whomever wrote the topic subject didn't quite capture what I was looking for (they created this topic from a question I had asked in another topic). It really should be: Can I use node servers other than the ones in the PG3 store? And, if so, how? Thank you, Ross

If I have a Polisy, am I limited to the 100 node servers in the store? For example, I have a SolarEdge inverter for my solar array; however, the node server in the store just tells you that the inverter is working - it has no info regarding the amount of electricity being produced. I know that SolarEdge's API provides this info. If I find a node server that meets my needs, can I go out to Github or wherever and load it onto Polisy? Sorry if I'm not using the correct lingo - I'm talking layman-ese here. Is there someone on the site who can be hired to create node servers? Is there a(n easy) way to create them ourselves? Thank you, Ross

@pjjamesoDid you ever solve this issue? I'm having the same problem. Thanks, Ross

I had a failed NS issue. I stopped the NS, unplugged my Sonos speakers, then plugged them all back in and started the NS. It then worked and has worked since. I was changing playlists really quickly via an ISY program I wrote (testing it) and I feel that broke it (but I don't know for sure and I haven't pushed it since). So, do the off/on thing and see if it connects and stays connected before you actually do anything with it ISY-wise.

More info: From the reading of the SolarEdge Monitoring Server API pdf (linked in my first post) I've determined that the API call that provides the lifetime, current year, current month and current day power generated is: https://monitoringapi.solaredge.com/site/<X>/overview?api_key=<Z> where: <X> is the 6 digit site ID <Z> is the api key. I don't know how to create a node server, but I would appreciate it if someone would please take a crack at it. Thank you, Ross

@bpwwer and Anyone Interested Bob, I believe you wrote the SolarEdge node server. If incorrect, please let me know and, if possible, point me in the right direction. In reading the SolarEdge API manual, PDF here, there appear to be many APIs. The one on PG3 appears to be the "Inverter Technical Data" API on p. 38. Unfortunately, it doesn't provide the data I assume most would want: how much energy is the system producing? I believe the API that divulges energy production is one of the Site Energy APIs on pages 13-23. It would be nice to know how many KWHs the system has produced YTD, MTD and Today. I would appreciate you (or anyone else??) looking into it. I'm happy to test and pay a reasonable fee as the current NS is free. Thank you, Ross

@vbphilI just created this topic. Perhaps if fits what you're looking for.

@auger66 Simplextech (creator of the NS) has stated that he doesn't check the forums regularly. However, if you send him a DM requesting that he look at this topic, he will do so. He did that for me for my pseudo-problem last week that ended up being something wonky with my speakers. Ross

After upgrading Polisy, learning about putty, SSH-ing, Node.js among other things and researching forums about other node server "Failed" issues and sweating about this for a couple of days, I stumbled upon a great idea. I unplugged and plugged back in my Sonos speakers and the node server worked again. Happy New Year, Ross

@simplextech To answer your questions, I am running Polisy version 3.1.13 and Frontend Version 3.1.13. Also, my ISY is 5.3.4. Following your instructions to get the node.js version, I got v18.7.0. @bpwwer The node.js version on my Polisy is v18.7.0. Thanks, Ross

@simplextech I am running Polisy version 3.1.13 (front-end version is the same). I'll need to research how to SSH as I've never done that before. I am attaching a log (not mine) that @auger66 posted back on May 9th in this thread: The errors there "error: POLY: Node a0a654e not found" are similar to my errors; however, I'm not sure how it was resolved. Thanks, Ross . ST-sonos log.txt

Just an update on ST-Sonos Failed. I uninstalled it completely last night and then reinstalled it this morning (trying the old off-and-on technique). Same issue - Failed after a few seconds. I clicked on Download Log and Download Log Package (I'm not sure of the difference) and attached them here. A recurring theme in the logs are: "error: POLY: Node e1c98da not found". Maybe I should install it in a different slot? Thank you for any assistance, Ross ST-Sonos_12-28-2022_73451-AM.zip ST-Sonos_12-28-2022_73443-AM.zip

Thanks @Bumbershoot. Not that I need to reinstall NSs very often, but this tip is helpful. Unfortunately, it did not solve my problem. So, I completely deleted the NS and reinstalled it (losing my links in the process) - and I still have the same problem (Failed). I'll await a response by @simplextech. Ross

When I restart (or stop/start - I've tried both), it says Connected for about 3 seconds and then goes back to Failed. It doesn't appear that anything can be done in Configuration as I have no entries there. I suppose I can uninstall/install the NS. I believe I can do it in the same slot and programs won't be affected. I'll see if anyone chimes in. I've worked with @simplextech before and he's been very responsive. This can wait until after the holidays.

@simplextech and others: Bought this earlier today and it worked for several hours (I did get it to play my Christmas music) but it is now "Failed". I've attached the log. Absolutly no hurry - i can play the music through the Sonos app in the meantime. Thanks, Ross ST-Sonos Failed State 2022-12-24.txt

@PatPend Here is some more info on the subject - and cheaper than the etching: Link to Forum Topic: Printing Insteon Buttons

The door to my tortoise hutch did not open as scheduled at 8am on Sunday morning. I had to actually walk over and hit the door-open button to let the little buggers run free for the day... I do have a Polisy, but this is a straight program on a separate ISY.

My OpenSprinkler (with extender) is on its way. I would prefer to stand on the shoulders of great men and women who have come up with programming for it! Would you please post a (or some) standard and interesting programs or ideas for OpenSprinkler or other systems? I also have a personal weather station and an OpenWeatherMap forecast, so I am also interested in programs that utilize recent/expected rain and/or temperature info to ratchet back or turn off the irrigation. I live in SoCal and water rates are going through the proverbial roof... Always appreciative, Ross

Upgrade went fine. For the first time ever, Polisy/PG3/ISY are all on the current versions. I feel it would be handy if one was notified of a more current version (in Polisy or ISY after you login) similar to how a phone app says you're not using a current version and click this button to update. That would be nice for those of us who don't like to tinker; however, I'm sure there are myriad reasons why it can't or shouldn't be done. Now I need to get UDI Mobile updated and start learning all of the bells and whistles I'm not currently taking advantage of. Watch for me over in that forum! Thanks, Ross

@@bpwwer @MrBill @Geddy I believe I understand now and sorry it took me so long to catch up. I do have an IoP, but I don't use it. I use my "other" ISY which is a standalone. However, I'm gleaning that I can go into IoP, Update Packages, and then my Polisy and/or PG3 will update. Then, I don't have to use IoP again until another update is needed (or until my current ISY dies). I haven't ever SSH'd (word?) and will do so if needed, but I'll try the above instead. Thank you all. I truly appreciate the generosity of your time as I've learned much just by lurking on this board. - Ross