HA core version
2025.12.2
Intergration version
0.6.10
Device type and model
Electric Heater 570000ZF (0)
Used App
Home Assistant
The description of problem
Device Info
- Model: 570000ZF (Electric Heater)
- Device Type: FB
- Integration Version: [check your version]
- Home Assistant Version: 2025.x.x
Problem
The FB device message parser crashes with IndexError: bytearray index out of range when processing messages from this heater model.
Root Cause
The parser assumes all FB devices send 14+ byte message bodies (to read body[13]), but this model sends compact 6-byte messages.
Error Messages
[Paste your 4 error messages from the log]
Message Examples
aa12fb0000000000020404a41000070200002c (6-byte body)
aa12fb0000000000020404a51000070100002c (6-byte body)
Proposed Fix
Add length check in message.py line 157:
if len(body) >= 14:
self.current_temperature = body[13] - 20
else:
self.current_temperature = None
Additional Context
Oscillation control is available in the Midea app but not exposed in HA. Byte 4/5 of the compact message format may contain oscillation state.
The logs
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2025-12-10 14:12:55.791 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.796 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_ac_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.800 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.803 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.806 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.809 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration goveelife which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.813 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.815 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.818 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_ac_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.820 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.823 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.826 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.828 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration goveelife which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.831 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:13:13.963 ERROR (MainThread) [homeassistant.components.panel_custom] Unable to register panel Supervisor: Overwriting panel hassio
2025-12-10 14:13:38.360 ERROR (MainThread) [simplipy] Unknown device type: 21
2025-12-10 14:13:54.309 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states('input_text.dyly_book_pro_charging') | int }}) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 461, in async_render
render_result = render_with_context(self.template, compiled, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template/context.py", line 45, in render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 1570, in forgiving_int_filter
raise_no_default("int", value)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template/helpers.py", line 24, in raise_no_default
raise ValueError(
...<2 lines>...
)
ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('input_text.dyly_book_pro_charging') | int }}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 579, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 463, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('input_text.dyly_book_pro_charging') | int }}' but no default was specified
2025-12-10 14:13:54.329 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('input_text.dyly_book_pro_charging') | int }}' but no default was specified') while processing template 'Template<template=({{ states('input_text.dyly_book_pro_charging') | int }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.dyly_book_pro_battery_level'
2025-12-10 14:13:56.166 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.spotify does not support any media_player features
2025-12-10 14:13:56.305 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.spotify does not support any media_player features
2025-12-10 14:13:56.314 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_ios_iphone does not support any media_player features
2025-12-10 14:13:56.315 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_roku_roku_bae does not support any media_player features
2025-12-10 14:13:56.315 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_ios_ipad does not support any media_player features
2025-12-10 14:13:56.315 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_web_chrome_osx does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_web_chrome_osx_2 does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_roku_roku_boo does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_joshua_g57_plex_for_android_tv_aftkm does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_ios_ipad_2 does not support any media_player features
2025-12-10 14:18:39.007 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [281472441525536] Dylan ha-Bbore from 127.0.0.1 (Home Assistant/2025.11.2 (io.robbie.HomeAssistant; build:2025.1537; macOS 26.1.0)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-12-10 14:19:03.074 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a41000070200002c, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:19:09.262 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a51000070100002c, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:19:13.766 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a710000706000025, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:19:15.771 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a81000070000002a, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:20:33.005 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [281473178548032] Dylan ha-Bbore from 127.0.0.1 (Home Assistant/2025.11.2 (io.robbie.HomeAssistant; build:2025.1537; macOS 26.1.0)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
HA core version
2025.12.2
Intergration version
0.6.10
Device type and model
Electric Heater 570000ZF (0)
Used App
Home Assistant
The description of problem
Device Info
Problem
The FB device message parser crashes with
IndexError: bytearray index out of rangewhen processing messages from this heater model.Root Cause
The parser assumes all FB devices send 14+ byte message bodies (to read
body[13]), but this model sends compact 6-byte messages.Error Messages
[Paste your 4 error messages from the log]
Message Examples
aa12fb0000000000020404a41000070200002c(6-byte body)aa12fb0000000000020404a51000070100002c(6-byte body)Proposed Fix
Add length check in
message.pyline 157:Additional Context
Oscillation control is available in the Midea app but not exposed in HA. Byte 4/5 of the compact message format may contain oscillation state.
The logs
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2025-12-10 14:12:55.791 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.796 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_ac_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.800 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.803 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.806 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.809 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration goveelife which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.813 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.815 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.818 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_ac_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.820 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.823 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.826 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.828 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration goveelife which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:12:55.831 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-10 14:13:13.963 ERROR (MainThread) [homeassistant.components.panel_custom] Unable to register panel Supervisor: Overwriting panel hassio
2025-12-10 14:13:38.360 ERROR (MainThread) [simplipy] Unknown device type: 21
2025-12-10 14:13:54.309 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states('input_text.dyly_book_pro_charging') | int }}) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 461, in async_render
render_result = render_with_context(self.template, compiled, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template/context.py", line 45, in render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 1570, in forgiving_int_filter
raise_no_default("int", value)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template/helpers.py", line 24, in raise_no_default
raise ValueError(
...<2 lines>...
)
ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('input_text.dyly_book_pro_charging') | int }}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 579, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 463, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('input_text.dyly_book_pro_charging') | int }}' but no default was specified
2025-12-10 14:13:54.329 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('input_text.dyly_book_pro_charging') | int }}' but no default was specified') while processing template 'Template<template=({{ states('input_text.dyly_book_pro_charging') | int }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.dyly_book_pro_battery_level'
2025-12-10 14:13:56.166 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.spotify does not support any media_player features
2025-12-10 14:13:56.305 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.spotify does not support any media_player features
2025-12-10 14:13:56.314 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_ios_iphone does not support any media_player features
2025-12-10 14:13:56.315 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_roku_roku_bae does not support any media_player features
2025-12-10 14:13:56.315 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_ios_ipad does not support any media_player features
2025-12-10 14:13:56.315 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_web_chrome_osx does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_web_chrome_osx_2 does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_roku_roku_boo does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_joshua_g57_plex_for_android_tv_aftkm does not support any media_player features
2025-12-10 14:13:56.316 ERROR (MainThread) [homeassistant.components.homekit.util] media_player.plex_plex_for_ios_ipad_2 does not support any media_player features
2025-12-10 14:18:39.007 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [281472441525536] Dylan ha-Bbore from 127.0.0.1 (Home Assistant/2025.11.2 (io.robbie.HomeAssistant; build:2025.1537; macOS 26.1.0)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-12-10 14:19:03.074 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a41000070200002c, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:19:09.262 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a51000070100002c, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:19:13.766 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a710000706000025, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:19:15.771 ERROR (Space Heater) [midealocal.device] [151732605888844] Error in process message aa12fb0000000000020404a81000070000002a, model 570000ZF, subtype 0, device protocol 3, message procol 2
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/midealocal/device.py", line 491, in parse_message
status = self.process_message(bytes(decrypted))
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/init.py", line 87, in process_message
message = MessageFBResponse(msg)
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 175, in init
self.set_body(FBGeneralMessageBody(super().body))
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/midealocal/devices/fb/message.py", line 157, in init
self.current_temperature = body[13] - 20
~~~~^^^^
IndexError: bytearray index out of range
2025-12-10 14:20:33.005 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [281473178548032] Dylan ha-Bbore from 127.0.0.1 (Home Assistant/2025.11.2 (io.robbie.HomeAssistant; build:2025.1537; macOS 26.1.0)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds