mirror of
https://github.com/house-of-abbey/GarminHomeAssistant.git
synced 2025-04-30 12:42:27 +00:00
Documentation tidy
Co-Authored-By: Joseph Abbey <me@josephabbey.dev>
This commit is contained in:
@ -14,6 +14,10 @@ In both cases, the enable and repeat time settings can be changed whilst the app
|
||||
|
||||
## Listening for the `device_id`
|
||||
|
||||
Open the event viewer in Home Assistant and add `garmin.battery_level` as the event to listen to as shown below.
|
||||
|
||||
[](https://my.home-assistant.io/redirect/developer_events/)
|
||||
|
||||
<img src="images/Battery_Event_Screenshot.png" width="600" title="Listening for battery events"/>
|
||||
|
||||
```yaml
|
||||
|
@ -110,9 +110,7 @@ There's an online way of testing the API URL too, thanks to [REQBIN](https://req
|
||||
|
||||
## Watch Battery Level Reporting
|
||||
|
||||
For this you will need to have already got the main application or widget working with a menu in order to prove that the API calls are successful. We have proven this works with both our home brew infrastructure as well as Nabu Casa. Now with a script similar to one of the following two, you should be able to fake the watch API call and verify receipt by Home Assistant in the Event logging by clicking the following button.
|
||||
|
||||
[](https://my.home-assistant.io/redirect/developer_events/)
|
||||
For this you will need to have already got the main application or widget working with a menu in order to prove that the API calls are successful. We have proven this works with both our home brew infrastructure as well as Nabu Casa. Now with a script similar to one of the following two, you should be able to fake the watch API call and verify receipt by Home Assistant in the Event logging as shown in '[Listening for the `device_id`](BatteryReporting.md#listening-for-the-device_id)'.
|
||||
|
||||
#### Battery: Linux, MacOS, UNIX, Cygwin etc
|
||||
|
||||
|
Reference in New Issue
Block a user