Skip to content
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

[BUG] Cannot activate Faikin Auto Mode using MQTT publish #506

Open
Taxxian opened this issue Sep 28, 2024 · 4 comments
Open

[BUG] Cannot activate Faikin Auto Mode using MQTT publish #506

Taxxian opened this issue Sep 28, 2024 · 4 comments
Assignees

Comments

@Taxxian
Copy link

Taxxian commented Sep 28, 2024

Faikin hardware
Amazon

Daikin hardware
4 different Stylish Wall Device with S21

Describe the bug
Is sent various MQTT commands like:

command/FaikinWozi/control
{
"env": 23.0,
"target": [22.0,23.0]
}

command/FaikinWozi/control
{
"target": 24.0,
"env": 21.0
}

It is received and I can see the new "env" value in MQTT status.

But "target" never changes and "control" is always false.

I can activate Faikin Auto Mode and set "target" in the Web UI and I can then see this data in the MQTT status, but if I do it using MQTT publish "target" values never change and FAM never avtivates.

Expected behavior
I shoud see the new "target" values in the WEB UI and MQTT status, FAM Mode should activate.

Additional context
Everything I tested works fine, I updated to the new Faikin version and it still works fine, except for the "target" command. (Dont know if it worked before the update, own it for 3 days...)

Edit:
I tried while the device was on or off, already heating or not and already in FAM or not. Nothing made a difference, targettt values got ignored.

Thanks for the help!

Regards

Martin

@revk
Copy link
Owner

revk commented Sep 29, 2024

OK, this is exactly how I use it, and it works for me, honest.

e.g. I regularly send

command/OfficeAC/control {"env":21.50,"target":[21.000,21.500]}

And the Faikin/OfficeAC message includes "control":true

You need two send control regularly. The "Faikin auto mode" on the web interface should disappear, e.g.

Screenshot 2024-09-29 at 10 01 54

I'm running latest beta.

@Taxxian
Copy link
Author

Taxxian commented Oct 2, 2024

Interesting I think I got it to work so far.

I can set the desired temp in the exposed climate entity in HA that directly translates to "target".
Then I had to activate lock mode to prevent the Faikin from going to cooling mode when night comes and the thermostat goes to 18Deg.

What does "update regularly" mean? Dont know if setting env alone keeps FAM running longterm,

Other stuff:
The climate entity shows heat/cool which is suboptimal, how can I see if its heating or not? I have to manually switch from heat to cool or back 2 times annually the way it is set up, and I have no solution for that.

Those icóns are incomprehensible, text should be standard.

Is there a way to influence the compressor frequency of the outdoor unit? I have a certain range where my roof vibrates, I want to skip that...

Overall: I like it! :-)

@revk
Copy link
Owner

revk commented Oct 2, 2024

Arg, ok I think send like every minute or so.

Not sure easy to change the heat/cool state. People want to know it is auto. But I guess it "locked" it may be something that ca be fixed.

You can set text not icons right?

And finally if you have it, demand control may be what you need to control it.

@Taxxian
Copy link
Author

Taxxian commented Nov 21, 2024

Update:
My workaround is doing fine for over a month now, so I dont consider this a problem anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants