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

Entities unavailable for sleeping devices #1802

Open
6 tasks done
chemelli74 opened this issue Jun 29, 2024 · 13 comments
Open
6 tasks done

Entities unavailable for sleeping devices #1802

chemelli74 opened this issue Jun 29, 2024 · 13 comments
Labels
bug Something isn't working

Comments

@chemelli74
Copy link
Contributor

System Health details

System Information

version core-2024.6.4
installation_type Home Assistant Container
dev false
hassio false
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 4.4.302+
arch x86_64
timezone Europe/Rome
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4989
Installed Version 1.34.0
Stage running
Available Repositories 1390
Downloaded Repositories 22
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Dashboards
dashboards 2
resources 12
views 14
mode storage
Recorder
oldest_recorder_run 19 giugno 2024 alle ore 19:53
current_recorder_run 28 giugno 2024 alle ore 19:17
estimated_db_size 972.75 MiB
database_engine sqlite
database_version 3.44.2
Spotify
api_endpoint_reachable ok

Checklist

  • I have added battery_notes: to my configuration.yaml and restarted.
  • I have read the FAQ's.
  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of any previous issues..

Describe the issue

Some device are not always connected and shows some entities as unavailable:

image

Should be "restore" entity so to avoid this issue.

Reproduction steps

  1. install Motion Shelly or any other sleeping device
  2. configure battery notes
  3. check all is fine
  4. wait for device to go sleeping
  5. recheck entities

Debug logs

No response

Diagnostics dump

No response

@andrew-codechimp
Copy link
Owner

andrew-codechimp commented Jul 1, 2024

Thanks for reporting this. I don't have any devices that sleep but you are correct, Battery+ should restore its state.

The new beta 2.3.12 now has this change, if you are able to validate I'll close this issue.

@andrew-codechimp
Copy link
Owner

Feedback from #1843 suggests this isn't fixed unfortunately.
Sorry, there is just something odd about the Shelly Door/Window sensor that's not getting it identified as a having a battery.
There's little I can do about this without having one to test myself so having to close this as unfixable.

@chemelli74
Copy link
Contributor Author

Hi,

The point is that those entities should be restored entity in order to work correctly.

Thank you for considering the code change.

@andrew-codechimp
Copy link
Owner

The latest beta does change them to restored entities but doesn't seem to have an effect.
It was a worthwhile change and may help with others but doesn't seem to fix the Shelly sensor.

@chemelli74
Copy link
Contributor Author

Will better investigate as soon as ai have the time for this task

@nicx
Copy link

nicx commented Aug 13, 2024

@andrew-codechimp is this problem fixed? I have a similar experience with all of my Shelly TRVs. When they are awake and I add them to HA Battery Notes everything is working as expected. After some time all Battery+ Sensors get unavailable. There is no chance to get them back working except to delete the device and read it. Shall I open another new issue?

Bildschirmfoto 2024-08-13 um 13 51 45

@andrew-codechimp
Copy link
Owner

I made these entities restore entities so thought they were fixed but if you are running the latest version then that appears not to made a difference.

Unfortunately I don't have any of these devices to be able to test this further so I don't have a way to fix this for these devices.

@nicx
Copy link

nicx commented Aug 14, 2024

@andrew-codechimp thanks for the info, even if that is of course a great pity. ;)

@andrew-codechimp
Copy link
Owner

I will reopen this issue just as a reminder to myself if I ever get a device to test or more inspiration.

@andrew-codechimp andrew-codechimp added the bug Something isn't working label Aug 14, 2024
@confucius78
Copy link

Hi @andrew-codechimp, is there anything I/we can do to help?

@andrew-codechimp
Copy link
Owner

Hi @andrew-codechimp, is there anything I/we can do to help?

Thanks but I think I'll have to read through the Shelly BLE code to see if there's anything odd there I need to handle.
I have some BLE devices myself (Xiaomi plant sensors) that do come back so it's not all BLE devices that have the issue.

@confucius78
Copy link

confucius78 commented Aug 20, 2024

Okay, well let me/us know if that changes. Happy to help. Actually it’s also not just BLE. I have them on wifi, but same issue 😉

@andrew-codechimp
Copy link
Owner

Okay, well let me/us know if that changes. Happy to help. Actually it’s also not just BLE. I have them on wifi, but same issue 😉

Good to know, I'll expand my scope to the whole Shelly integration then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants