-
Notifications
You must be signed in to change notification settings - Fork 75
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] #565
Comments
If you know it is definitely S21 you can set nox50a, and the settings kit to invert tx and rx. That will simplify the logs at least, as it tries many combinations. It may then be worth power cycling the whole lot (air con too). Then get some more logs from MQTT. |
wow. played with the protocol settings and it connected. it shows Faikin-S3-MINI-N4-R2: ebf3c2b 2024-09-26T14:35:29 Altherma_S so its no s21 or Nox50a?? Now, its connected but i can’t turn the unit on via the web if i have MQTT connected? |
I don't think Atherma allows control, just reporting of settings. I'll have another look, but it is not S21 protocol. |
With debug on i don’t see anything come in. Message 344 received on info/FaikinBroom/rx at 5:54 PM: Is there anything specific I should enable to derive the info needed? |
This state info is presented at the start of listening Message 354 received on homeassistant/climate/F0F5BD74290C/config at 5:58 PM: Message 353 received on state/FaikinBroom/status at 5:58 PM: Message 352 received on state/FaikinBroom at 5:58 PM: |
I am not sure how far Altherma development got, I thought we had basic state info. Select latest beta, if you have not already. |
Ok will try the beta. |
I upgraded to the beta version and tried to send an “on command” to the system (so hard to work out how to do this, could you please put examples in the manual for people to reference and make the link for the command easy to identify the options you can use) So I sent the following to,power on the unit: command/FaikinBroom/on This is the error: Message 86 received on Faikin/FaikinBroom at 8:48 PM: $$$$$$$$$$$$ then I tried to send a command with json format, I am not sure this is right how I formatted it, but got the following Message 171 received on error/FaikinBroom/command at 9:00 PM: |
Yeh I don't think the interface for Atherma has a means to send any controls. |
I just want power on. Shame |
I know there are some other people who have been working on this, but I think we concluded there is no "control" in the protocol even. If someone works it out I'll add to the code. |
@revk FYI I've had a batch manufactured and am distributing them in Australia. This is one of mine. @seafurymike send it back and I'll pass it on to someone else. Pls add your model to the wiki and indicate it's not compatible. https://github.com/revk/ESP32-Faikin/wiki/List-of-confirmed-working-air-con-units |
Faikin hardware
Purchased locally from UK stock
Daikin hardware
Connected via X35 and X50
Model FFQ35BV1B
Describe the bug
Unit will not come online. Checked wiring diagram and confirmed connectivity is correct from this link
https://github.com/revk/ESP32-Faikin/wiki/Wiring
**unit led is flashing magenta, as well as webpage showing offline. Have never managed to get unit online
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
ERROR OUTPUT FROM MQTT STREAM BELOW
. Message 53 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"S21","cmd":"F1","noack":true,"value":"FE"}
QoS: 0 - Retain: false
Message 52 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A¬Tx¬Rx","badsum":"7A","data":"7505"}
QoS: 0 - Retain: false
Message 51 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A¬Rx","badsum":"7A","data":"7505"}
QoS: 0 - Retain: false
Message 50 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A¬Tx","badsum":"FE","data":"15EA15EA"}
QoS: 0 - Retain: false
Message 49 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A","badhead":true,"mismatch":true,"badrxlen":true,"data":"15EA"}
QoS: 0 - Retain: false
Message 48 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"S21¬Tx¬Rx","cmd":"F1","noack":true,"value":"01"}
QoS: 0 - Retain: false
Message 47 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"S21¬Rx","cmd":"F1","noack":true,"value":"01"}
QoS: 0 - Retain: false
Message 46 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"S21¬Tx","cmd":"F1","noack":true,"value":"FF"}
QoS: 0 - Retain: false
Message 45 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"S21","cmd":"F1","noack":true,"value":"F8"}
QoS: 0 - Retain: false
Message 44 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A¬Tx¬Rx","badsum":"F4","data":"75057505"}
QoS: 0 - Retain: false
Message 43 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A¬Rx","badsum":"7A","data":"7505"}
QoS: 0 - Retain: false
Message 42 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A¬Tx","badsum":"FE","data":"15EA15EA"}
QoS: 0 - Retain: false
Message 41 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"X50A","badhead":true,"mismatch":true,"badrxlen":true,"data":"15EA"}
QoS: 0 - Retain: false
Message 40 received on error/FaikinBroom/comms at 3:05 PM:
{"protocol":"S21¬Tx¬Rx","cmd":"F1","noack":true,"value":"01"}
QoS: 0 - Retain: false
The text was updated successfully, but these errors were encountered: