aranet devices have gone offline after upgrade to 2024.4.3

[Viss]

The problem

all 3 of my aranet home devices have gone offline since installing the update to 2024.4.3. I attempted to remove and readd one to see if that would fix the issue, but I am given an error complaining the aranet "has to be at least verison 1.2.0, however all three are currently at the newest possible firmware, 1.4.14

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.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

aranet

Link to integration documentation on our website

https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+aranet%22

Diagnostics information

the log is 30.5 meg, i had to zip it
aranet-debug-log.zip

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I glanced at the logs and saw a bunch of python nonetype errors pertaining to mac addresses in the aranet module, so I'm estimating whatever the new changes that went in are, they had some effect on this module. I saw something was merged in ~5 days ago, I'm willing to bet it was that.

Additional information

No response

[home-assistant]

Hey there @aschmitz, @thecode, mind taking a look at this issue as it has been labeled with an integration (aranet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of aranet 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 aranet 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)}}

---

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

[mawek]

i have exactly same issue

[gawdzilla-dev]

I was experiencing the same issue after upgrading to 2024.4.3. I just rolled back to 2024.4.1, and the aranet integration started working again.

[finfinack]

Same issue here. To debug, I tried removing the aranet device and re-adding it. When trying to re-add, it does show up (i.e. it's visible to the Bluetooth dongle) but then then fails with This device is using outdated firmware. Please update it to at least v1.2.0 and try again. despite being on the latest firmware.

This error message is coming from here and my assumption is that a bump in the aranet client causes this. The version was indeed bumped recently from 2.2.2 to 2.3.3.

There were a bunch of changes going into the library and I'm familiar with neither the library nor the HA integration so I'm just hoping to provide some starting points here.

Last but not least, maybe it's related to this recently opened issue in the aranet library.

[thecode]

Hi,
Can you manually downgrade aranet4 and confirm if it fixes the issue?
If you can shell into home assistant container you can use:

sed -i 's/aranet4==2.3.3/aranet4==2.2.2/g' /usr/src/homeassistant/homeassistant/components/aranet/manifest.json

Restart core after this to apply the changes.

To validate your changes are in place (run inside the container):

cat /usr/src/homeassistant/homeassistant/components/aranet/manifest.json | grep aranet4
pip show aranet4

For now we need to wait for upstream to fix the issue, for me downgrading to 2.2.2 bring back the issue fixed in #115298

Thanks

[finfinack]

Thank you Shay. I went through the steps you mentioned and I can confirm going back to aranet library v2.2.2 brings the connectivity back. I was both able to re-add the device I removed before and the other devices I haven't removed started to show readings again too.

I understand you can't downgrade to 2.2.2 generally. Hope upstream will soon fix this though :) It might be worth confirming if this is the issue they describe in Anrijs/Aranet4-Python#42 because if not, upstream doesn't even know about it yet I suspect.

Thank you!

[derobert]

I can also confirm downgrading to 4.2.2 with your steps fixes the issue (HA OS, x86-64 VM).

[Anrijs]

I'm unable to reproduce this on my end. Can you run aranetctl --scan using v2.3.3?

Edit: running this on windows gave me an error, that might be related to this.

[finfinack]

Interestingly enough, I didn‘t get an error (with v2.3.3) and it correctly discovered the devices I have.

Also worth noting that for me the error only occurred after the discovery, i.e. in the onboarding flow of HA after clicking on the device HA (not the aranet integration) already discovered.

[Viss]

How would i edit that manifest json if im on hassos on a raspi? i dont seem to have the ability to find it from within home assistant

[Anrijs]

I might have found the issue, but someone will need to check if fix works.
Try upgrading aranet4 to aranet4==2.3.4b1

[Viss]

its been over a month and this is still broken, despite two home assistant major updates since. Is there something we can do to get the devs attention for this one?

[thecode]

its been over a month and this is still broken, despite two home assistant major updates since. Is there something we can do to get the devs attention for this one?

The developer of the upstream library is still waiting for someone to confirm the fix:
#115602 (comment)

Method is explained here (but use 2.3.4b1 instead of 2.2.2:
#115602 (comment)

sed -i 's/aranet4==2.3.3/aranet4==2.3.4b1/g' /usr/src/homeassistant/homeassistant/components/aranet/manifest.json

When someone confirm it fixes the issue we can release a new package.

[Viss]

I was able to do the fix in the issue that referenced this one. i didnt know you could just ssh into HA and run a docker command to drop into a shell inside the actual HA container - thats SUPER HANDY. I did that, updated the libarary as instructed, bounced HA core and they all came back to life. super easy.

[nikbi7]

@Anrijs I can confirm that 2.3.4b1 and 2.2.2 work for me in Hassio, but the current 2.3.3 does not.