-
Notifications
You must be signed in to change notification settings - Fork 41
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
Comments
I have the same issue. Interestingly, the attribute
For me this happens with both a Busch Jaeger thermostat and a touch panel. |
@jheling We’re you able to have a look at this issue? |
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. |
Can we provide you with data about the heating devices? |
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. |
I also would like to see the current HVAC action of free@home climate devices. Please let me know if I can help somehow. |
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.
The text was updated successfully, but these errors were encountered: