Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shelly Plus RGBW PM unavailable on input event #135003

Open
maceace opened this issue Jan 7, 2025 · 15 comments
Open

Shelly Plus RGBW PM unavailable on input event #135003

maceace opened this issue Jan 7, 2025 · 15 comments

Comments

@maceace
Copy link

maceace commented Jan 7, 2025

The problem

Good day. Does anyone know why my shell device always disconnects for a moment when I change the input status? See the video:

Screen_Recording_20250107_155018_Chrome.mp4

config_entry-shelly-01JCTB4HEQVCBG4HQMETHPGV27.json

What version of Home Assistant Core has the issue?

2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

diagnostics-shelly-plus rgbw pm-debug-log.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Tasks

Preview Give feedback
No tasks being tracked yet.
@home-assistant
Copy link

home-assistant bot commented Jan 7, 2025

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)

@thecode
Copy link
Member

thecode commented Jan 7, 2025

Thanks, to investigate this we need diagnostics

  • Please download the diagnostics from the device card in Home Assistant and attach it in a comment. and debug logs from Home Assistant not from the device.

  • Please enable Debug for Shelly integration, toggle the input to generate error, 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

@maceace
Copy link
Author

maceace commented Jan 7, 2025

@maceace
Copy link
Author

maceace commented Jan 7, 2025

Uploading error_log-4-bin.txt…
Rename error_log-4.bin

@thecode
Copy link
Member

thecode commented Jan 7, 2025

Uploading error_log-4-bin.txt… Rename error_log-4.bin

The link is broken for this one

@maceace
Copy link
Author

maceace commented Jan 7, 2025

I don't know how else to send the *.bin file.
error_log-4-bin.txt

@thecode
Copy link
Member

thecode commented Jan 7, 2025

Does the input change trigger an automation or a change in the device config/settings?

@maceace
Copy link
Author

maceace commented Jan 7, 2025

the entrance is separate
input change triggers automation

@thecode
Copy link
Member

thecode commented Jan 7, 2025

Can you share the what is the automation sending to the device? can you disable this automation and check if the problem disappear?

Thanks

@maceace
Copy link
Author

maceace commented Jan 7, 2025

I turned off automation, the problem persists

@maceace
Copy link
Author

maceace commented Jan 7, 2025

The automation says, when the cabinet door is closed 1 sec (switch on), turn on the LED strip to 20% , wait 30 seconds, turn off the strip.

@thecode
Copy link
Member

thecode commented Jan 7, 2025

Can you enable the uptime sensor and make sure the device doesn't reboot after changing the input state?

@maceace
Copy link
Author

maceace commented Jan 8, 2025

Yes.
I activated the uptime sensor.
I just changed the input status.
The uptime sensor has the status: 14 hours ago .

@thecode
Copy link
Member

thecode commented Jan 8, 2025

14 Hours is low, unless you know you rebooted the device, but probably not the issue.
Does the change to unavailable happens immediately or 60 seconds after the input change?

@thecode thecode changed the title Shelly plus rgbw pm Shelly Plus RGBW PM unavailable on input event Jan 8, 2025
@maceace
Copy link
Author

maceace commented Jan 8, 2025

immediately. it is evident from the video

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants