-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird Daikin AC #47
Comments
Should fix issue hristo-atanasov#47, set daikin_toggle: true in config
Fixed with #52. |
Hi @angsanley , sorry to bump an old topic. I'm facing an issue where the integration and the remote goes out of sync often, ie, after turning off mains, and later turning back on with the remote, the state becomes inverted. ie, when turned on via HASS, it turns off, when turned off via HASS, it turns on. Thanks! |
Hey, sorry for late reply. I haven't played with Home Assistant for a while now so I don't know any new updates regarding this anymore. But the last time I tried this it was already fixed with #52 maybe that helps. |
Hi, Thanks for replying! I've checked out #52, don't see any mention of this being resolved sadly :( |
Hello,
I have a Daikin AC that is working fine with Tasmota and IrHvac except that there's a weird quirk with this kind of Daikin AC. I'm using DAIKIN64.
So this AC doesn't have a separate on and off command. Instead, the AC handles the toggle itself, the remote only sends "On" command to toggle the power state.
If we send
{"IRHVAC":{"Vendor":"DAIKIN64","Model":-1,"Power":"Off"}
while the AC is on or off, it will beep and do nothing.
But, if we send
{"IRHVAC":{"Vendor":"DAIKIN64","Model":-1,"Power":"On"}
while the AC is off, it will turn on.
And also vice versa, if we send
{"IRHVAC":{"Vendor":"DAIKIN64","Model":-1,"Power":"On"}
while the AC is on, it will turn off.
So, is there's any possibility to change the toggling behavior to only send the
Power
command if we want to change the power state?I think the
Power
command here is not to set the power state, but to toggle it.Thank you!
The text was updated successfully, but these errors were encountered: