mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-09 18:36:51 +00:00
Get Ohme to gold quality (#37983)
* Add use cases, examples, troubleshooting, data updates and known limitation to ohme * Review comments * Linting
This commit is contained in:
parent
917b40f649
commit
acc95b1f2d
@ -143,6 +143,58 @@ The `ohme.set_price_cap` action is used to set the price cap threshold. This can
|
||||
| `config_entry` | No | The config entry of the account to apply the price cap to. |
|
||||
| `price_cap` | No | Threshold in 1/100ths of your local currency. |
|
||||
|
||||
|
||||
## Use cases
|
||||
|
||||
This integration enables several use cases to optimise efficiency of a solar and/or battery storage system.
|
||||
|
||||
### Solar charging
|
||||
Use the charger mode to maximize solar consumption:
|
||||
- Set the charger to "Paused" when solar production is low
|
||||
- Switch to "Max charge" during peak solar hours
|
||||
|
||||
### Battery storage
|
||||
If you have a home battery system:
|
||||
- Charge your EV when the battery is above certain capacity
|
||||
- Pause EV charging when the battery needs replenishing
|
||||
|
||||
## Examples
|
||||
|
||||
### Send a notification on status change
|
||||
|
||||
To be notified when the status of the charger changes, for example when a vehicle is plugged in, you can use an automation.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
# Example automation
|
||||
triggers:
|
||||
- trigger: state
|
||||
entity_id:
|
||||
- sensor.ohme_home_pro_status
|
||||
from: unplugged
|
||||
actions:
|
||||
- action: notify.mobile_app_iphone
|
||||
data:
|
||||
message: "Vehicle plugged in"
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Entities are shown as unavailable
|
||||
You may need to power cycle your charger. Please see the [manufactuer's guidance](https://ohme-ev.com/support/my-charger-is-offline/) for the procedure.
|
||||
|
||||
## Data updates
|
||||
|
||||
This integration fetches data every 30 seconds with the following exceptions:
|
||||
- CT readings are fetched every minute.
|
||||
- Device settings are fetched every 30 minutes.
|
||||
|
||||
## Known limitations
|
||||
|
||||
The integration does not provide the ability to manage vehicles or routines, which can instead be managed on the manufacturer's app.
|
||||
|
||||
## Removing the integration
|
||||
|
||||
This integration follows standard integration removal. No extra steps are required.
|
||||
|
Loading…
x
Reference in New Issue
Block a user