Samuel Prashker

Realistically, a feature like this doesn't really work with such a rate limit on Discord side.

Put in a pull request for this - compiled a local BIN to test, and validated as working on my PVA (@0.5 Celsius increments)

Seems this is a common problem, just adding my experience to it. I found configuring using the thermostat control itself to be too annoying, so I setup my schedule via...

@danielgoepp Feel free to send what you can, I'm stuck between fixing it properly or - like you - doing whatever to make the wife happy! From the perspective of...

SwiCago's codebase seems to work in this manner - when you set something, it "queues" it by making it the "wanted settings" and either explicitly by end user, you call...

Agreed with above assessment, I think this is an issue with the upstream "externalUpdates" handling. It doesn't confirm if wanted settings were actually applied before assuming the settings coming from...

Agreed it's not a generalized solution. I will recompile my local instance without external updates and test as much as I can there. What we really need, is a way...

I recompiled Mitsubishi2MQTT without `hp.enableExternalUpdate()` and seems to be fairly reliable experience if controlled solely via automation. Obviously you lose out on external updates which is probably unacceptable for most...

Just an update after having Mitsubishi2MQTT+HeatPump (with my grace period fix attempt). I haven't had any "did my setting apply" anxiety - been consistently working 👍

@skooj Thanks for the feedback, I also submitted a PR upstream as it seems stable enough for everyone that has been using it so far. Regarding remote_temp still having a...