Ross

@glacier991 Off topic, but I usually am... I, and a few others on this board, gave up on the Wireless tags as I found them unreliable. I had to go take out and put in the batteries one too many times as they lost connectivity with the hub. If that's not happened with yours, that's great. I changed to Yolink sensors and they have worked flawlessly with a much better battery life. Just my 2 cents, Ross

Don't laugh, but I still use the old Insteon 2441TH thermostats. However, I've rendered them dumb and use a Yolink sensor (via the Plugin and programs) to control when they turn on and off. I place the Yolink where I want to measure the temperature as the thermostat is kind of out of the way and I don't really care what the temperature is at that location. I do care what the temperature is at my couch in the living room and in my bedroom. I installed a heat pump last year and it all still works as before. Ross

I was hoping for fewer taps to mark them read; and now we may have a additional confirmation dialog to tap. I understand that we all use these a bit differently: Kentinada likes my idea, but DennisC and dex like it another way. Perhaps there could be a setting asking how to mark them "read". Thanks as always, Ross

@Kentinada It would be nice if the blue dot went away as soon as one goes to the notification page (similar to how an email is considered read once it's looked at). I'm not sure why there is the extra step of having to tap on it. Ross

@wrj0 There are many ways to capture temperature at your location. You may want to move away from a service like OpenWeatherMap. Yolink has a great temp sensor (you also need a Yolink hub) and there is a good Plug-in for it. And the batteries last for ages. There are other cheaper and much more expensive options (including having your own weather station). I still use OpenWeatherMap for forecasts and rely on it to determine whether to run my sprinklers or not. Ross

@ISY4Me I just downloaded the NS. My Moon Phase number is now 21.34 (at 7:10am Pacific on Jan 4,2023). It should be the age of the moon (in days) since the last new moon. However, I just searched online and the moon is currently 22.55 days old. So, the number doesn't make sense to me. The azimuth and elevation do appear reasonable; however, I don't understand Zenith. I think we should monitor the moon phase until the next new moon on Jan 11 (3:57am Pacific) and see if it starts over. I don't know enough about NodeServers to see what math it's using. Here's an explanation of the Age of Moon (sorry if you already knew this): https://in-the-sky.org/article.php?term=age_of_moon. If you don't mind: when I clicked on More Info, I just got a Not Found page. Did you use meters or feet for your elevation? Ross

@tlightne Thank you. I clicked on "Reinstall here?" and it did upgrade. Ross

@bpwwer Hi Bob, I am on v3.1.4. I thought all I had to do was to Restart the plugin and it would automatically upgrade to 3.1.8. However, it appears I'm still on 3.1.4. Do I need to re-install it? @Andy P Thank you for bringing up this topic. I've noticed for awhile that this was always zero. I just figured that's the way it was. I'm happy to have better-minded folks in this forum who think of things that I don't! Ross

@n4bos Glad you're up and running again. I am interested in the leak detection report programming/Resource. Would you mind leaving some breadcrumbs here as to what you've done? Thank you, Ross

Kasa NS also showing disconnected for me.

The Yolink devices have worked really well for me (I only have wired and wireless temperature sensors so far). I had nothing but trouble with the CAO Wireless tags. They would stop reporting and I'd have to go and remove/install the battery to get them working again.

@johnnyt I have had DST issues in the past, but I didn't this month. Maybe it's only the "Spring Forward" time that I have issues. However, I do occasionally have an issue where my Polisy and ISY stop talking to each other if I have a power outage. I bought 2 Kasa plugs and plugged the ISY and Polisy into each. Kasa has a simple app to turn the plugs off/on. I was recently in Japan and received an alert that my house had a momentary power outage. And afterwards, my Polisy wasn't talking to my ISY (I could tell that the weather info wasn't being updated). I simply opened the Kasa app, turned the Polisy off, waited 1 minute, turned it on - and all was well again. Just a note that I first turned the ISY off/on, but that didn't change the situation. So, maybe the Kasa plug only needs to be used on the Polisy. I believe there is a Kasa node server - so what I did above might be able to be automated through an ISY program. However, I like the app just in case the ISY needs a hard reboot as well. Ross

@pz1122 I prefer text messages to other methods of receiving info from the ISY; however, about every 4-6 months, things go wonky. The carrier (mine is Verizon) throttles the messages and either none come through or they're delayed. Things go back to normal within days or up to 3 weeks. When this happens, I change a variable and then the ISY also emails me the message. When the texts start working again, I change the variable back and I only receive texts. I wish notifications in UD Mobile acted the same way as text messaging - it's close, but you still have to do an extra click or two to clear the message. Ross

Thanks @MrBill. I do understand Rain Storm, it was the 709 number that threw me. I figure rain_storm_last is probably the last storm and rain_storm is the current storm.

@bpwwer If available for the DavisWeather node server, I would enjoy having rain_storm. Although, I don't know what the 709 represents, I'm sure I could figure it out after a storm. I also don't know how that differs from rain_storm_last. No hurry - it's not going to storm in San Diego until October

