search

jheling / freeathome

Free@Home component for Home Assistant
103 stars 37 forks source link

Integration stopped working with HA 2022.7.0 #130

Closed bezibaerchen closed 1 year ago

bezibaerchen commented 1 year ago

I read about changes in Python.

Status as of now: "Failed to set up: Import error

bezibaerchen commented 1 year ago

Workaround still working though, just confirmed here

RichardvanGestel commented 1 year ago

Workaround still working though, just confirmed here

I thought that was a bit complicated.. and wasn't sure it would work for me.. This afternoon I just sat down... and miraculously, it works! Thanks!

derjoerg commented 1 year ago

Workaround with 2022.8.1 still working

SuperMaximus1984 commented 1 year ago

5. apk add libsodium

Could you please help with the error I get after fully following your guide? `Logger: homeassistant.components.shell_command Source: /usr/src/homeassistant/homeassistant/components/shell_command/init.py:115 Integration: Shell Command (documentation, issues) First occurred: 18:49:42 (1 occurrences) Last logged: 18:49:42

Error running command: /usr/share/hassio/homeassistant/custom_components/freeathome/scripts/fah_requirements.sh, return code: 127 NoneType: None`

My full path is mentioned above, though I tried only pointing to config path. No matter what it doesn't run within HA startup. Tired of installing libsodiummanually via docker everytime after updates.

jeroen84 commented 1 year ago

All, I've look at the two options: https://github.com/jheling/freeathome/issues/130#issuecomment-1197912093

Option 2 is very complex and not sustainable as it requires - next to time to develop and test - significant future maintenance. Option 1 should be considered to make this integration future proof.

I've made a first try, but this is not working yet. It cannot do a successful key exchange, perhaps because pynacl lacks an important libsodium function crypto_onetimeauth. If anybody has time to investigate and would like to contribute: https://github.com/jeroen84/freeathome/tree/move-pynacl

A third option we could consider is moving to the REST API. I notice that this option was considered ~2 years ago in https://github.com/jheling/freeathome/issues/80

There were limitations of the API back then. Perhaps there are developments in due course that makes this option feasible?

jeroen84 commented 1 year ago

I have just pushed a PR for replacing libnacl with pynacl. This should fix the issue structurally. Please test on your setup: https://github.com/jheling/freeathome/pull/134

RichardvanGestel commented 1 year ago

I have just pushed a PR for replacing libnacl with pynacl. This should fix the issue structurally. Please test on your setup: #134

It works fine here! Well done! I'm running HA on intel nuc

NeoBlack commented 1 year ago

Super that it is fixed, when can we expect a new release? Just ask; no pressure :)

theuzzy commented 1 year ago

Real nice guys! this works like a charm! Update HA 2022.8.2 -> 2022.8.5

Tho85 commented 1 year ago

Super that it is fixed, when can we expect a new release? Just ask; no pressure :)

We do not currently use GitHub releases for this custom component.

Do you use HACS? I'm not an HACS user myself, but you should be able to update the component there somewhere.

NeoBlack commented 1 year ago

Thx, I will try that. I am very new to HomeAssistant and HACS. I don't know anything about the internal release process. I will give it a try in the evening.

fotiDim commented 1 year ago

I updated using HACS just fine. It updates to the latest commit.

AStenzel commented 1 year ago

I have just pushed a PR for replacing libnacl with pynacl. This should fix the issue structurally. Please test on your setup: https://github.com/jheling/freeathome/pull/134

Works for me too! Good job and thanks to all contributors!