Actions: JMcCumberIO/flashforge_adventurer5m
Actions
Showing runs from all workflows
173 workflow runs
173 workflow runs
services.yaml use precise
and robust syntax, particularly for selectors (e.g., text: {},
boolean: {}, number: {mode: box}).
This was identified as a potential root cause for UI fields not
rendering correctly for some services (like toggle_light) and
potentially contributing to "unknown error" messages for other services
if their parameters were not being correctly presented or submitted
by the UI.
This commit standardizes the definitions for all services with parameters
to improve UI compatibility and reliability of service calls.
Tests
#109:
Pull request #61
opened
by
JMcCumberIO
toggle_light service was not showing its state field in the UI,
leading to "required key not provided" errors.
This commit meticulously corrects the toggle_light service definition
in services.yaml. The primary change is ensuring the boolean selector
for the state field is formatted as boolean: {}, which is a more
robust and precise way to define an empty mapping for the selector.
This change should allow Home Assistant's UI to correctly parse the
service definition and render the necessary input field for the 'state'
parameter, resolving the issue where the field was not appearing and
thus the required data was not being sent.
Tests
#107:
Pull request #59
opened
by
JMcCumberIO
SPEED_MILLIMETERS_PER_SECOND and
CONCENTRATION_MICROGRAMS_PER_CUBIC_METER constants
from homeassistant.const to string literals ('mm/s' and 'µg/m³')
in sensor.py.
This addresses an ImportError that occurs when the custom
component is run on Home Assistant core versions older than
2022.11 (for speed unit) and 2022.4 (for concentration unit),
where these specific constants are not yet available.
This change ensures broader compatibility of the integration.
Tests
#105:
Pull request #57
opened
by
JMcCumberIO