Appliance Capabilities via local JSON file - WELLBEING #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried a Wellbeing Appliances (Electrolux Purifier PUREA9) and I noticed that using the integration API, it reports no capabilities for the Purifier (while using the https://api.developer.electrolux.one/api/v1/appliances/{applianceId}/info I can get the Purifier capabilities).
Of course the washing machine and the dryer work as expected.
Despite not reporting the capabilities, the integration API reports the Purifier state via websocket.
So I added the capabilities to put a local JSON file under
appliance_capabilities
folder that can be manually extracted from the Electrolux Web API. It can be extended for any other model.In addiction I modified the
number
entity to check the configuredstep
: if it is1
, we can assume that the number isint
so it will send the command asint
instead of nativefloat
. This is because the Purifier accepts a fan speed between1
to9
and, sending afloat
(e.g.3.0
) generates and error as it expects3
. I think this is valid in general.