Shelly Dimmer 2 consistently reports 32 degrees F only once, every day, just before 6am EST

[KruseLuds]

The problem

Here is a link to a full discussion of the issue:

What version of Home Assistant Core has the issue?

core-2024.7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

There is no other information available, there is no error in the logs

Example YAML snippet

Not applicable

Anything in the logs that might be useful for us?

Here is my setup:

## System Information

version | core-2024.7.1
-- | --
installation_type | Home Assistant Supervised
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.12.4
os_name | Linux
os_version | 6.1.0-22-arm64
arch | aarch64
timezone | America/New_York
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 5000
Installed Version | 1.34.0
Stage | running
Available Repositories | 1455
Downloaded Repositories | 28

</details>

<details><summary>AccuWeather</summary>

can_reach_server | ok
-- | --
remaining_requests | 31

</details>

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Debian GNU/Linux 12 (bookworm)
-- | --
update_channel | stable
supervisor_version | supervisor-2024.06.2
agent_version | 1.6.0
docker_version | 27.0.3
disk_total | 915.4 GB
disk_used | 35.5 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | 
supervisor_api | ok
version_api | ok
installed_addons | AdGuard Home (5.1.1), Log Viewer (0.17.0), Home Assistant Google Drive Backup (0.112.1), File editor (5.8.0), Core DNS Override (0.1.1), Matter Server (6.2.1), Cloudflared (5.1.14), Mosquitto broker (6.4.1), Ring-MQTT with Video Streaming (5.6.7), Terminal & SSH (9.14.0), RPC Shutdown (2.5)

</details>

<details><summary>Dashboards</summary>

dashboards | 10
-- | --
resources | 20
views | 44
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | June 3, 2024 at 6:47 PM
-- | --
current_recorder_run | July 8, 2024 at 10:58 AM
estimated_db_size | 3708.80 MiB
database_engine | sqlite
database_version | 3.45.3

</details>

Additional information

No response

[home-assistant[bot]]

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `shelly` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign shelly` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

shelly documentation shelly source _{^{(message by IssueLinks)}}

[KruseLuds]

I have a litte information to add which I also added to the forum link above: "I just determined more information on this when looking into what you said... I had forgotten but I had set up an automation long ago that reboots every shelly device, 30 seconds apart one after the other, starting at 4:45am (which seemed to help with stability at some point in the past). I am pretty sure that there is a hiccup that when this unit reboots it registers, once, 32 degrees fahrenheit. It is still an issue and I wlll continue to pursue it as such with the integration issue and shelly issues logged witht he manuafacturer."

[bieniu]

Please enable Debug for Shelly integration, wait for this temperature value, disable debug and attach the log.

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

Thanks

[KruseLuds]

Shelly supplied me with an RC (release candidate) firmware update and the issue has gone away, so when that comes out, it will not longer be an issue.