Target Closure Sensor shows "unknown" when using local API

[reib3n]

The problem

Hello guys, when I switched from cloud API to local API it seemed that the target closure sensor stopped working. The state is now always "unknown" for my to shutters of somfy.

Please let me know when I can provide additional information.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

core-2024.4.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @imicknl, @vlebourl, @tetienne, @nyrodev, @tronix117, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `overkiz` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign overkiz` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

overkiz documentation overkiz source _{^{(message by IssueLinks)}}

[iMicknl]

Can you please add your diagnostics?

1. If your device already shows up in Home Assistant, go to your integrations page and select Overkiz, your hub and the device. Press the 3 dots and select "Download diagnostics. Otherwise, go to your integrations page and select Overkiz. Next to your hub, click the 3 dots and select "Download diagnostics".

2. Attach your diagnostics (JSON file) to this issue by uploading the file in a new comment (drag and drop supported).

[reib3n]

Here is the diagnostic file. Thanks for your help!

overkiz-01fb275b2c7694368e7aecaa12873710-Büro-ed73ef211fa19201327851ec6134b8dc.json

[Balou47110]

Bonjour, J'ai le même problème depuis la dernière mise à jour... Mes automatismes fonctionne donc 1 fois sur 2. Mes volets roulants somfy sont souvent indisponible ou Inconnu... Avez vous des pistes concernant ce problème ? Merci

[reib3n]

Hey, any news on this?

Can I help or provide something for you?

[iMicknl]

@reib3n are you sure your diagnostics were provided when the value was 'unknown'?

Looking at the states for your io:RollerShutterUnoIOComponent, a value is provided in the diagnostics and should be provided in HA as well..

{
              "type": 1,
              "name": "core:TargetClosureState",
              "value": 100
            }

[reib3n]

@iMicknl, sorry for the late reply. Busy holiday times right now.

Ok, I tested a bit and found a bit different behavior then initial.

It seems the Target Closure behaves like this:

startTestcycle:

Shutter is closed but the cover entity still shows its going down: Target Value is 100% Shutter is closed and I click on the entity stop button: Target Value is 124%

Shutter is opening and entity is showing that it is opening: Target Value is all the time 124% Shutter is opened and entity is showing that it is opening: Target Value is UNKNOWN Shutter is opened and I clicked on the entity stop button: Target Value is 124%

Shutter is closing and entity is showing that it is closing: Target Value is all the time 124%

GOTO startTestcycle

I add again the diagnosis. maybe you can see my tests right there overkiz-01fb275b2c7694368e7aecaa12873710-Büro-ed73ef211fa19201327851ec6134b8dc.json

[memberxx]

@iMicknl

Hi, I got a similar issue. For a terrace roof and a zip screen the Overkiz target position is working, EXCEPT for 0% position. It is showing undefined for 0% position for both covers. everything 1-100% is working fine for me:

[memberxx]

Will there be any solution for this issue? not a DEV but guess it should be a small fix to send 0% instead of NaN

[iMicknl]

@memberxx yes, but at the moment there are 35 open issues and I don't have a lot of time. No ETA when this will be fixed.

[reib3n]

@memberxx yes, but at the moment there are 35 open issues and I don't have a lot of time. No ETA when this will be fixed.

Ok thats good to know ;-)

Will there be any solution for this issue? not a DEV but guess it should be a small fix to send 0% instead of NaN

But for me there seems to be a lot 124% false values to. Is it the some you see too?

[iMicknl]

The 124% false values are caused by your Uno hardware. I would need to dig into this, but I have seen this in the past related to Uno devices.. If I am not mistaken, Uno devices are RTS devices where the hub is keeping state. When the hub doesn't know the current state, it can output a value over 100%.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[memberxx]

Any chance to fix this unknown issue for 0% or any workaround to have n/a be read as 0%?

[iMicknl]

Yes, but at the moment I don't have time to work on this unfortunately. We will leave this issue open for another maintainer, but due to the amount of open issues, I don't expect a quick fix.