hi,
An HA developper asks for some use cases on how to use emoncms integration with automation.
dev ← alexandrecuer:emoncms_iqs
opened 07:16AM - 31 Jul 25 UTC
## Breaking change
## Proposed change
Add quality scale.yaml to emoncms
…
## Bronze
- [X] `action-setup` - Exempt : This integration does not provide additional actions.
- [X] `appropriate-polling` - If it's a polling integration, set an appropriate polling interval : https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/coordinator.py#L34
- [X] `brands` - Has branding assets available for the integration : https://github.com/home-assistant/brands/tree/master/core_brands/emoncms
- [X] `common-modules` - Place common patterns in common modules - https://github.com/home-assistant/core/blob/dev/homeassistant/components/emoncms/coordinator.py + only sensors : https://github.com/home-assistant/core/blob/dev/homeassistant/components/emoncms/sensor.py
- [X] `config-flow-test-coverage` - Full test coverage for the config flow : https://github.com/home-assistant/core/blob/dev/tests/components/emoncms/test_config_flow.py
- [X] `config-flow` - Integration needs to be able to be set up via the UI : https://github.com/home-assistant/core/blob/dev/homeassistant/components/emoncms/config_flow.py
- [X] Uses `data_description` to give context to fields
https://github.com/home-assistant/core/pull/149733
- [X] Uses `ConfigEntry.data` and `ConfigEntry.options` correctly
- [X] `dependency-transparency` - Dependency transparency : https://github.com/Open-Building-Management/pyemoncms
- [X] `docs-actions` - Exempt : This integration does not provide additional actions.
- [X] `docs-high-level-description` - The documentation includes a high-level description of the integration brand, product, or service : https://www.home-assistant.io/integrations/emoncms
- [X] `docs-installation-instructions` - The documentation provides step-by-step installation instructions for the integration, including, if needed, prerequisites : https://www.home-assistant.io/integrations/emoncms#configuration
- [X] `docs-removal-instructions` - The documentation provides removal instructions
https://github.com/home-assistant/home-assistant.io/pull/40234
- [X] `entity-event-setup` - Exempt : no events are registered by the integration.
- [X] `entity-unique-id` - Entities have a unique ID : https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/sensor.py#L206 and https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/__init__.py#L40
- [X] `has-entity-name` - Entities use has_entity_name = True : https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/sensor.py#L230
- [X] `runtime-data` - Use ConfigEntry.runtime_data to store runtime data : https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/sensor.py#L204 and https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/__init__.py#L70
- [X] `test-before-configure` - Test a connection in the config flow : https://github.com/home-assistant/core/blob/98e6e20079d96cebeb75089a54f631f166bfd15b/homeassistant/components/emoncms/config_flow.py#L87
- [X] `test-before-setup` - Check during integration initialization if we are able to set it up correctly : https://github.com/home-assistant/core/blob/98e6e20079d96cebeb75089a54f631f166bfd15b/homeassistant/components/emoncms/__init__.py#L69
- [X] `unique-config-entry` - Don't allow the same device or service to be able to be set up twice : https://github.com/home-assistant/core/blob/98e6e20079d96cebeb75089a54f631f166bfd15b/homeassistant/components/emoncms/config_flow.py#L106
## Silver
- [X] `action-exceptions` - Service actions raise exceptions when encountering failures
- [X] `config-entry-unloading` - Support config entry unloading : https://github.com/home-assistant/core/blob/89aa349881e2f406daee627a0014796e5dbf2aea/homeassistant/components/emoncms/__init__.py#L76
- [X] `docs-configuration-parameters` - The documentation describes all integration configuration options : https://github.com/home-assistant/home-assistant.io/pull/40234
- [X] `docs-installation-parameters` - The documentation describes all integration installation parameters : https://www.home-assistant.io/integrations/emoncms#configuration
- [ ] `entity-unavailable` - Mark entity unavailable if appropriate
- [X] `integration-owner` - Has an integration owner : https://github.com/home-assistant/core/blob/dev/homeassistant/components/emoncms/manifest.json
- [X] `log-when-unavailable` - If internet/device/service is unavailable, log once when unavailable and once when back connected : https://github.com/home-assistant/core/blob/614bf96fb9d115b78f494b63590e703216bc1d11/homeassistant/components/emoncms/coordinator.py#L42
- [ ] `parallel-updates` - Number of parallel updates is specified
- [ ] `reauthentication-flow` - Reauthentication needs to be available via the UI
- [X] `test-coverage` - Above 95% test coverage for all integration modules
## Gold
- [ ] `devices` - The integration creates devices
- [ ] `diagnostics` - Implements diagnostics
- [ ] `discovery-update-info` - Integration uses discovery info to update network information
- [ ] `discovery` - Devices can be discovered
- [X] `docs-data-update` - The documentation describes how data is updated : https://github.com/home-assistant/home-assistant.io/pull/40234
- [ ] `docs-examples` - Exempt : this integration does not provide any automation
- [ ] `docs-known-limitations` - The documentation describes known limitations of the integration (not to be confused with bugs)
- [ ] `docs-supported-devices` - The documentation describes known supported / unsupported devices
- [ ] `docs-supported-functions` - The documentation describes the supported functionality, including entities, and platforms
- [X] `docs-troubleshooting` - The documentation provides troubleshooting information : https://github.com/home-assistant/home-assistant.io/pull/40234
- [ ] `docs-use-cases` - The documentation describes use cases to illustrate how this integration can be used
- [ ] `dynamic-devices` - Devices added after integration setup
- [ ] `entity-category` - Entities are assigned an appropriate EntityCategory
- [X] `entity-device-class` - Entities use device classes where possible : https://github.com/home-assistant/core/blob/ad3174f6e689b93e93d96a1d85b19faa3b4f317f/homeassistant/components/emoncms/sensor.py#L44
- [ ] `entity-disabled-by-default` - Integration disables less popular (or noisy) entities
- [X] `entity-translations` - Entities have translated names : https://github.com/home-assistant/core/blob/ad3174f6e689b93e93d96a1d85b19faa3b4f317f/homeassistant/components/emoncms/strings.json#L52
- [ ] `exception-translations` - Exception messages are translatable
- [ ] `icon-translations` - Entities implement icon translations
- [X] `reconfiguration-flow` - Integrations should have a reconfigure flow : https://github.com/home-assistant/core/blob/ca290ee6313209d0f0be89a6a053c6fe54873631/homeassistant/components/emoncms/config_flow.py#L182
- [ ] `repair-issues` - Repair issues and repair flows are used when user intervention is needed
- [ ] `stale-devices` - Stale devices are removed
## Platinum
- [X] `async-dependency` - Dependency is async
- [X] `inject-websession` - The integration dependency supports passing in a websession : https://github.com/home-assistant/core/blob/ca290ee6313209d0f0be89a6a053c6fe54873631/homeassistant/components/emoncms/__init__.py#L65
- [ ] `strict-typing` - Strict typing
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [X] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [X] The code change is tested and works locally.
- [X] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] I have followed the [perfect PR recommendations][perfect-pr]
- [X] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [X] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
The goal is to improve the doc in order to give people an example idea of what they can do with this integration. What would someone use this for? How do you use it in automations?
Could you some of you illustrate their usage ? or do you only use the integration for the energy dashboard ? which was last year reported as the main reason for the update : cf EmonCMS Integration · Open-Building-Management/emoncms · Discussion #23 · GitHub
best
Alex
borpin
29 September 2025 15:29
2
You wouldn’t directly, but you might trigger an automation based on a sensor value. So when Temp x is > y then…
It is producing sensor state data so the answer is anything you can do with any other (numeric) state sensor.