My ST-Sonos NS fails about once a week or even longer now (it failed either today or yesterday), but it's not every 3 days when I started this topic. @bpwwer In your 2nd March 31 post above, you mention that you'll be monitoring the situation. I assume you haven't seen anything since then? If not, would you kindly prompt whomever it was you were engaging to get a status update? Thank you! Ross

@macjeff 1) I found an Excel formula for Easter online (assumes the Year is in A1): =FLOOR("5/"&DAY(MINUTE(A1/38)/2+56)&"/"&A2,7)-34 I can't vouch for it, but I've checked several dates and they appear correct. Now, you "just" need to put it into ISY math. 2 There is a HolidaysGoogle node server. I don't use it, but Easter might be included. 3) The Timedata node server has a "Days since Unix Epoch" number. You could brute force enter 25 variables with the next 25 Easter days and run a formula at 12:00:01am checking to see if this DsUE= one of those 25 variables. This will keep you going until the year 2048. The EISY might be a museum piece by then. Good luck, Ross

@TriLife The DavisWeather NS (used if you have Weatherlink IP) has a field "High Rain Rate". You might be able to use that if it exceeds a threshold. I don't use it; so, I don't know when it resets (at the end of the hour/day/storm).

@TriLife In case Bob's response is that the NS's are providing all that there is to provide, you can write programs to determine when a storm begins depending on your definition of a storm (mine is .02 to eliminate dew days) and when it ends (mine is 24 hours after the last rain). Hourly and daily accumulations can also be determined with programs and variables. I'm not sure how one would record "current rain rate" as it changes minute by minute when it's raining.

@photogeek54 The node server runs well and is exactly what I was looking for. Thank you! I aspire to be able to do what you did; however, I'm afraid I don't even know where to start. I need a Node Servers for Dummies book. Everything I've seen online quickly goes into Beautiful Mind territory for me. I notice there's a few things in the NS that are blank for me because I don't have the inputs. Just curious what SolarEdge product would allow me to see, for example, Consumption? I assume this NS is ready for the production store. Thanks again and thank you to @bpwwer for assisting us here. Ross

@photogeek54 @bpwwer Thank you both. It's now connected. I see 5 nodes: my name, Energy Last 15min, Energy Today, Inverter 1 and Production Overview. I'll keep an eye on it for a few days and report back to you. Many thanks, Ross

@photogeek54 Just to clarify and sorry if I use the wrong lingo: My PG3 resides on my Polisy and my ISY resides on my ISY994. I've never used the ISY on my Polisy (IoP). When I deleted the NS and reinstalled it, I did it on the PG3 on my Polisy just as I did before. I believe (but I certainly could be wrong) what @bpwwer was saying is that the NS was trying to contact the ISY on my Polisy (since it was having an issue with 192.168.1.6 which is IoP). I don't think it should care what is going on with that ISY since I loaded it for the ISY on the ISY994 (192.168.1.3). As far as I know, I don't have any problems with my Polisy as all of my other NS's are working. And I don't believe I have the necessary skills to fix a Polisy programming problem in any case. Let's see what Bob says after he reads the posts after his. I appreciate your help, Ross

@photogeek54 @bpwwer I deleted the NS and reinstalled it in slot 9 (for the ISY on my ISY994 which resides in my "cave" - not on the ISY on my Polisy). Please see attached which shows that I downloaded it to my ISY994. All my other NS's are connected. I also attached another PG3 log. I did all of this soon after 19:55 on 4/28. Perhaps this is an Eisy v. Polisy thing? The Eisy has the same IP address as PG3 (I assume) whereas I have 2 different IP addresses: ISY994 is on 192.168.1.3 and the Polisy/PG3 is on 192.168.1.6. Perhaps the old version I have is affecting it? My Polisy is on 3.1.13. I'm not sure if that makes a difference or not. I ran into trouble updating it a while back and haven't had the time to focus on it. My ISY is 5.3.4. I'm happy to keep plugging away at this if you are. Thank you, Ross pg3_4-28-2023_75940-PM.zip

@bpwwer 192.168.1.6 is my Polisy. I see ISY/IoX on there (when I launch), but I don't use it. I use my ISY at 192.168.1.3. I'll reload the NS this evening (Pacific time). I have 10 other NS's and I haven't had an issue like this with them. Maybe I selected the wrong IoX. But, the NS showed up next to all of the others - just disconnected. Thanks for your assistance, Ross

@photogeek54 and @bpwwer Per your request, I deleted the other SolarEdge NS. And, as you surmised, it didn't fix the Disconnected Status for the solaredge_poly NS. I have an ISY994 and a Polisy. From what I've gleaned in these forums, NS's should work the same on Polisy and Eisy. I'm attaching another Log (from the PG3 menu) after deleting the other SE NS and restarting/stop/starting your NS. pg3_4-28-2023_70104-AM.zip