core icon indicating copy to clipboard operation
core copied to clipboard

integration: shelly Very slow updates.

Open dougle03 opened this issue 1 year ago • 15 comments

The problem

I've had a Shelly EM for over a year now and all good until about 3 months ago when the power measurements updates slowed right down to sometimes as slow as once every 40 seconds. It used to report power monitoring (watts for example) about every second. I've contacted Shelly to see if they have made changes to the update frequency but they have not released a FW update for my Gen1 device for nearly a year. The only other option is the Shelly integration or HA that's throttling the update frequency on this integration...? I'm not using the Shelly cloud so this is a local issue not cloud related. Any ideas...?

What version of Home Assistant Core has the issue?

core-2024.7.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

dougle03 avatar Jul 06 '24 08:07 dougle03

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)

home-assistant[bot] avatar Jul 06 '24 08:07 home-assistant[bot]

Is CoIoT configured correctly?

Please enable Debug for Shelly integration, wait an hour, 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

bieniu avatar Jul 06 '24 08:07 bieniu

Is CoIoT configured correctly?

Does this look ok? 10.10.50.8 is the static IP for my HA installation. And the port is the default 8123 image

dougle03 avatar Jul 06 '24 10:07 dougle03

Please enable Debug for Shelly integration, wait an hour, disable debug and attach the log.

Running now; will revert in an hour. Thanks for your help 🙏

dougle03 avatar Jul 06 '24 10:07 dougle03

Is CoIoT configured correctly?

I am running HA core in a docker container on a RPi4 8gb - It used to update about every second, then just fell off the ball...

dougle03 avatar Jul 06 '24 10:07 dougle03

And the port is the default 8123

You have to use port 5683 not 8123 https://www.home-assistant.io/integrations/shelly/

bieniu avatar Jul 06 '24 11:07 bieniu

You have to use port 5683 not 8123

Was this a recent change? The confusing thing is that It's been working just fine, then dropped off... I'll change the port (And map it in Portainer) see if that solves the issues.

dougle03 avatar Jul 06 '24 11:07 dougle03

Please enable Debug for Shelly integration, wait an hour, disable debug and attach the log.

Hi, here's the log if that's helpful. Thanks config_entry-shelly-370f35546be2c8b03f57c062e4477566.json

dougle03 avatar Jul 06 '24 11:07 dougle03

Was this a recent change?

No, port 5683 for CoIoT is used... forever.

here's the log

This is not a log file, this is a diagnostic file. But in this situation you have to catch a new log after changing the port to the correct one.

bieniu avatar Jul 06 '24 12:07 bieniu

What's confusing me is that it used to work just fine, the update frequency was circa 1-2 seconds, then suddenly it's changed to sometimes upto 40seconds. I can turn a 3kw kettle on for 10 seconds and off again without a single update. Regardless of ColoT, It used to work better. Is ColoT a red herring perhaps? Only one error showing for the Shelly (I only have the one Shelly device). image

dougle03 avatar Jul 06 '24 12:07 dougle03

Status updates every few seconds are not possible without a properly configured CoIoT unicast or (after certain conditions are met) multicast. If status updates were once more often, it means that you had to change something in the configuration of devices and/or network.

bieniu avatar Jul 06 '24 12:07 bieniu

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Nope, still the same problem. Sometimes it updates every second, other times it can freeze for over a min.. Not really very useful...

dougle03 avatar Oct 04 '24 13:10 dougle03

If you have correctly configured your device, update HA to the latest version and attach the current log and diagnostics file.

bieniu avatar Oct 04 '24 14:10 bieniu

I have the same issue with the Shelly PM mini gen3. Sometimes the „power“ entity Updates just every ~30minutes! In the Shelly App it shows the correct power value. It seems like the entity in HA just updates if the changes in a higher range. If it‘s „just“ 0,xW off, it doesn‘t receive an update every time. Sometimes it‘s fine and updates every time.. very weird.

see attached the diagnostics file. config_entry-shelly-01J9XVFRSCSK9VC3K4GWBZ3C1X.json

Nappyy avatar Oct 13 '24 20:10 Nappyy

@Nappyy The open post is about Shelly Gen1 device, and yours is Gen3. These are completely different devices. Please open a separate issue. Thanks.

bieniu avatar Oct 20 '24 19:10 bieniu

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Nope, still a problem; can be upto 60 seconds between updates, then other times one update a second. No pattern I'm afraid...

dougle03 avatar Nov 03 '24 20:11 dougle03

Please follow https://github.com/home-assistant/core/issues/121364#issuecomment-2393879030 and provide logs and diagnostics, there is no point keeping this issue open waiting for magic to happen without logs.

thecode avatar Nov 03 '24 20:11 thecode

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.