-
Notifications
You must be signed in to change notification settings - Fork 62
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
Read vertical swing mode via REST api? #109
Comments
I don't really use the web server so I can't tell you for certain but I don't set anything to determine what gets exposed to the web interface. If it's missing it might be an esphome limitation. |
Hi and thanks for your reply. I may have figured out another way. I will post the solution here when finished. For now I have the following problem, in the yaml file I have another component that gives me e.g. the new vertical swing mode to set. str::string newVertSwingMode = data.substr(15).c_str(); my_climate is the same Panasonic ac component as in your example yaml, just with an added ID. |
The vertical swing is a select element in ESPHome (select::Select). The The value itself is set here:
|
I see, thanks! |
void PanasonicAC::update_swing_vertical(const std::string &swing) { |
I can now read all parameters and set most of them. Setting (writing) the vertical swing mode is still giving me some trouble though, could you give me any pointers on how to do this with a lambda function in the YAML? I can set the vertical swing mode to auto like this: However the different vertical swing modes (up/center/down etc) are not configurable using the set_swing_mode function. So what is the proper way to do this? |
Hi, I activated the esphome web server by adding this line to my yaml:
web_server:
port: 80
I can now request the status via (http://panasonic-ac.local/climate/panasonic_ac
However the vertical swing state (swing/auto/down/down-center/center/up center/up) is missing.
How can I add this? In web_server.cpp I can (apparently?) only add supported traits to the json. Any way around this?
The text was updated successfully, but these errors were encountered: