Some o0 and s0 sensors show unknown

[majdzik84]

Integration does not read all parameters.
Parameters:
o01 , o02 , o03 , o04 oraz s01, s02, s03, s04, s05, s06 are presented as unknown even though the values appear in the application.
These sensors are so important that they provide vital information about whether the compressor or fan is working.

Thank you for your efforts in integration.

config_entry-aqua_temp-01K22VDEKSBFGZG0V4NE23HGX7.json

[spanznet]

I have a similar issue, the API response has all numerical values ok, but all non-numerical values have no data at all in the response and is therefore 'unknown' in HA.

eg numerical value correct response
{'code': 'D04', 'value': '8.0', 'dataType': None, 'rangeStart': '1', 'rangeEnd': '20', 'tmJson': None}

eg non-numerical value empty response
{'code': 'O01', 'value': '', 'dataType': '', 'rangeStart': '', 'rangeEnd': '', 'tmJson': ''}

[spanznet]

Just updating above with new findings, the API doesn't have the following keys:

O01, O02, O03, O04, O05, O06 and S01, S03, S04, S05, S06

So they will always return unknown in the integration's current form, so you may as well delete them from your entity mapping file.

For my HiTemp device, EvoHeat270, I believe the binary values for O01-O06 are stored in a key called 2050.

eg when compressor and fan are off:
{"code":"2050","value":"0000000000110000","dataType":null,"rangeStart":"","rangeEnd":"","tmJson":null},

eg when compressor and fan are on (bits 5 to 10 are O01-O06):
{"code":"2050","value":"0000100100110000","dataType":null,"rangeStart":"","rangeEnd":"","tmJson":null},

The S keys are probably the same, but I just deleted those from entity mapping too