larryllix Posted February 2, 2018 Author Posted February 2, 2018 Did you ever read the upgrade instructions? https://www.raspberrypi.org/blog/raspbian-stretch/ Nope. With all that information out there I wouldn't even know there was any that actually applied or even worked, most of the time. LOL Thanks
io_guy Posted February 2, 2018 Posted February 2, 2018 Lot of fuss over here playing with mono versions. The default mono version in stretch is fine to use. Switching to the mono repo for it just gives you the latest.
rccoleman Posted February 3, 2018 Posted February 3, 2018 The default mono version in stretch is fine to use. That's been my experience. After upgrading to Stretch and updating the one repo line in sources.list to point to Stretch, everything including Nodelink is working fine.
larryllix Posted April 13, 2018 Author Posted April 13, 2018 On 01/02/2018 at 6:31 AM, io_guy said: Larry, if you're blaming your exobee setpoint on NodeLink or the ISY then give me a log. 47 ecobee NodeLink users and you're the only one this happens to. Just an FYI I had another ecobee4 set to the minimum temperature of 17C. This was soon after ecobee's website was down and NodeLink heartbeats both stopped for a few hours, yesterday again Unless you found anything in the NodeLink boot up / reconnect code, I suspect this has to do with the ecobee API sending a 0 degrees setting. OTOH I never thought to actually look at the stat itself, and it may have just been a remote app indication error. It showed "17C Hold until 3:00 AM" in the app. Unfortunately I reset it on the app before even looking at the stat, but the ecobee4 records do not show it as ever happening on the setpoint history???
io_guy Posted April 14, 2018 Posted April 14, 2018 I don't see any way NodeLink would be sending these minimum temp sets. As with last time, log it to a file. If NodeLink sends it, it can be logged.
larryllix Posted April 14, 2018 Author Posted April 14, 2018 50 minutes ago, io_guy said: I don't see any way NodeLink would be sending these minimum temp sets. As with last time, log it to a file. If NodeLink sends it, it can be logged. The only thing I can find that is a command out of NodeLink in the log is (this is one of two per day) setting the Climate Types. Since you perfected that I don't need to/ and don't use temperatures at all. I can do it all without keeping track of any temperature now by setting preset Climate Types in the stats. Much safer and simpler method! You can't remote set anything that isn't preset in the stat. 2018-04-12 20:00:28 - Web Request: /isylink/nodes/n001_ecobee1/cmd/GV3/2/25?HoldType.uom25=1 Either some random garbage is getting into the comms and the ecobee4 is interpreting it without enough security checks, or the ecobee site has sent it around the time they came back online last night. Ecobee was down again (and not accessible via webpage either) for a few hours and tonight as well. These guys are starting to scare me. Thank Gawd my ecobee4 traps out any setpoint less than 17C. My ecobee3 has never been affected like this yet AFAIK.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.