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

4.3" Panel room temperature controller crashes #46

Open
smove50000 opened this issue Jan 31, 2021 · 4 comments
Open

4.3" Panel room temperature controller crashes #46

smove50000 opened this issue Jan 31, 2021 · 4 comments

Comments

@smove50000
Copy link

Hello.
First i have to say: GREAT WORK! And thanks for your work.

I just setup up everything in Homebridge / Homekit and so far everything seems ok.
But i recognized, the internal room temperature controller of the 4.3" Display didnt sent valid data to Homekit.
Shows only Zero degree.
So i tried to press the icon and check if i can change the temperature in Homekit. After doing this, the Display switches immediatly to "broken" in the Free@Home GUI.
To get it back to work you have to do a factory reset within the Display.

It is reproducable. ( checked it twice)
homebridge-freeathome v2.0.3
Homebridge: v1.1.7
Node.js Version | v14.15.4
Npm Version | v6.14.11

@floriangrotz
Copy link

I see an issue as attached

8.3.2021, 10:42:21 [HOOBS 4EC7@Office RTR@@target Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 7
8.3.2021, 10:42:21 [HOOBS 4EC7@Bathroom RTR@@target Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 7
8.3.2021, 10:42:21 [HOOBS 4EC7@Bedroom RTR@@target Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 7

@henry-spanka
Copy link
Owner

Please enable the debug mode of homebridge and control the panel manually (touch or System Access Point) and send me the logs.

@henry-spanka
Copy link
Owner

I guess the plugin reads the wrong input/output due to the panel having different datapoints.
I will try to fix it soon when we switch to the local API.

@floriangrotz
Copy link

Many thx!

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

3 participants