Ross

I never shut mine down. However, every once in a long while (a week or two maybe?), it gets locked up and I use Task Manager to shut Java down and then I start it up again with no ill effects. I like having it available at all times as I tend to tinker!

My wish was granted. YoLink now sells a temperature/humidity sensor rugged enough for outdoors with a 5' cable. They do suggest you don't subject the unit to too much of the elements (no direct sunlight and don't let it get too wet).

@Kentinada I have 2 YoLink hubs (both non-speaker) connected via ethernet at each end of my house. I can't tell which hub my devices are talking to, but they all work nicely. I was having issues with a temperature sensor being offline at one end of the house (surrounded by concrete blocks). Adding a 2nd hub fixed the issue. Good luck, Ross

I'm sorry to say I had a lot of issues with my Wireless Tags. I had to keep pulling/reinserting the batteries to get them talking again. I switched to YoLink and I have not had a single issue. Good luck, Ross

I don't really know what a syslog is (I even Googled it and still don't understand!). However, I log my variables into a Google Sheet every minute or upon certain events. Works great for me. The thread got somewhat hijacked, but others had input on how they log things.

Just curious. Can one have 2 YoLink hubs? One plugged into an ethernet and the other for a speaker?

@tlhilton As far as OpenWeatherMap not working, please see here:

@MCruzan I use the following program: If 'Nodes / WeatherLink / WeatherLink' Temperature < 150.0°F Then $sAirTemp = 'Nodes / WeatherLink / WeatherLink' Temperature °F Else - No Actions - (To add one, press 'Action') Whenever the temperature changes (assuming the outside temp is < 150 degrees(!)), it will update my state variable "sAirTemp". Good luck, Ross

@apostolakisl Have you upgraded from One Call 2.5 tp 3.0? OpenWeatherMap deprecated 2.5 in June. @bpwwer released version 4.0 of his plug-in to work with One Call 3.0. It's not all that clear on their website, but the free version provides 1,000 calls per day. You can set your limit (change it from 2,000 to 1,000) so you don't go over this number and get charged. If you've already done the above, then I'm sorry - your issue is over my head! Ross

I just updated to One Call 3.0 and everything works nicely. Thank you @bpwwer!

I do about the same: Temp below 75, less watering. 75-90, normal watering. >90, more watering. Turn off the sprinklers based on recent rain (and turn them off for x days based on how much rain). Turn off the sprinklers based on forecasted rain. I have saved $$ with my OpenSprinkler. I created a bunch of programs and my ISY and plug-ins check the forecast and rain totals and then enables/disables the programs as appropriate. Ross

@mbking I assume you're asking this of @bpwwer. I believe that putting his handle in the body of your comment (using the @ sign) will place a notification in his inbox. Good luck, Ross

@Techman I know nothing about UPS's. Would you please make a recommendation of one? If the power does go out, do you have a program that then shuts down the EISY, Router, etc.? I'm not sure how long the UPS can keep things going after the power goes off. Thank you, Ross

@dstanley Hi dstanley, Does your plugin show "Disconnected" when this happens? My st-sonos plugin disconnects every few days and I have to restart it once or twice a week. We tried to fix the issue in the thread below, but it hasn't been resolved. Apologies to @bpwwer as I never saw his last post there until today. Unfortunately, Bob, version 1.0.10 didn't fix my problem. If dstanley's issue is not the same as mine, I'm sorry for hijacking this thread. The other thread was closed by whomever decides that threads should be closed. 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