larryllix Posted September 2, 2016 Posted September 2, 2016 Whatever HTML fix you did sure cleaned out the 8-10 random comm. failures per day, I was having. I had the usual 4-5 errors with hardwired Ethernet ISY, at whole house query time = 4:00 AM ....gone. Failures with my WiFi furthest basement T7900, maybe 2-3 per day....gone. Occasional failures with a same room T7900...gone Nice job and thank you again! I have only had one "deserialization error" since v0.5.13 was released/installed. I actually had to observe the heartbeat of each device to know NodeLink was still functioning. LOL
larryllix Posted September 4, 2016 Author Posted September 4, 2016 io_guy With the T7900 humidity mix up, the latest v0.5.13 correction has made things worse for NodeLink on my ISY with both my T7900s. I get the current sensor humidity displayed on both the Humidity, and the Humidity setpoint boxes in the Admin Console now. The Humidity_Setpoint value has been lost from v0.5.12 and not available at all now My ISY programs stopped working with the missing hum-setpoint Further there is no admin console box for "dehumidify Setpoint" despite being sent from the T7900, depite being misalligned from the nomenclatures. I understand there is Venstar screw-up on this stat as well as difference between stat models. Can this be corrected to compensate for Venstar's mess until it gets straightened out by Venstar? It sure would be nice to have the three values. Humidity, Hum_setpoint, and deHumidify_setpoint! Thanks for your hard work on this and everything else. This is the response I get back from the T7900 with "http:x.y.z.zz/query/info" --------------------------------------------- {"name":"MAIN 0.000000LOOR", "mode":2, "state":2, "fan":0, "fanstate":1, "tempunits":1, "schedule":1, "schedulepart":1, "away":0, "spacetemp":24.0, "heattemp":23.0, "cooltemp":23.5, "cooltempmin":1.5, "cooltempmax":37.0, "heattempmin":1.50, "heattempmax":37.0, "hum":0, ←-???? "hum_setpoint":51, ←--this is the actual humidity sensor output “hum” "dehum_setpoint":38, ←-this is the actual stat humidity setpoint “hum_setpoint” "hum_active":41, ←-this is the actual stat dehumidify setpoint “dehum_setpoint” "setpointdelta":2.0, "availablemodes":0} ------------------------------------------------------
io_guy Posted September 4, 2016 Posted September 4, 2016 There's no way around the bug. 0.5.13 just sends what Venstar says the hum setpoint is, previous versions sent nothing (unless the auto-humidity was enabled). You've set what you think this decodes as, my 7900 behaves differently (I don't dehumidify). I can't make a fix to work for everyone, Venstar needs to step up to the plate. I can add dehum setpoint as a variable, but I'm not playing cards with them to Band-Aid Venstar's mistake.
larryllix Posted September 5, 2016 Author Posted September 5, 2016 I guess I have my auto turned on, even though I do not use humidity from the stat contacts, as versions previous to v0.5.13 sent the Humidity setpoint and I am/was using it in programs. Now it is broken and substitutes the sensor humidity for the parameter. Adding the dehumidify setpoint as read only would definitely help. I don't expect to control it from ISY or the humdity setpoint. I only use them as read only from the stats to control external humidify/dehumidify equipment.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.