Closed Tomcraft1980 closed 3 weeks ago
Looking through that log file...
tasks
property as optional.tasks
property. Again that is likely to be because you haven't added a schedule.tasks
the plugin is not accepting the API /api/v1/appliances/${this.applianceId}/state
responses. This prevents those accessories from completing their initialisation.displayName
has got set to a blank string for the two newly added robots. I suspect that this is because the name has not yet propagated to the robots and back to the /api/v1/appliances/${this.applianceId}/state
response; this does seem to be quite slow.tasks
property in the API responses.So, it looks like there are three issues, all related to the /api/v1/appliances/${this.applianceId}/state
response:
tasks
property is not present in the response. I need to treat it as being optional rather than always present.applianceName
can be blank, even when set correctly in the /api/v1/appliances
response. Switching to the value from the /api/v1/appliances
response is probably the best approach, perhaps with a fallback to generating a name from the applianceType
and applianceId
.
- Immediately after an appliance has been added its full details are not available via the API. I do not intend to do anything about this.
Agree!
- If no schedule has been configured then the
tasks
property is not present in the response. I need to treat it as being optional rather than always present.
This would be nice, since I do not use the tasks in den AEG app. Ich have fully automated the robots to only clean when we leave the home.
- The
applianceName
can be blank, even when set correctly in the/api/v1/appliances
response. Switching to the value from the/api/v1/appliances
response is probably the best approach, perhaps with a fallback to generating a name from theapplianceType
andapplianceId
.
Awesome! Thanks in advance for geting into this.
Try v2.2.3.
Fixed! Thanks so much!
Good to hear it is working again now.
This would be so much easier if Electrolux actually documented how different appliances implemented the API... or even just provided examples of the responses from different appliances.
I have used many third-party APIs in various homebridge plugins, and the Electrolux one is by far the worst in almost every way. The new documentation barely says anything that wasn't obvious from reverse engineering the previous app API, the functionality is incredibly limited, the rate limits are some of the strictest that I have dealt with (and without any event mechanism to mitigate the need for polling), the OAuth implementation is broken in several ways (e.g. refresh tokens themselves being refreshed and immediately invalidated, so if there is an error it needs to be manually recovered), etc.
Let's hope they fix this. Would propably be a good idea to let them know your difficulties. ;-) devportal @ electrolux . com
Description of Issue
I had connection problems with one of my robots as you noted in #53, so I deleted that robot and the one added after that one (as the AEG app is not able to sort the robots individually, they are added in the order you add them to the app) and readded them successfully to the app and named them like before, like so:
They were not added to the devices section until now. Because of the issues with the checkboxes (#54) I did some testing yesterday downgrading homebridge DEB package, trying your plugin version 2.0.0 again and finally completely uninstalled the plugin, reinstalled it and inserted a new access & refresh token. My first robot (AEG RX9-1-IBM) was added to the homebridge and HomeKit devices again, but the newer 9.2 models are missing.
Plugin Version
2.2.0
AEG/Electrolux Appliance(s)
AEG RX9-1-IBM 900 277 268, AEG RX9-2-4-ANM 900 277 479, AEG RX9-2-6-IBM 900 277 480
HomeKit App(s)
No response
Diagnostic Checks
Log File