Shelly Door Window 2 entities unavailable

[wilotas]

The problem

Hi guys,

After last upgrade to 2022.11.1 entities of Shelly Door Window 2 device appear as "Unavailable" in HA. If I try to reload each device, some entities appear online (binary sensor for instance) but events are not launched.

I have same issue for 3 door window 2 devices.

What version of Home Assistant Core has the issue?

2022-11-1

What was the last working version of Home Assistant Core?

2022.10.X

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Shelly

Link to integration documentation on our website

No response

Diagnostics information

config_entry-shelly-df98784bcbacab05721142f20feb7abf.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[Intecpsp]

I had a 1 go down, but a 1PM stayed up. Tried to remove and re-add, but can't get it connected again

[wilotas]

I did not disconnect it. It was working for 2 years so I think it is something related with integration changes.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Cody @.> Sent: Sunday, November 6, 2022 5:12:53 PM To: home-assistant/core @.> Cc: wilotas @.>; Author @.> Subject: Re: [home-assistant/core] Shelly Door Window 2 entities unavailable (Issue #81654)

I had a 1 go down, but a 1PM stayed up. Tried to remove and re-add, but can't get it connected again

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/81654#issuecomment-1304835806, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAD5KWVW2EYAO4FG3GKSJ3DWG7DHLANCNFSM6AAAAAARYNFOVA. You are receiving this because you authored the thread.Message ID: @.***>

[Intecpsp]

Yeah, I even just factory reset it and it's still not connecting. I also removed the 1PM and it added back instantly.

[wilotas]

Something affecting battery devices I think. All other like 2.5, 1, 1L are working as usual.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Cody @.> Sent: Sunday, November 6, 2022 5:35:03 PM To: home-assistant/core @.> Cc: wilotas @.>; Author @.> Subject: Re: [home-assistant/core] Shelly Door Window 2 entities unavailable (Issue #81654)

Yeah, I even just factory reset it and it's still not connecting. I also removed the 1PM and it added back instantly.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/81654#issuecomment-1304839901, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAD5KWTRI27IMFZOVJGOUUDWG7F2PANCNFSM6AAAAAARYNFOVA. You are receiving this because you authored the thread.Message ID: @.***>

[home-assistant[bot]]

Hey there @balloob, @bieniu, @thecode, @chemelli74, 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 Change the title of 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.

_{^{(message by CodeOwnersMention)}}

---

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

[chemelli74]

Hi all, did you configure unicast as per documentation ?

Simone

[wilotas]

Hi Simone.

It was not configured in unicast before (earlier 2022.10.X versions) and it was working for 2 years. Anyway, i tried to configure unicast this morning with same results. No event triggers, some entities not detected...

Something strange.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Simone Chemelli @.> Sent: Monday, November 7, 2022 12:37:22 AM To: home-assistant/core @.> Cc: wilotas @.>; Author @.> Subject: Re: [home-assistant/core] Shelly Door Window 2 entities unavailable (Issue #81654)

Hi all, did you configure unicast as per documentation ?

Simone

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/81654#issuecomment-1304927547, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAD5KWSNOHPBWNW2SI6RYI3WHA6LFANCNFSM6AAAAAARYNFOVA. You are receiving this because you authored the thread.Message ID: @.***>

[chemelli74]

Please add the following to configuration.yaml , restart HA, and post the log:

logger:
  default: warning
  logs:
    homeassistant.components.shelly: debug
    aioshelly: debug

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.

Simone

[thecode]

From previous issues it turned out to be firewalling issue in the host OS, what OS you use to run the container? We had multiple similar issues when nothing changed from the user perspective, however and update for the host OS changed something.

Please add the following to configuration.yaml, restart home assistant, generate a state change in the device and attach the log.

logger:
  default: info
  logs:
    aioshelly: debug 
    homeassistant.components.shelly: debug

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

[wilotas]

Hi,

I will configure that entry in configuration.yaml for sure.

I have been using Synology DSM as host to run docker.

Just to be sure, where will I find the log file?

Regards

[wilotas]

logshelly.txt

Attached log after activating switch wich should be detected by Door Window 2 sensor.

[thecode]

The log shows that the device needs authentication but it is not provided by HA, however this entry can be wrong. To identify the problem please attach the FULL log, thanks

[wilotas]

logshelly_full.txt

Thanks @thecode . I saw that in the log but I did not change anything in the devices settings. I atttached full log.

Thanks for the support, again.

[wilotas]

Hi guys,

Seems that last Shelly firmware activates the RESTRICT LOGIN option by default in settings. Deactivating it, it works as usual.

Regards

[thecode]

Thanks for the update, closing, if you still experience issues feel free to comment and I will re-open.