Open mtfurlan opened 6 years ago
Fan state does not report correctly. Requested fan state appears to mirror active fan state.
Mqtt reset/run command. Mqtt set reset interval
Delay fan turn on a few seconds.
publish a status (like "../thermostat/timeout true") when the inactivity timeout has been reached and thermostat is resetting to default values.
Done:
Todo
Sorted todo
mqtt
/button
/timeout
Delay fan by 30s done. Kevin is now responsible for the tests, but it seems to work.
Autodetect BME vs BMP 280 Detect if temperature sensor unplugged while running
Changing swing changes mode to heat (observed when thermostat was set to cool and was actively cooling)
Further unexpected behavior, and I can't find anywhere in the code where swing should affect what mode it's in.
2018-08-20 23:13:55.914 cmnd/i3/inside/office/thermostat/swing 4 2018-08-20 23:13:55.959 stat/i3/inside/office/thermostat/mode heat 2018-08-20 23:13:55.962 tele/i3/inside/office/thermostat/output {"state": "off", "fan": "off"} 2018-08-20 23:13:57.520 cmnd/i3/inside/office/thermostat/swing 4 2018-08-20 23:13:57.569 stat/i3/inside/office/thermostat/mode heat 2018-08-20 23:14:50.730 cmnd/i3/inside/office/thermostat/swing butts 2018-08-20 23:14:50.808 stat/i3/inside/office/thermostat/swing 0 2018-08-20 23:15:06.715 cmnd/i3/inside/office/thermostat/swing 1 2018-08-20 23:15:06.748 stat/i3/inside/office/thermostat/mode heat 2018-08-20 23:15:21.364 cmnd/i3/inside/office/thermostat/swing 10 2018-08-20 23:15:21.391 stat/i3/inside/office/thermostat/swing new swing out of range 0-3 2018-08-20 23:15:24.703 cmnd/i3/inside/office/thermostat/swing 5 2018-08-20 23:15:24.790 stat/i3/inside/office/thermostat/mode heat 2018-08-20 23:15:24.794 tele/i3/inside/office/thermostat/output {"state": "off", "fan": "off"} 2018-08-20 23:15:27.125 tele/i3/inside/office/thermostat/input {"target":20, "mode":"heat", "fan":"auto", "swing":0, "timeout":10800000}
Issue with swing is known, fix is implemented. Unresolved issue: Swing can take letters and thinks it gets 0 and this is bad.
Swing should also probably never be allowed to be 0 lest we end up switching HVAC 100 times a day.
Swing issue fixed; String parsing issues fixed Delay fan thing done Timeout set from MQTT, but not set in eeprom
New todo
Something is wrong with the eeprom, not persisting properly? Maybe it's being reset every boot?
Newerest todo
3 hours after changing mode from 'AC' to 'off' the target changes from its current value to 10. This time delay seems not very intuitive. Should we even display a target when mode is 'off'?
Probably not. Maybe a countdown to time out?
On Sun, Sep 9, 2018, 19:39 mkfink notifications@github.com wrote:
3 hours after changing mode from 'AC' to 'off' the target changes from its current value to 10. This time delay seems not very intuitive. Should we even display a target when mode is 'off'?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/i3detroit/custom-mqtt-programs/issues/64#issuecomment-419753541, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJyGrw9p-VlMgNuqGAVV86AJRsEJfiAks5uZaaXgaJpZM4U1N2j .
Timeout should be irrelevant in off mode. Just checked my home thermostat and just stops displaying target when set to off. It also remembers the last set heat and cool targets when I switch back to those from off, and I think I'd want that kind of behavior on this thermostat if I were using it at home with timeout disabled.
Makes sense.
Todo
On Sun, Sep 9, 2018, 19:45 mkfink notifications@github.com wrote:
Timeout should be irrelevant in off mode. Just checked my home thermostat and just stops displaying target when set to off. It also remembers the last set heat and cool targets when I switch back to those from off, and I think I'd want that kind of behavior on this thermostat if I were using it at home with timeout disabled.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/i3detroit/custom-mqtt-programs/issues/64#issuecomment-419753889, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJyGvm9whDHmL9WQoiVNLBtWfRVomlJks5uZagigaJpZM4U1N2j .
Add a command to query the current state of all inputs/outputs/sensors
Added query command
Set temp with remote command Detect BME unplugged
Make it so you can't turn on heat/cool more than once every two minutes or something.
Current state of publishing topics:
tele/.../sensors {"temperature":19.85, "pressure":98621.7, "humidity":42.0}
tele/.../output {"state": "off", "fan": "on"}
tele/.../input {"target":19, "mode":"heat", "fan":"on", "swing":1, "timeout":0}
stat/.../mode HEAT
stat/.../target 19
stat/.../fan on
Command topics:
cmnd/.../mode
cmnd/.../target
cmnd/.../fan
cmnd/.../query
tele/.../input
being tele confused me.
Is this "correct"?
Also, todo list as I currently read it:
Todo items that need research into what we meant two years ago:
Redraw screen on connection Something with fan forced sticking on