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

I prefer receiving texts rather than using Pushover and UD Mobile; however, it's just my personal preference. Geddy and MrBill are absolutely right when they say texts are unreliable. When they work, they work great for several weeks to a few months. But then they randomly shut down for about 2 weeks or so. For me, Verizon was not working at the end of March and beginning of April, but it's worked fine since then. When I notice the texts not working, I change a variable so that the notifications go to UD Mobile (and texts). When the texts start working again, I change the variable back. My notifications are not critical - just informational. If you do have critical ones, MrBill's suggestions appear to be tried and true. Ross

@photogeek54 Attached is my log from the top of the PG3 web page. I don't really know what I'm looking for; so, I'm sending you the entire log. Sorry if it's TMI. pg3_4-27-2023_103016-PM.zip

@photogeek54 I found it in the non-production store and installed it. I copied my key (api_key) and 32-digit value from the other SolarEdge NS. I started, stopped and restarted several times; however, it says "Disconnected". When I click Restart, it updates the Time Started but then instantly goes to Not Running. When I tried to download the log and log package, it says it was doing it, but there is no file in Downloads. I'm happy to troubleshoot this and I'm sorry I don't have more info. Please feel free to ask anything. @Geddy This NS is in non-production. This topic took a turn (for the better), I'm happy for this and future comments to remain here at least until it's up and running on my end; but, I'll leave that to you. Thank you, Ross

@photogeek54 I went to the non-production NS store but didn't see it. What's the name of the NS? I searched for "solaredge", "solar" and "edge" with no luck. Of course, this from a guy who can't find the milk in the fridge... https://polyglot.universal-devices.com/ Thanks, Ross

@Javi I'm not sure this is the appropriate place for suggestions, but I do have a minor one. I have Android. When I receive a notification in UD Mobile, it shows up in the pulldown menu, the little dot appears on the App Icon and, when I open the app, it shows up on the flag on the middle-bottom. All good. To clear the flag after opening the app, you must click on the notification even if it's staring at you. And, you also have to clear the notification on the pulldown menu. One has to do 2 things to clear it (I hope that makes sense). Seems you should be able to clear it by doing one thing. Going to notifications in the app or by clicking on it on the pulldown menu. When I say "clear", I don't mean delete. I just mean getting rid of the pink dot and the pulldown notification because I've read it. When I receive a text and I click on it in the pulldown menu, it realizes that now I've read it and doesn't keep notifying me that I have an unread text. Or, if I go into the messaging app and read it, it removes it from the pulldown menu. I hope this makes sense and is helpful, Ross

This may not be helpful as I don't know the answer to your question, but there is a workaround. I use the Timedata Node server and you can use If statements with that data. Not exactly the ones you pose, but you can get there either with some math or brute force. - Ross

Thanks Javi. The darker font in the body should be sufficient. - Ross

I'm trying out notifications in UD Mobile and I have a white background (better for my eyes). The subject is a nice-contrasting black font on white; however, the body is a light-gray font on white. It's hard to read. Can the body font color (and size) be changed either in Network Resources or in the app? Can I use HTML to format the message in Network Resources? Thanks, Ross

@bpwwer Thanks for the update. I have no idea what it means which means I'm probably a long way from writing my first NS. @carealtor I can't remember the differences in the 2 Sonos NSs; however, I remember being frustrated with the Sonos NS and was very glad when ST-Sonos came on the PG3 scene. I won't bore you with the details, but I have >50 playlists. I press a keypad button or click a link in a Google Sheet and a state variable changes which triggers Sonos to shuffle and play the playlist. The other NS couldn't do that, if I recall.