-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Describe the bug
I have a K Safe+ (device type 0x67, version 0x6f0104) that does not seem to get recognized correctly (shows as device type 255 in HA).
The integration sends a request to /api/rest/FB00 which reproducibly crashes/reboots the module.
The API documentation defines an endpoint with FB00 + 4 more bytes for the date (Tagesstatistik) but doesn't have an endpoint without those 4 additional bytes. It's "not great" that the module doesn't handle this gracefully but is there anything I can do to prevent this request? Is this different in other firmware versions or an issue with the integration missing the date bytes?
From a TCP trace of an update run:
GET /api/rest/FF00 HTTP/1.1
{"data": "67"}
GET /api/rest/0100 HTTP/1.1
{"data": "6f0104"}
...
GET /api/rest/FB00 HTTP/1.1
- no response, module crashes and reboots
From my documentation: "/api/rest/FB000D0807E7 - Tagesdaten vom 13.08.2023"
Metadata
Metadata
Assignees
Labels
No labels