core: Incorrect readings goveelife thermometers

The problem

I bought multiple Govee H5104 devices and both ran overnight. At some point they started to randomly report the exact temperatures of 13.1C(55.58F?) and 26.2C(79.16F?) in the Home Assistant Govee integration every now and than.

I have checked the Govee app and the history there shows the correct temperature, a stead ~20*C all night.

I’m not sure where the 13.1C and 26.2C comes from. I tried to enable debug logging, but whenever one of these temperatures got recorded, there is nothing in the logs.

See images: Govee_integration Comp_app Slaapkamer_app

What version of Home Assistant Core has the issue?

2024.2.1

What was the last working version of Home Assistant Core?

N/A, first version where implemented

What type of installation are you running?

Home Assistant OS

Integration causing the issue

govee_ble

Link to integration documentation on our website

https://www.home-assistant.io/integrations/govee_ble/

Diagnostics information

Enabling the debug logging for ~1 hour where the temperatures did switch between normal/13.1/26.2 recorded nothing…

Example YAML snippet

Default integration via the "add device" button.

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

Original URL
State: open
Created 5 months ago
Comments: 19 (6 by maintainers)

Most upvoted comments

Most of the values read by HA are correct though, its just that sometimes it randomly gives some weird value as shown on the pictures above. Wouldn’t you need the values of such a value to find the issue?

To get a better idea what the issue is, I’ll need the data from when things are not correct. If the app is correct at the time, you can use the app value instead of the displayed device value

Alright, i’ll wait for the anomaly to occur and send you the details. I have to wait for them to be recorded by the debug logging now.

Crazyhead90 on Feb 15, 2024

Most of the values read by HA are correct though, its just that sometimes it randomly gives some weird value as shown on the pictures above. Wouldn’t you need the values of such a value to find the issue?

To get a better idea what the issue is, I’ll need the data from when things are not correct. If the app is correct at the time, you can use the app value instead of the displayed device value

bdraco on Feb 15, 2024