You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I shutdown the printer (the power plug is automated to switch OFF 15 min after a print [except if a print is started in this delay], it's enough to let extruder cool down), I've noticed the Bed Temperature sensor value remains at the very last recorded value. It is not set to null (or whatever "no value" is). The MCU is not reachable anyway.
Version of the moonraker integration
I'm runing moonraker-home-assistant integration v 0.10.0
27,12°C is definitely not the temperature of my room. It's the very last "true" temperature of the bed before the MCU is disconnected and no sensor value can be retrieved.
Those values (some values / all values ??) should be reset to "none" / "null" values instead of their last valid value.
Thanks
When I shutdown the printer (the power plug is automated to switch OFF 15 min after a print [except if a print is started in this delay], it's enough to let extruder cool down), I've noticed the Bed Temperature sensor value remains at the very last recorded value. It is not set to null (or whatever "no value" is). The MCU is not reachable anyway.
Version of the moonraker integration
I'm runing moonraker-home-assistant integration v 0.10.0
Describe your setup
Klipper, Moonraker, Mainsail, on Rpi
Describe the bug
See top of bug report
Moonraker Logs
home-assistant_moonraker_2023-09-19T10-36-41.342Z.log
The text was updated successfully, but these errors were encountered: