Ross

@dakall Agreed. They happen to be 6 hours after sunrise now because we are near the equinox (which took place on 3/19 at 8:06 PDT). And, I rounded. But the average of sunrise/sunset should work for any day of the year.

@peterathans I'm trying to think how DST matters. Currently (now DST), sunrise is 7am and sunset is 7pm. The average is 1pm which is solar noon. Two weeks ago (standard time), sunrise was 6am and sunset was 6pm. The average was 12pm which was solar noon. As long as the DST time change occurs at night (2am), I think the average calculation works. But please prove me wrong - you wouldn't be the first! Ross

@dakall "I know there are variables for sunrise and sunset, but I can't average them together successfully." Can I assume that averaging sunrise and sunset times will be good enough to determine solar noon? This seems reasonable to me, but I don't know if I'm missing something astronomy-wise. If it is good enough, then can I assume the issue is getting the EISY/ISY to calculate the correct math? As an aside, solar noon only varies by half an hour during the year. It's 15 minutes off in early February and early November. It is not centered on noon; however, unless you happen to be on the exact longitude for your time zone (e.g., 90W for Central time). You need to add/subtract 4 minutes for each degree of longitude you're west/east of your standard longitude (75 ET, 90 CT, 105 MT, 120 PT in the US) to get your local "standard" noon.

Please see my 2 posts here (the other posts went a different direction).

I did this with the ISY. I assume that the EISY would be similar. Please look for both of my posts - the other posts went a different direction.

There is a way to post data to a Google Sheet. I post data once per minute to a sheet. I think there's a maximum # of rows one can post. Therefore, I clear my sheet (automatically) at 2am. I just want current data. If you're only going to post once per day, you can certainly have a year's worth of data in there.

@paulbates "The only challenge was my first use of the 8003 temp humidity in my bathroom to operate the vent fan when the humidity rises. Since humidity is relative, I couldn't put a raw value (like 45%) in the program as it moves around." Even though the relative humidity is relative, I would think you'd be safe running the vent when it gets above 85%. That's considered "wet" in meteorological circles. At 85%, the dew point is pretty close to the temperature resulting in surfaces "sweating" regardless of what the temperature actually is. Possibly start there and wander down to your liking. You could also use a dew point calculation (anything with a DP > 60), but putting that formula in a program is above my pay grade. I have the formula if you want it. However, it might be easier saying If temperature >70, then RH > x. If temperature <70, then RH > y. Ross

Thanks for the idea and I'll take a look to see if it's off on a consistent basis. I'd still have to waterproof the whole thing and I don't trust my ability to achieve that. I'd rather take my chances on soldering a longer cable. Ross

My wish list is a wired Yolink temperature sensor where the cable is about 1 foot longer. I bought 2 of them and tried to splice the cable, but the readings were off. I would have then had to waterproof it anyway which I don't think would have been successful. The cable appears to be proprietary; so, I don't think I can just use an off-the-shelf temp sensor cable. Ross

I really like the Yolink line and I appreciate @Panda88 for the plugin!

@glacier991 If you mean the Plugin - it works great. Sign up for an account at Yolink. Enter the UAID and Secret Key into the Plugin (node server) configuration and it automatically finds all the devices associated with your account. They also have a nice app. 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.