aeg_my_washer_doorlock sensor values are reversed

[teddoshop]

The sensor aeg_my_washer_doorlock shows locked when the door is unlocked and the other way around.
I'm using a AEG 7000 Series washing machine.

[kingy444]

have you used the integration in v1 or only recently installed ?

Essentially is this a migration issue, or specific to your device. Could you provide the diagnostics file too please

[simllll]

I see it too, i use the latest version (2.0.5), furthermore the door state sensor does not work at all. It's always "Off/Closed".

electrolux_status-01JB06RPG67FSSJZCYJR6CEJEW-Waschmaschine-04791a8940c3474632bf9b775ef9c5b9.json

[kingy444]

Looks like the state mapping had open/closed back to front on some of the items.

I believe i've fixed both the issues in the PR submitted.

Can you confirm if the door state is open or closed in the provided json ?

[simllll]

Right now the door is actually opened, seems like it is not reported correclty even here.

One other entity I could use insteda is

but somehow this doesn't show up in the frontend?

[simllll]

Another thing, looking at the values.. time to end is "-1" .. but in the frontend it's "0.0"?

[kingy444]

Another thing, looking at the values.. time to end is "-1" .. but in the frontend it's "0.0"?

That's an intentional coding. That's not an issue 😄

[kingy444]

Right now the door is actually opened, seems like it is not reported correclty even here.

One other entity I could use insteda is

but somehow this doesn't show up in the frontend?

This should be data live queried from the api so that one's weird - could you enable debug logging and provide some logs too

Open and close the door (and let me know which state it was in first/second

Re appliance state - double check the entity isn't just disabled by default

[simllll]

I got the "issue", if the washing maschine is off, it doesn't update the states. Even though it's connected.
"Unfortunately" it turns off automatically when it's done, and therefore I do not get updates when the door is opened.

Any idea how I could workaround this? Just turn it on every few minutes or is there any way to "update" it forcefully? :p

[simllll]

Re appliance state - double check the entity isn't just disabled by default

Looked for everything, also in the developer tools, can't find it.
Edit: maybe it's "appliance mode", I'm checking.. :-)
Edit 2: Okay, it's not :(

[kingy444]

I got the "issue", if the washing maschine is off, it doesn't update the states. Even though it's connected.

"Unfortunately" it turns off automatically when it's done, and therefore I do not get updates when the door is opened.

Any idea how I could workaround this? Just turn it on every few minutes or is there any way to "update" it forcefully? :p

I think this one might be fixed with a forced update that albinator added

But... it's probably a good idea we add a method for you to do that at will (then you can just call the home assistant service.update in an automation to solve the issue

[simllll]

Okay the "API" itself is fine, I checked with the api calls directly.

It updates even if the washing maschine is off (some seconds delay, but good enough :-)).

So is this the "forced update" you are talking? How often is the api queried? Or is there some kind of socket for updates?I only found this so far and was playing aorund with it https://developer.electrolux.one/documentation/reference#getApplianceState

[kingy444]

Yea the state changes are pushed for most things immediately (like opening a door). But the api doesn't push them when say the oven reaches 0

So I suspect this is the same issue, in that Electrolux doesn't trigger the push of the data to HA

We need to query for it manually

[simllll]

Okay got it, thanks for the explanation. One funny side effect: If I query the API via the getApplicaneState manually, it seems it gets reflected in HA too ... maybe the "push" is triggered then somehow :).

So best way for me would be some sort of action that forcefully updates the values. Then I just call it every 60 second, till my desired state is reached 👍

[kingy444]

Honestly - the api calls are pretty horrible outside the developer portal 😂

I won't be able to look at it tomorrow. But I don't think adding an update method would be difficult (have done similar for other integrations), then you can just use an automation

[simllll]

Honestly - the api calls are pretty horrible outside the developer portal 😂

I won't be able to look at it tomorrow. But I don't think adding an update method would be difficult (have done similar for other integrations), then you can just use an automation

Nice, thanks a lot. Just let me know when I can send you a coffee ;-)

Edit: Somehow it seems the values are reported correctly now, I didn't change anything.. but right now it works.. strange

[teddoshop]

@kingy444 I believe you already reproduced the issue right? Or do you still need more information from me? :)

[kingy444]

unsure @teddoshop - ideally if you can open the door and provide a diagnostics file - then close the door and do the same i can confirm the issue for you

@simllll - I checked and looks like we are all good here already. I dont think you should actually have to do anything but because of the mappinbg issue its not working for you atm. @albaintor added code for deferred updates on timeToEnd so assuming that is a trigger here for you then it should just work.

If you dont want to wait for the next version bump for that to work for you (as it needs my PR too) you can (in the mean time ) run the below or just chuck into an automation.

action: homeassistant.update_entity
data:
  entity_id:
    - binary_sensor.aeg_oven_doorstate