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

Current heating action for climate devices #167

Open
swappie-d opened this issue Oct 20, 2023 · 6 comments
Open

Current heating action for climate devices #167

swappie-d opened this issue Oct 20, 2023 · 6 comments

Comments

@swappie-d
Copy link

Hi all,

I noticed that the climate devices don't show their current HVAC action. Since I would like to have that in HA available I did some research and made a fork of the repo and did some changes to climate.py, fah_thermostat.py, const.py and added to test files for testing purposes. However this is my very first attempt at coding python so it's not working yet, I can't find where I forgot to add the current heating action output datapoint, so the state is correctly communicated from the SysAP to the freeathome custom component. Could someone have a look at this commit I made and help me with what I did wrong?

If I look at the monitor output I see a message from the SysAp to freeathome updating the value of the PID_HEATING_ACTIVE when using my changes.

BTW: how can I use the test py's? Maybe I can then solve it my self.

I made use of the ABB local API documentation and used that to read the correct output datapoints and pairingID's from the local api.

@guerda
Copy link

guerda commented Dec 4, 2023

I have the same issue. Interestingly, the attribute temperature returns the target temperature, but it renders correctly in the UI. I feel that this integration does not comply with https://developers.home-assistant.io/docs/core/entity/climate/

{{ state_attr('climate.touch_panel', 'temperature') }} = null

For me this happens with both a Busch Jaeger thermostat and a touch panel.

@swappie-d
Copy link
Author

swappie-d commented Apr 17, 2024

@jheling We’re you able to have a look at this issue?

@jheling
Copy link
Owner

jheling commented Apr 19, 2024

Hello, I don't have any heating devices in my system, so I hoped that another user with such a device would respond. I will try to take a look at it.

@guerda
Copy link

guerda commented Apr 20, 2024

Can we provide you with data about the heating devices?

@guerda
Copy link

guerda commented May 30, 2024

Entity None (<class 'custom_components.freeathome.climate.FreeAtHomeThermostat'>) implements HVACMode(s): heat_cool, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please report it to the author of the 'freeathome' custom integration

I just saw this in the log files: I'm having a look at this, but want to tackle the cover groups in #94 first.

@Macstar1601
Copy link

Macstar1601 commented Jun 13, 2024

I also would like to see the current HVAC action of free@home climate devices. Please let me know if I can help somehow.

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

4 participants