Update sleep period for Shelly devices with buggy fw

[chemelli74]

Breaking change

Proposed change

Update sleep period for Shelly devices with buggy fw

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Shelly Door/Window 2 becoming "unavailable" until reload of Shelly Integration #107533
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @balloob, @bieniu, @thecode, @bdraco, mind taking a look at this pull request 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 pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign shelly Removes the current integration label and assignees on the pull request, 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 pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[thecode]

Suggested change

	LOGGER.warning(
	LOGGER.info(

I think this can be in info level, no need to warn the user as there is no action needed from the user side we can silently update the value and it will still be visible if we ask for logs

[chemelli74]

Many users have a default level of WARNING, this is why I prefer to make it visibile.
Anyway is a single shot, not a recurring one so if not visible the first time is lost.

[thecode]

I think a warning should only be visible if there is something that the user needs to take care about (connection error, something that is configured incorrectly or doesn't work).

I had multiple times when I was asked in PRs to reduce the level not to make users worry about things they can't control or need to inform us.

In any case if another code-owner thinks this should be warning let's keep it as warning.

[thecode]

Main change is to move the block before we init the device and fix the test, constants would be nice

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.