* Add backup helper
* Add hassio to stage 1
* Apply same changes to newly merged `webdav` and `azure_storage` to fix inflight conflict
* Address comments, add tests
---------
Co-authored-by: J. Nick Koston <nick@koston.org>
* Add backup endpoints to the onboarding integration
* Add backup as after dependency of onboarding
* Add test snapshots
* Fix stale docstrings
* Add utility function for getting the backup manager instance
* Return backup_id when uploading backup
* Change /api/onboarding/backup/restore to accept a JSON body
* Fix with_backup_manager
* Replace Supervisor resolution API calls with aiohasupervisor
* Use consistent types to avoid uuid issues
* Fix mocking in http test
* Changes from feedback
* Put hass first
* Fix typo
---------
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* Use aiohasupervosor for store addon info
* Use aiohasupervisor install addon
* Use aiohasupervisor for store info API
* Fix onboarding test
* Changes from feedback
* Move get_supervisor_client out of constructor
* Mock supervisor_client in tests
* Make property private
* Add virtualization field fo system info
* Add ntp sync and host connectivity
* Prevent nonetype errors
* Add supervisor_connectivity and fix tests
* Add mock of network info to other fixtures
* Update more fixtures with network/info mock
Co-authored-by: Sid <27780930+autinerd@users.noreply.github.com>
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
Co-authored-by: J. Nick Koston <nick@koston.org>
* Deprecate the map integration
* Revert changes in DashboardsCollection._async_load_data
* Add option to allow single word in dashboard URL
* Update tests
* Translate title
* Add icon
* Improve test coverage
Move analytics setup to stage 1 to avoid delaying frontend startup
analytics was only needed in the frontend startup phase for onboarding.
Its very unlikely the user will be able to complete the onboarding
steps and get to the analytics screen before analytics is done loading
so we can delay loading it until stage 1. To be absolutely sure that
it is ready, the core_config step in onboarding will wait to proceed
if it is some how still being setup
* Convert persistent notification tests to async
* Create/dismiss persistent notifications in exposed functions, not service calls
* Fix notify persistent_notification
* Remove setting up persistent_notification
* Drop more setups
* Empty methods
* Undeprecate sync methods because too big task
* Fix setup clearing notifications
* Fix a bunch of tests
* Fix more tests
* Uno mas
* Test persistent notification events
* Clean up stale comment
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
