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

Issues with xx.5 degrees set on the AC #11

Open
sindudas opened this issue May 24, 2023 · 1 comment
Open

Issues with xx.5 degrees set on the AC #11

sindudas opened this issue May 24, 2023 · 1 comment

Comments

@sindudas
Copy link

Installed 3 ESP32 with mel-ac-demo. Got 1 of them since 1 week unreachable. In the absence of time and because it is on the roof, I tried several times to restart it (turn off power and turn it on again) without success.
Now I have connected the serial port and observed what happened. It was crush dump all time. I have changed with a new ESP32, but the same result (when paring it with homekit).
I have finally figured out the problem. The AC thermostat was at 23.5ºC. When I have changed it to 23.0ºC it has started to work correctly. And when I have changed to 23.5ºC again, the ESP32 has crashed
I think it doesn't manage correctly half degrees
Here is the serial log dumped just before the crush started

HAPPlatformLog.c:55 Characteristic [0000000000000001 MEL-9E78] [0000000000000135 temperature.target] Value out of range: 23.5 (constraints: minimumValue = 16 / maximumValue = 31 / stepValue = 1). HAPPlatformLog.c:55 HAP assertion failed - HAPFloatCharacteristicHandleRead @ /data/fwbuild-volumes/2.20.0/apps/mel-ac-homekit/esp32/build_contexts/build_ctx_038970181/deps/homekit-adk/HomeKitADK/HAP/HAPCharacteristic.c:1333

abort() was called at PC 0x40112c56 on core 1

Backtrace:0x40087df2 0x40088481 0x4008ecae 0x40112c56 0x4010e50c 0x40107707 0x4011c9f5 0x4012084a 0x401164f0 0x40120010 0x40120571 0x4011323d 0x4018e609 0x4018fc51 0x40192445 0x40199f69 0x4018a1f5 0x400829bd 0x400828c5

@d4rkmen
Copy link

d4rkmen commented May 24, 2023

Hi, its not an issue but it's a feature😎
The 'stepValue' is set to 1.0 so validation for 23.5 fails in setter

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

2 participants