Replies: 1 comment
-
OK, worked out that the sensors that are not being discovered have the same name under different headings, EG Fridge{doorState} and Freezer{doorState} so an additional modification is required to specify the full parameter, EG fridge/doorState. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm very grateful this integration has been reborn. I have had my Electrolux fridge discovered which has several switches and controls however previously I have some nice temperature controls and a door open/closed alert.
I can see from the logging if the API get appliance data contains multiple values it won't be added as an entity (Exception is the network interface link quality.
Example logging line below has no discovered entities
"iceMaker": {"alerts": [], "iceDispenserState": 0, "iceTrayWaterFillSetting": 1, "evaporatorFanState": 1, "defrostTemperatureC": -12.4, "applianceState": "RUNNING", "defrostTemperatureF": 9.68},
Example below is discovered and added as a sensor
"waterFilterState": "GOOD",
Example below is the only instance of a line with multiple data items that works. EG linkqualityindicator
"networkInterface": {"swVersion": "v5.4.2", "otaState": "IDLE", "niuSwUpdateCurrentDescription": "xxxxx", "swAncAndRevision": "xxxxx", DIAGNOSTIC "linkQualityIndicator": "VERY_GOOD"},
Just wondering if this is something easy to fix/add to the integration to allow those additional sensor/switches to be discovered. I'm struggling to work this out how it all fits together.
Beta Was this translation helpful? Give feedback.
All reactions