-
Notifications
You must be signed in to change notification settings - Fork 21
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
Implementing HmIP-BWTH and HmIP-STHO-A #19
Comments
I will look into it. It probably takes a couple of days... |
sounds great, thank you for your help |
Have a look at version >=0.0.19. It's completely untested so please test and let me know if something isn't working right. |
Just updated to 0.0.20 and it seems that everything's working great (correct temperature, immediate reaction of a homekit temperature change in homematic). |
Yes, unfortunately the Home-App displays temperatures with a resolution of 0.5 degrees. That's probably because 0.5 degrees is more than enough when used with Fahrenheit in the US. All I can say is that homebridge-homematicip transmits the full resolution to HomeKit. I believe the Eve-App shows a higher resolution. |
Hey, I noticed a problem with the outside temperature below 0° Celsius. In that case the HmIP-STHO-A temperature is shown as "no response", air humidity is still working. |
This is a weird HomeKit "bug" where the minimum temperature of the current temperature is 0 degrees Celsius. I hopefully fixed it in 0.1.1. |
Wow, that was fast :) Yes, it's fixed now. Thank you! |
Just noticed that there is also a minus in front of the "0,0", when there is an outside temperature in the Homematic App of "-0,1". |
I don't quite understand. HomematicIP-App shows "-0,1" and the Home App shows "-0,0"? |
Yes, Home App shows "-0,0", but this should be "0,0". Beginning with "-0,5" and lower the minus is correct. |
it would be great if you could implement HmIP-BWTH and HmIP-STHO-A in the homebridge-homematicip plugin for hoobs.
https://github.com/coreGreenberet/homematicip-rest-api/issues/114#issuecomment-767381606
The text was updated successfully, but these errors were encountered: