brutella / hkknx-public

hkknx is a HomeKit KNX bridge for KNX.
https://hochgatterer.me/hkknx
97 stars 6 forks source link

FAN in KNX has value from 0 to 255 dec, but hkknx only has value from 0 to 100 available. #91

Closed hahasagined closed 3 years ago

hahasagined commented 3 years ago

Hello, I am using a fan that where I have to write values from 0 to 255 - hkknx only gives me 0 to 100, so the fan never goes to 100% (=255). Is there something that I can configure here or is that a missing feature? Thank you!

brutella commented 3 years ago

I've added the option in the latest pre-release build for version 1.3.0. Please download it again.

hahasagined commented 3 years ago

Thank you for the fast response @brutella I downloaded the latest version form github (hkknx-1.3.0_linux_amd64.tar.gz) and started it and can't find the option, what am I doing wrong?

this is what I downloaded: wget https://github.com/brutella/hkknx-public/releases/download/1.3.0/hkknx-1.3.0_linux_amd64.tar.gz

Bildschirmfoto 2021-04-26 um 09 24 02

brutella commented 3 years ago

Did you download it just now? I've uploaded a new build just some minutes ago.

hahasagined commented 3 years ago

works like a charm, thank you :) just bought the license, your product and your quick responses are appreciated.

hahasagined commented 3 years ago

ok - something that I have seen, maybe that is a bug or expected by design: the Fan is not showing any data, until I have manually changed the value via HomeKit or ETS. it seems like HomeKit does not "read" the initial value of the fan when the server is starting.

When I start HK-KNX, I see in the verbose logs: DEBUG 2021/04/26 17:54:25 io.go:12: read: 3/0/14 but, still the current value is not seen.

Is that expected?

chef76 commented 3 years ago

You have to set the read-flag on your actuator for the value that sends to your group adress 3/0/14. Without the flag, the actuator does not respond to the initial read-request. You should see a timeout in the logs.

hahasagined commented 3 years ago

thank you for your response. Here is the screenshot of my fan device: image

If I go to ETS and do a "read" for that group address, I see that I get a response with the current value: image

so from the KNX side it is working as expected, not sure if there is a way to debug this on HK-KNX.

chef76 commented 3 years ago

There shouldn't be wrong data-type in HKKNX. What data-type is set in ETS for your group adresses?

hahasagined commented 3 years ago

both are 5.0001 Percent: image

In the Group Address Page, the type seems to be right? image

brutella commented 3 years ago

Ok, then you would need the datatype DPST-5-1 (5.001) instead of DPST-5-10 (5.010). I can add that.

hahasagined commented 3 years ago

that would be great, I missed the detail about DPST-5-1 and DPST-5-10. Thanks!

brutella commented 3 years ago

The datatype DPST-5-1 is now available.

hahasagined commented 3 years ago

Now the error in the GUI is gone: image

But still, if I open the Home App or restart HKKNX I don't see that the fan is online. From what I can see, if the HKKNX is starting, it is reading all initializing GAs, that is working and I see a reply from KNX in the KNX Bus: image

Still in the Home App, the fan is off - even though it is on 75%. image

should I open another issue for that?

brutella commented 3 years ago

Hab den Fehler beim Initialisieren entdeckt. Bitte nochmals updaten. 😄

hahasagined commented 3 years ago

😍 image