* Sync sensors with individual servers
- Update sensors once, and allow syncing enabled/state with individual servers instead of doing the same for every server
- Default to the default sensor enabled state for new servers instead of copying another server
* Make last update sensor server-specific
* UI
* New servers: enable if enabled on any server
* Handle per-server enabled state in location tracking
* Fix icons in dark mode
* Server gestures and chooser
- Add gestures to quickly switch between multiple servers
- Add a chooser to select a server, and add a gesture for it
* Fix history (new page is added _after_ loading finishes)
* Sync Thread datasets when starting Matter commissioning
- When starting Matter commissioning from the frontend, check if there are Thread datasets on the device or in core but not the other, and if so try to sync them
* Also sync Thread datasets in shared device flow
- Datasets may not be used by the system but it is useful for future devices
- Make methods in ThreadManager a bit more general
* Multiserver foundation
- A foundation to build multiserver support on. Not ready for general use.
* Update new vehicle support
* Rebase fixes
* Multiserver settings
- Show settings for the correct server when editing server settings from the settings
* Bind session to device/install
- Save an install id with the app install to make sure that it isn't re-used on another device causing issues
* Add migration
- Migrate server info from shared preferences to the database after database migration and clean up
- Remove unused url shared preferences
- Read/save server version from/to database
* Fix auth error when session is refreshed
* Show server name instead of URL
- Read the server name when getting the config, and save it to the database
- Allow the user to override the server name in the app's settings
* Multiserver notifications
- Make notifications aware of which server sent the notification
- Show server name in notification if more than 1 server is added to the app
- Use the server-specific repositories when calling webhooks/authenticating/etc
* Handle multiserver in websocket worker
- Copy the settings database row to the new server ID to allow for server-level settings (websocket) while keeping the original for app-level settings (sensor update frequency), and handle this in onboarding
- Make the websocket worker check in on all servers and open/close connections where required
- Add the webhook_id to websocket notifications to link them to servers
- Update ServerManager servers to defaultServers because I'm using the same filter everywhere
* Migrate shared preferences
- Move server-specific device name to Server and secret key to ServerConnectionInfo
- Add a server ID key to the remaining shared preferences and migrate existing values
* Add option to delete server from settings
- Allow deleting servers directly from the app's settings, because you might not be able to do so from the frontend.
* WebView switching and active server management
- Allow switching which server is considered 'active' and used for the webview when loading
- On auth errors remove the server instead of removing the URLs (?)
- When getting external auth consider that the server might just have been removed (possible race condition from frontend which frequently causes 1 unauthorized connection when logging out)
- Fetch config after adding a new server to fill in name and version before first use
* Sync registrations and blocking load
- When starting the app, sync all registrations
- Remove Wear state with server but new registration required
- When receiving a new push token, update all registrations
- Do a blocking load for getting the servers because otherwise the app might think it's not registered when running in the background
* Use StateFlow for the server list
- Don't manually refresh but use a StateFlow to get updates pushed when the list of servers changes
- Make settings use unique server keys to prevent constant remove/re-add
* Sensor updates and sync with multiple servers
- Send sensor updates to all servers and sync changes to the app. Sensors are shared across all servers the app is connected to so changing enabled state on one server will update it for all servers.
- Don't update sensor enabled state for location tracking directly from onboarding, this should be done in the result.
- Remove unused SensorWithSettings class
* Send NFC tag scans to all servers
* QS tiles server selection
- Listen to updates for a specific server
- Allow selecting server if there is more than one
* Shortcuts server selection
- Allow selecting server if there is more than one
- Extract OutlinedButton with DropdownMenu for server selection to a standalone Composable
- Update QS tiles to not automatically reset server ID when server no longer exists, align with shortcuts
* Fix revoked sessions + crashing app
- When a session is revoked update the session object to reflect it
- Fix app crashes on revoked sessions because of race conditions with the AlertDialog causing window active/inactive at the same time as finishing it
* Extra server onboarding tweaks
- Skip welcome and location
- Save/fix notification preference for minimal version
* Fix sensor state type conversion errors for new servers
- If the state is removed but the type isn't, this can result in unwanted conversions throwing errors so remove the state type as well when copying a sensor
* Matter multiserver
- Request specific server ID in Matter functions
- Add server selection to shared Matter device flow
* Android Auto multiserver
- Allow switching server in Android Auto. Defaults to active server, note that it doesn't change the default but only changes it in AA.
* Widgets server selection
- Add server selection to all widgets and update handling to use the selected server
* Clean up TODOs out of scope
* Device controls multiserver
- Subscribe to updates for each server that controls are added for
- Allow managing lock screen enabled controls for each server
* Don't try to register sensors when finishing
- Don't try to do a sensor update when finishing, as this may cause unintended use of resources we're trying to clean up (when deleting a server)
* Server-level zones and location tracking
- Keep track of which server a zone belongs to for location tracking, and send updates only to that server
- Add server name to zone selection setting
* Merge fix
* Show 'Activate Server' any time there are multiple servers
- If the user is looking for the option to go to their server why hide it if it is already used, making them go back twice?
* More consistent strings
* Improve add server feedback in settings
- Preserve the activate server before adding a new one to prevent unexpected active server changes
- Show a Snackbar when another server is added indicating success with a button to activate it, or failure
* Remove unused ServerManager
* Fix tag import
- Update images to align with Matter branding guidelines
- Remove "shared" from screens as this flow is also used for fast pair where it makes no sense
* Move server settings to a server settings screen
- Move server-specific settings to a new screen to be accessed from the main settings only containing server specific settings in preparation for multiserver
- Sensors is currently not server-specific even though one setting is stored by server ID, to be fixed later
* Store app preferences in another shared preferences file
- Store app preferences not in the integration shared preferences file, but in the shared preferences file for general prefs (it is named themes but there are already other app-level prefs in it)
- Move Wear specific preferences to it's own repository + shared preferences file
* Improve server row with local data
- While we don't have a server name or user name, show the registration name when available to improve the server row layout
* Simplify location permission request code
- Remove the flexible permission requests as it isn't used in the current settings structure, only expect location permissions
- Switch from the deprecated functions to the new flow using activity result contracts
* Remove unused string
* Initial commit of wear OS notifications
* Update to allow message and title
* Move constants to object to reduce imports
* Split up logic to match phone app
* Update readme and set websocket to false for wear OS
* Bump firebase BOM
* Initial work on Android Auto support.
* Get some toggling working, add a main view that is useful.
* Make sure we can test this on every commit.
* Migrate to full flavor.
- Add option to quick settings tile to only allow interacting with it when the device is unlocked, similar to device controls on Android 13 (but phrased differently to match the system default behavior)
- Add a lot more quick settings tile services
- Enable QS tile services only for tiles up to the highest tile # in use + 4, with a minimum of 12, to prevent long lists and make it work 'automagically'
* Update instead of cancel notification on reply
- When a notification is replied to, update it instead of cancelling it to allow the other to continue manipulating it
* Support multiple replies
- Keep a history of replies in the bundle to match system behavior
* Only keep replies that are actually shown
* Update Matter dependency
* Improve shared device commissioning
- Show device name if available
- Show error codes if returned
* Show toast for commissioning request errors
- When an error occurs for commissioning requests/before the Play Services UI is shown, show a toast informing the user that Matter is currently unavailable. Most user-facing errors will be shown in the Play Services UI (during commissioning).
* Add setting to start the app always on the first dashboard view
* Run linting
* Do not close SettingsActivity
* Only show first view if not in HA Config + Fix flash of dashboard when navigating to app settings
* Scroll to top when calling first view of dashboard
If we are on a another view a we are scrolled to the bottom, the first view will be also at the bottom
* Use default dashboard as starting dashboard
* Allow HA config dashboard to call the first view of dashboard
- Also disallow /hassio (Home Assistant addons) to call the first view
* Enhance show first view setting description
* Fix class name spelling LifecycleHandler
* Fix calling first view of dashboard on config/areas and config/automation
Co-authored-by: Justin Bassett <bassett.justint@gmail.com>
* Add new option to vibrate when quick settings tile is clicked
* Use vibration effects if the device supports it
* Review comments
* Remove question mark
* Set switch color when unchecked
* Matter commissioning: MVP
- Implement a basic framework for the app to support Matter commissioning
- Add hooks for the `matter/commission` message that will be sent by the frontend to trigger Matter commissioning
* [WIP] HA as Matter share target
* [WIP] Updated commissioning flow
- Add websocket Matter API support
- Update architecture to better ensure a working minimal build
- Remove external bus responses for Matter commissioning message
* Rename MatterRepository
* Handle shared Matter devices
- Adds UI to handle shared Matter devices instead of copying the pairing code to the clipboard
- Updates the on network pairing pin/code to be a String, which may be received for shared devices
* Cleanup test button
* Pairing code type and service error handling
- Update pairing/pin code type to Long for server
- Send Play Services error if commissioning returned an error
* Increase timeout for Matter commissioning requests
* Use normal commissioning for shared devices
- Use the normal matter/commission command for devices shared with the app
- Shared device UI polishing
* Fix minimal and remove old name
* Update frontend commissioning status enum
* Update quick setting tiles with state updates
* Keep track of appropriate job to cancel when needed, use variable for toggle with lock
* Switch to Job from CoroutineScope
Catch ActivityNotFoundException for downloads
- When trying to forward a download intent to the system catch the exception that is thrown if the system can't handle it to prevent a crash
* Manage app language using AndroidX, integrate with Android 13
- Manage the app language using AndroidX to fix the setting not being applied and to be able to easily integrate with Android 13's system setting
* Move locales_config.xml to common
* Generate locales_config.xml when downloading translations
* Fix multiple variants for languages being collapsed into one
* Fix language codes with region variants
* Don't split languages when using app bundles
* Rename
* Add daily floors sensor for Wear OS3 devices
* Do a compatibility check for sensor availability in health services
* Print more logs and attempt to send latest data, update more getAvailableSensor methods
* Process review comments
* Process more review comments, use actual time in millis
* Clear out available sensors when updating with new list
* Log the capabilities in case we need to troubleshoot later
* Review comment
* Missed one additional review comment
* Return immediately instead of storing a list
- If no Wear app is installed on a device, checking for nodes will throw an exception that the API is unavailable. This is an expected error, don't log it to not confuse users.
* Update change log for week of 10/21
* Add data roaming breaking change fix
* Update per recent merges
* Mention breaking change for command_bluetooth on android 13+ devices
* Support zone name only location tracking
* Update strings to match iOS
* Only add Sent location setting on supported versions
* String updates
* Simplify code as the setting is always on
* Save cloud URL separately and add pref
- Save the cloud / remote UI url that is received during registration separately, and add a preference to use the cloud url instead of the external url
- Save the cloud / remote UI url and cloudhook url received during webhook config updates, to be able to support using cloud after the app was set up
- Clean up cloudhook url when logging out
* Add UI for "Use Home Assistant Cloud" url
* Cleanup
* Fix function order
- Update onBackPressed functions which have been deprecated to use the new OnBackPressedDispatcher and OnBackPressedCallback
- Indicate support for the predictive back gesture
* Use compressed entity changes for device controls
- Add support for the subscribe_entities websocket subscription which delivers initial state + changes in a compressed format to reduce data usage
- Use the new subscribe_entities format in device controls on supported Home Assistant versions
* Less duplicate code
* Add notify command for app-lock
* Add null check for optional parameters
* Only allow enabling app_lock by notify command if previously enabled by user
* Use constants for app lock command parameters
* Add BiometricManager check before turning on app_lock
* Remove 'hasLockEverBeenEnabled' in favor of only biometricmanager check.
* Improved value checking for app lock command.
Made setAppLock function suspending i.s.o. sepearate runBlocking calls.
* Show notification if no parameters were updated.
* improved parameter value checking
* Don't make changes when invalid data is provided
* Early check on argument validity for app lock commands
* Cleanup app lock command parameter validation
* Request notification permission during onboarding
- When using Android 13 or the minimal version, add a screen to onboarding to request to enable notifications on the device. This screen is based on iOS onboarding. When tapping Continue, on Android 13 this requests the system permission and/or on the minimal version this changes the websocket setting.
- Compile with and target SDK 33 (targeting required to be able to request notification system permission on demand)
* Add notification settings link in settings when off
- Show a new setting in settings for the user to enable notifications for the Home Assistant app, either because the permission was denied (Android 13) or the user manually turned off all notifications (Android 8-12).
- This new setting replaces the notification channels setting when everything is off; in this case there is no point managing individual channels. If at least one channel is on, the existing notification channels setting is shown instead.
* Compose tweaks
- Remove redundant content description for icon
- Change to a simpler scroll modifier
* Fix skipping notifications on minimal version
- Ensure that the value is actually saved to the database
* Post Bluetooth on/off commands as if invalid
- When using Android 13, post notification commands to control Bluetooth on/off as a normal notification as if they were invalid, as the function has been deprecated for the app
* Remove type that can be inferred
- Update Gradle to latest version (7.5.1)
- Update Android Gradle plugin to latest version (7.3.0)
- Move package property out of manifest into gradle build files namespace as recommended
* Merge Follow Home Assistant/Follow System Settings theme
- As these two themes behave the same now, don't present two options but instead just one. The default setting has been renamed back to "Follow System Settings" to best match expectations. Internally the "android" setting still works, settings will show "Not set".
* Remove useless webview force dark
- The WebView force dark settings are no longer required (and will no longer be supported when targeting Android 13), as the latest appcompat/webview/HA frontend already respect the app's theme setting and allow overriding it
* Add support for showing custom icons in device controls
* Clean up and set color based on state
* Set icon size and adjust colors based on domain
* Move color values to resources and add more color options from source
* Review comments
* Only set the icon if it exists in the library
* Add commands to control screen brightness and a sensor to get the value
* Minor file clean up
* Review comments
* Rename Device Settings to Display Sensors
* Add support for intent scheme URI in clickAction and actionable notifications
* Add a new prefix for app links in actions
* Rename app link to deep link to be more precise
* Use correct intent prefix
* Take user to the play store if the app is not installed
* Fix taking user to the market if app is missing, remove ability for deep links since we can't get the package name
* Only open the play store if we have an actual package to open to
* Add support for using BSSIDs for internal connection
- Add support for entering BSSIDs to use for detecting when the internal connection URL should be used. These are saved like any regular SSID, but contain the prefix "BSSID:".
* Add link to documentation
* Fix full screen mode for all devices
* Hide system UI when we regain focus and a video is still full screen
* Revert theme changes
* Remove unneeded line break
- Set the thumbnail template for the camera control to active as long as the camera isn't unavailable and the app was able to download an image, to show the camera image more often and better match the frontend.
- Instead of receiving all state changes when the device controls are open, only receive state changes for entities that were added as controls. This potentially reduces the amount of data used while controls are open.
* Improve adding quick settings tiles
- Use the new option available on Android 13 to prompt the user to add a tile to the quick settings panel, if a tile wasn't already added
- Switch Toast to Snackbar
- Move some logic from the manage tiles view to viewmodel
* Only show subtitle field when supported
- Setting a tile subtitle is only supported on Android Q+, so don't show the field on versions before that!
* Deeplink into app for tiles that aren't setup
- Instead of disabling a tile if it isn't setup, if the user is logged in set it up as inactive with the default icon/label and deeplink into the app settings with a notice that it needs to be setup first. This provides a better first use experience, as the user can simply tap it to setup instead of requiring them to manually go to the settings.
* Always do Wear onboarding on phone
- Switch the Wear onboarding to always use the sign in flow on the paired phone, instead of offering the option to sign in completely on the watch.
- When opening the companion app using the Wear app, immediately link the user to the list of instances or sign in screen.
- Use standard OAuth flow for devices without companion app installed.
- Fix type casting of location preference in Wear onboarding result.
* Fix ListenableFuture await import
* Add BLE Beacon Monitoring Sensor
* Fix on/off toggle
* Add on/off commands
* Fix commands
* Add all beacons to attributtes
* Add Kalman Filter
* Improve performance
* More settings
* cleanup
* Fix linter errors
* Update description
* Show monitoring state in sensor
* Add missing permissions
* Fix permissions
* Fix Bluetooth state of Android 12
* Use instance instead of singelton
* Use runBlocking for updateLastSendState
* Use own scope for beacon manager
* Use new notification commands
* fix rebase
* use null instead of empty string
* return if sensor is disabled
Implement subscribe_trigger and use it in widgets
- Implement support for subscribing using subscribe_trigger, currently used to get state changes only for specific entities
- Change the entity state and media player widgets to use this new subscription instead of subscribing to all state changes, based on the template widget
- Removed some placeholder code from media player widget
* Add setting to bypass app lock on home network
* Debug loging to check logic
* Fix logic. Cleanup logging.
* Disable home lock bypass when no home networks are configured.
* Only check for WiFi SSID, not internal URL when evaluating isLockEnabled.
* Fix build error
- Adding a media player widget from settings didn't work because the list used to check that entities have been selected isn't updated immediately, but only on load or in a callback after pinning the widget. To work around this, manually check it before pinning the widget.
* Add some more attributes to geocoded sensor and check that device supports it
* Remove language attribute as it does not supply the expected data
* Combine latitude and longitude into the location attribute again
* Update WebSocketRepository for multiple subscriptions of same type
- Change the structure of how the websocket repository tracks individual subscriptions to allow subscribing multiple times with the same type, but different data
* Update TemplateWidget to use template subscriptions
- Instead of depending on entity state changes and refreshing any time there is a change, use the render_template subscription for the template widget to limit the amount of data and power used. To make this possible without too much abstractions, the TemplateWidget no longer implements BaseWidgetProvider.
- Fix hardcoded "Loading" string
* Handle potential null subscription ID
- Implements #2795 for changes to tracked subscription ID
* Handle failed subscribing similar to other failures (null)
- When subscribing fails, return null and don't store an active subscription instead of continuing and returning a flow (which would never emit messages)
* Update manifest
* Handle foreground service restrictions for persistent connection
- When trying to start the WebsocketManager as a foreground service, catch exceptions due to restrictions and show the user a notification to fix it
* Update logging in WebsocketManager
- Change to the OkHttpClient used elsewhere by the app to download notification videos to resolve problems related to cookies and mTLS authentication. As a result, storing and deleting the file is now handled by the app instead of by the system.
* Modify Notification GIF Framerate
Modoify VIDEO_INCREMENT_MICROSECONDS to have notification GIFs generate a frame every 0.5 seconds for a video instead of the current every 2 seconds. This should result in smoother notification animations thus improving the UX
* Increase processingFrames.size
Increase processingFrames.size as increasing the framerate results in the animation ending too soon
* Scale video to a max width of 480 while maintaining video ratio
Notification video width scaled to 480. (1920 / 4) Height will scale accordingly while maintaining video aspect ratio. e.g. 1920x2560 will be scaled to 480x640
Frames are set to every 1 seconds with 5 frames resulting in a 5 second GIF
* Update MessagingManager.kt
Based on research and rapid prototyping under another fork, I've decided that scaling the image to a fixed width and a ratioed height is not going to work. There are issues that need to be resolved which result in the image being cut off and stretched in the notification.
End result is the only overall change is changing the frame generation from once every 2 seconds to once every 1 second. This has improved the fluidity of notifications but I understand is my own subjective opinion.
This means there is still a potential case where 4K cameras will exceed the size limits of notifications.
* Typo fix
* Re-Implement Scaling to a Constant Width
* Update MessagingManager.kt
* Add logic to not scale videos smaller than specified width and Increase GIF speed (ViewFlipper)
* Tune processing times
Tune processing time to have one frame generated every 0.75s, then frames are played back at 3x speed. This results in 9 seconds of activity being played in 3 seconds.
* Implement Dynamic Frame Count
Dynamic number of frames up to a specified size limit (currently 2.5MB)
* Review Before Merge
* Actually update geocoded sensor on location updates we send to HA
* Ensure sensor is updated before checking if we should send the update
* Move update logic to sensor receiver, ensure last sent attributes are updated
* Restart location updates if we detect too much time passed since last update
* Switch to last location received for proper evaluation
* Code review: move variable logic to be inside the condition
* Fix websocket stays subscribed after widget edit due to multiple instances
- When a widget is edited, the system will send a broadcast to _a new instance_ of the widget class. Because there is a websocket connection to keep widgets updated, the new instance of the class should also receive events to unsubscribe.
* Use companion object to prevent unnecessary updates
- Only actually start listening for updates in one of the instances in order to prevent unnecessary duplicate widget updates
* Actually check the paired state instead of assuming it
* Ensure the attributes have no duplicates by making the lists distinct
* Actually check for duplicate devices to remove them
* Apply code suggestion
* Revert some changes and remove allowDuplicates per comment
* Add support for lock domain in QS tiles, change tile not setup message to be more precise
* Update dispatcher
* Review comments: Remove not setup from string, only get state if domain is lock when tile is clicked
* Remove duplicate strings
* Remove error message on null template
- Null is a valid value for a template so the app should reflect that instead of suggesting there is an error, which may cause users to start looking in the wrong place.
* Log.e instead of Log.i
* Add logging in authentication fragment to print errors
* Expand error messages to contain more useful data
* Add error content to pop-up to provide more data to the user
* Show more descriptive onReceivedError message
* Ensure the correct messages are used
* Add changes from @jpelgrom to only show the error on the expected URL
* Add condition to onReceivedErrror as well
Automatically delete stale widgets from database
- Automatically removes widgets that are no longer bound to the widget provider but that are still in the database -> 'stale'/old widgets will no longer cause unnecessary updates
- Removes the external storage permission for logs for devices on Android 6+, because the external cache dir is usable without this permission and it will no longer work when targeting Android 13 on Android 13 devices. It should work on Android 4.4 and above but this bug suggests it might not on Android 5, but it is auto-granted and needed for downloads anyway: https://issuetracker.google.com/issues/37013142.
- Set the maximum version for the external storage permission to Android 9; starting with Android 10 the download manager will use MediaStore.Downloads which doesn't require any additional permissions.
* Implement styling on the template tyle
* Also process preview in phone settings
* Small cleanup
* Improve template null handling
* Update template rendering error
* Update help text to indicate new line and markup options
* Also support newline
* More extensive replacement for <br>
* Add camera device control
- Adds a camera device control on supported devices (12+)
- Update content description for camera widget
* Improve Icon if downloading thumbnail fails
- Show a blank grey thumbnail like an empty tile if downloading the camera thumbnail fails, because the system will stretch the provided image so a 'proper' icon can end up looking weird
* Improve error handling
* Migrate SSID dialog to Compose, move + rename prioritize internal
- Replaces the SSID dialog with a new screen built with Compose (same functionality as before)
- Move the prioritize internal setting to the new SSID screen where it makes more sense, and rename it + style it as a dropdown to prevent unnecessary changes
* Remove unused Spacer
* Fix button widget field data overwrite on text change
- The text changed listener might be called while the button widget fields were being setup if a value exists. If other fields are bound at the same time this might overwrite their values and cause problems, so make sure to use the adapter position for the viewholder instead.
- If setting a value fails set the text input to empty instead of showing the previous value
* Fix incorrect input in button widget fields
- Properly set the hint for the button widget fields to null if no hint is available to prevent an old hint from being visible
- Properly set the autocomplete functionality to null if no autocomplete functionality is expected to prevent unwanted autocompletion
* Fix services list if service was previously selected
- Always load the full services list, even if a service was previously selected, and apply a filter on the list after setting it to prevent the dropdown from showing incorrect values
- Add specific error if the app encounters a HTTP 404 response during onboarding registration, because that means the mobile_app integration is missing
- After an error, clean up the session data to make sure a new registration attempt is made
* Show entity state on entity chip in Wear OS app
- Shows the color and position of an entity state on the entity's chip in the Wear OS app by using a custom background class that accepts more than a single Color
* Use horizontal instead of diagonal gradients
- The default BrushPainter actually isn't the correct one, the ToggleChip class uses its own but that is marked as internal and we cannot override the default BrushPainter so another copied class it is
* RTL entity position support
- When using an RTL language, the entity chip should fill in the position value from the right side
* Support cover position
- Show cover position as entity chip's background
- Adjust background color code to also work when a chip isn't checked for covers that are currently closing
* Cleanup EntityUi
* Cleanup duplicate code in device controls
* Naming conventions
- Should've used a lowercase letter to start
- Fix class
* Fix build
- Updates because ToggleChipColors has changed
- Add workaround for implementing Compose interface because kotlin-gradle-plugin is linked to stable Compose and we cannot update yet
* Update gradient values to match rc02
- Wear Compose 1.0.0-rc02 changed the default values for the gradients in ToggleChips, so update the values used when using a custom background to match
* Rebasing First TLS Client (MTLS) implemention onto upstream's master
* Removed commented code
* First Client TLS implementation rebased with upstream's masster
* Removed redundant semicolon
* Added try/catch to key import, added import feedback to enduser
* ktlint fixes
* Rely on the device Credential store
* Tweaked and cleaned the strings related to the TLS Client Auth message
* Removed commented code
* Attempt to remember the key alias and load it as soon as the app starts
* Cleaned rebase and tidying up code
* Added handler for HTTP error (when a certificate is not provided)
* When no certificate is availble, do the request to get an HTTP error back (for error handling)
* Pleased the linter
* Pleased the linter
* Switched to constructor injection
* Attempt to load the key in a non-blocking fashion.
* Do not loop around the blocking code
* onReceivedClientCertRequest now runs non blocking and the KCAC callback is used instead of polling.
* Wait until the executor task actually completes.
* Cleaned the code
* Removed unused import
* Wait for the executor to finishes executing its task
* During onboarding, if TLS Client Auth is enabled but no certificate is available, correctly report to the user
* Use a safe call on errorResponse
* Do not block anymore
* Removed unused return types
* Removed unused return types and the executor
* Removed unused imports
* Code cleanup
* Improved synchronization
* Added a string for certificate expiration
* Added a function to clear the alias and removed blocking code
* Added a function to clear the alias
* Display an error message if the user certificate is not valid plus minor refactoring
* Check the validity of the selected certificate
* Added an error message if the client certificate is not valid
* Resolved warnings and linting issues
* Fixed broken branch when testing for error condition
* Removed unused imports
Co-authored-by: Mirco Boschi <mircoboschi@gmail.com>
* Fix storage sensors to update continuously and do some refactoring in StorageSensorManager
* Fix size unit formatter logic.
So now it can not only output 0GB for smaller values (<1GB) but also 345MB or 640KB for example
* Use String.format(...) for adding thousands separator and replace StringBuilder usage with template
* Speed up loading device controls by running network async
- Speed up loading the device controls menu and initial controls by launching all requests in an async block, which allows the server to respond out of order
- For individual controls, only start listening for changes once we have provided initial controls
* Speed up Wear OS cold boot by running network async
- Speed up a cold boot of the Wear OS app by launching all network requests in an async block, which allows the server to respond out of order
* The webview activities now handle keyboard|keyboardHidden|navigation
configuration changes by keyboard connection changes, to avoid the
activity restart which leads to frontend reload.
* Don't include devices twice in Bluetooth list
- Don't include Bluetooth devices twice in the devices list when using it for location-related functions. Do allow duplicates for the BT sensor for backwards compatibility.
* Switch high accuracy mode BT constraint to device address
- Change the Bluetooth device constraint for high accuracy mode for location updates to use the Bluetooth device address instead of the device name to ensure uniqueness + fix crash in sensor settings screen
- Set padding in Scaffold because lint doesn't seem to like ignoring it
* Migrate high accuracy mode BT constraint names to addresses
- When enabling the high accuracy mode, make sure that all data for the Bluetooth device constraint is a Bluetooth device address and if not try to match it to a device.
- Because the database can contain devices that are not currently paired/connected, without changing to a new setting this check always must be executed, which is why it is placed in the function for enabling the high accuracy mode.
* Also show user-friendly labels in sensor settings detail screen
- Update the sensor settings detail screen to also show a user-friendly label for list settings on the main screen, before opening a dialog. This will use the same function as when the dialog info is populated, which simplifies code.
- Merge SensorSettingType.LIST with other list types rows in sensor settings detail screen, remove getSettingTranslatedEntry in viewmodel which is no longer necessary.
* Fix empty Bluetooth list setting value when off
* Bump reorderable and fix breaking changes
* Only include reorderable with full version
* Improve "Wear Favorite Entities" screen design
- Fix too small touch targets for dragging
- Fix no background resulting in overlapping text when dragging
- Update design to standard Material design
- Re-use Composable for selected and unselected favorite entities
* Add dagger module for daos
* Update classes in common to inject daos
* Update app view models to use inject
* Use inject with widgets
* Update app activities and fragments to use inject
* Clean up imports
* Make TileExtensions use coroutines
- Instead of silently failing, inform the user that a sensor cannot be enabled due to missing permissions and provide a link to change the setting. If possible, name the specific permission that is required.
* Sync sensor enabled state from app to core
- Change sensor 'registered' to indicate not registered, registered as disabled or registered as enabled
- When a sensor is disabled, set it's status as such on core 2022.6 servers
- In the sensor registration, use the basic sensor details in case there is no info in the database that can be used
* Clean up version check
- Now that there is a standard function to get the version, re-use it
* Improve which sensors are synced to core
- Update database migration to reset registration state on db upgrade to make sure the information is correct for all sensors
- Only sync sensors that are actually available on the device
- Fix registering all sensors on core <2022.6 on app/core version change
- Fix unnecessary sensor updates due to location sensors which are never registered always triggering update on core >=2022.6
* Sync sensor enabled state from core to app
- After pushing app enabled changes to core, if on core 2022.6 check if the enabled state for any of the sensors is different from what is registered in the app and try to update the sensors. This is done by reading the entire config, because otherwise we wouldn't know about sensors that have been enabled and the app already updates all sensors at the same time so no need for tracking individual updates in the sensor update response.
- Restore getting config using webhooks, because only the webhook config contains information about entity enabled state
- Add support for opening a specific sensor's settings page, used for the notification when trying to enable a sensor that requires granting (additional) permissions
* Update Media Player Widget Preview
* Add support for multiple media players. optionally show media source label
* fix crop of media player widget preview image. avoid unnecessary api call's when finding active media player. add db migrations. add text color to media source label. set default value of showsource to false.
* remove placeholder source for source icon to fix widget preview
- Use unique tags to allow identifying which function receives an error
- Actually use the onReceivedSslError callback error
- Also show SSL errors in the external auth callback
* Provide Compose preview for Play Store listing screens
* Update previews for onboarding
- Set theme correctly and show system UI
- Add variant for dark mode
* Update Wear OS listing image
* Remove specific icon, we can use domain default
* Improve time zone sensor string
- Update string to reflect if the time zone is using summer/daylight savings time or not
- Use the user's language settings instead of always using English
* Keep using English for sensor state
- Catch any exceptions thrown during app registration (after webview login) instead of crashing. There should only be a few errors possible here that are not encountered in the webview.
- Set dialog theme to fix background on API <31
