Issues with 4,3 Zoll RTR - Change of Temperature not possible / Current Temperature not shown

[floriangrotz]

Problem witht the Support of the 4,3 Display RTR

Changing Temperature:

[29/12/2022, 12:54:14] [My free@home Setup] Office RTR (Room Temperature Controller ABB700DB6452 (ch0010)) set characteristic TargetTemperature -> 20 [29/12/2022, 12:54:14] [My free@home Setup] Received HTTP 403 status code unexpectedly: [29/12/2022, 12:54:14] [homebridge-freeathome-local-api] This plugin threw an error from the characteristic 'Target Temperature': Unhandled error thrown inside write handler for characteristic: Received HTTP 403 status code unexpectedly: . See https://homebridge.io/w/JtMGR for more info.

Current Temperature are not shown see attachment

Happy to help to make it work

Environment:

• Plugin Version: 1.4.1
• Homebridge Version: 1.60
• Node.js Version:
• NPM Version:
• Operating System: Rasp

[floriangrotz]

[floriangrotz]

The first three are from an RT with a 4,3 Zoll Display

The next three from a regular RT with small LCD Display

[pgerke]

Ok, it seems like B+J is using other data points to provide the temperature values in the 4.3" panel with the integrated RTR while re-using the functionID from the "normal" RTR. Interesting design choice... Could you please provide a device config JSON for the 4.3" panel with the RTR so I can get an overview of the functionIDs, datapoints and pairingIDs they are using. Please refer to https://github.com/pgerke/homebridge-freeathome-local-api/wiki/Retrieving-the-Configuration-for-a-device-from-the-System-Access-Point to learn how you can retrieve a device configuration from your System Access Point.

[floriangrotz]

Attached the Json response_1672411870395.json.txt

[pgerke]

Thanks for providing the config. This confirms what I feared... B+J is using other data points to provide characteristice in the 4.3" RTR compared to the "regular" room temperature controllers but they're using the same function ID...

[floriangrotz]

So, a hope for a fix? :)

[pgerke]

There's always hope 😉 But I'd like to consider a few options (e.g. add resilience, pairing ID look-up, ...) before I decide on how to proceed here.

[pgerke]

Fixed with v1.4.4.

[floriangrotz]

Works like a charm ❤️

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.