Remootio after latest update on HA (22-07-23)

[alpha520098]

Logger: homeassistant.util.package Source: util/package.py:107 First occurred: 7:57:57 AM (3 occurrences) Last logged: 7:58:20 AM

Unable to install package aioremootio @ git+https://github.com/sam43434/aioremootio.git: ERROR: Cannot install aioremootio==1.0.0.dev0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip is available: 23.1.2 -> 23.2 [notice] To update, run: pip install --upgrade pip

[nivek1612]

I have no idea why you had your changes overwritten then. Someone with more knowledge than me might know.

[alpha520098]

Yeah me either, but let's hope that remootio gets the act together

[retreatinstyle]

try doing this, effectively putting the same changes back in as before

Go to your HA /config/custom_components/remootio/

edit manifest.json file and change the line with requirements to look like the below "requirements": ["aioremootio @ git+https://github.com/GITHUBUSERID/aioremootio.git"], but change GITHUBUSERID to yours

edit this file /config/custom_components/remootio/cover.py to make the suggested changes

as shown here 0f1b0c1

restart HA and see if that works. Other than that will need someone with more skills than me

Thank You!!! This fixed it for me perfectly :)

[nivek1612]

2023.10.2 breaks it again

Unable to install package aioremootio @ git+https://github.com/nivek1612/aioremootio.git: ERROR: Cannot install aioremootio==1.0.0.dev0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

[retreatinstyle]

2023.10.2 breaks it again

Unable to install package aioremootio @ git+https://github.com/nivek1612/aioremootio.git: ERROR: Cannot install aioremootio==1.0.0.dev0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Have you followed the instructions above and created a fork? Mine works perfectly with latest update.

[alpha520098]

yeah mines broken, i've also have my own fork - its the version that needs updating?

and @retreatinstyle could you share some insight?

[nivek1612]

2023.10.2 breaks it again Unable to install package aioremootio @ git+https://github.com/nivek1612/aioremootio.git: ERROR: Cannot install aioremootio==1.0.0.dev0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Have you followed the instructions above and created a fork? Mine works perfectly with the latest update.

Yes mine has been fine until the latest update. I have my own fork and followed the instructions

[yarafie]

HA updated dependency aiohttp to 3.8.6 so go into your fork of aioremootio and change aiohttp to 3.8.6 in requirements.txt

[nivek1612]

HA updated dependency aiohttp to 3.8.6 so go into your fork of aioremootio and change aiohttp to 3.8.6 in requirements.txt

yes, that fixes it thanks again.

[yarafie]

ive changed my fork of aioremootio to be semi future proof if minor versioms of dependencied change take a loojk

[alpha520098]

@yarafie i can confirm that worked for me, thanks again for pull all of us out the poo!

[nivek1612]

ive changed my fork of aioremootio to be semi future proof if minor versioms of dependencied change take a loojk

I've mirrored those changes in my fork thanks

[jwinston100]

I have updated my fork's requirements.txt to show aiohttp==3.8.6 and am using

Home Assistant 2023.10.3 Supervisor 2023.10.0 Operating System 11.0

But the Remootio integration doesn't work. I have a notification which reads

Invalid config The following integrations and platforms could not be set up:

remootio (Show logs) Please check your config and logs.

And the log shows

Logger: homeassistant.setup Source: setup.py:185 First occurred: 12:53:40 PM (1 occurrences) Last logged: 12:53:40 PM

Setup failed for custom integration remootio: Requirements for remootio not found: ['aioremootio @ git+https://github.com/jwinston100/aioremootio.git'].

Not sure what is wrong.

[yarafie]

@jwinston100 double check that you updated requirements.txt to correct version of aiohttp

[alpha520098]

@yarafie i've just updated mine and its done the same as @jwinston100

[yarafie]

@alpha520098 and I assume its workinng @jwinston100 im running 10.2 and its working for me

[alpha520098]

there's been another update 10.3 and a operating update

[alpha520098]

@yarafie here's mine:

aiohttp==3.8.6 pycryptodome==3.17 async-class==0.5.0 voluptuous==0.13.1

[yarafie]

I see in 10.3 see below notes

Downgrade aiohttp to 3.8.5 (@frenck - #101913)

Testing the below

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

[yarafie]

@alpha520098 @jwinston100 I changed my requirements.txt to the above.

This should work if HA Changes aiohttp to a higher version. in HA 10.2 they updated to version 3.8.6 in HA 10.3 they downgraded to version 3.8.5

my adjustments to requirements.txt should handle it

[alpha520098]

@yarafie so that i get this right for version 10.3 and the aihttp is: 3.8.5?

[yarafie]

@yarafie so that i get this right for version 10.3 and the aihttp is: 3.8.5?

Yep. Check HA Changelog for 10.3 i pasted it above

[alpha520098]

@yarafie so that i stop being such a pain in the ass, and mate i will buy you a beer one day for all your help

aiohttp>=3.8.5 pycryptodome>=3.17 async-class>=0.5.0, voluptuous>=0.13.1

does that look correct?

[yarafie]

@yarafie so that i stop being such a pain in the ass, and mate i will buy you a beer one day for all your help

aiohttp>=3.8.5 pycryptodome>=3.17 async-class>=0.5.0, voluptuous>=0.13.1

does that look correct?

No guarantees but below should be better

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

[alpha520098]

@yarafie yes i can confirm below works with 10.3 - you sir are a bloody legend!!

aiohttp>=3.8.5 pycryptodome>=3.17 async-class>=0.5.0, voluptuous>=0.13.1

[nivek1612]

Using this approach suggested by @yarafie

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

I can confirm works at 10.2 and 10.3 and will work when they finally go back to aiohttp version 3.8.6

[jwinston100]

Yes, thank you yet again @yarafie. That works!

[nathanbean]

Fresh install here. After following this thread to a T I was finally able to get the integration to start and add my device, a ghost controls gate opener. However I do not have any entities! I have deleted and re-added the integration, tried re-enabling the API socket with new keys, and still nothing. Any suggestions, I am a noob so take it easy on me.

Home Assistant 2023.10.5 Supervisor 2023.10.1 Operating System 7.1 Frontend 20231005.0 - latest

[alpha520098]

To be clear you've forked your own repo?

[alpha520098]

Fresh install here. After following this thread to a T I was finally able to get the integration to start and add my device, a ghost controls gate opener. However I do not have any entities! I have deleted and re-added the integration, tried re-enabling the API socket with new keys, and still nothing. Any suggestions, I am a noob so take it easy on me.

Home Assistant 2023.10.5

Supervisor 2023.10.1

Operating System 7.1

Frontend 20231005.0 - latest

try doing this, effectively putting the same changes back in as before

Go to your HA /config/custom_components/remootio/

edit manifest.json file and change the line with requirements to look like the below "requirements": ["aioremootio @ git+https://github.com/GITHUBUSERID/aioremootio.git"], but change GITHUBUSERID to yours

edit this file /config/custom_components/remootio/cover.py to make the suggested changes

as shown here 0f1b0c1

restart HA and see if that works. Other than that will need someone with more skills than me

So you will have to change a few lines of code at the cover.py

That should fix it this has been a problem prior - let's us know if you get stuck

[nathanbean]

Fresh install here. After following this thread to a T I was finally able to get the integration to start and add my device, a ghost controls gate opener. However I do not have any entities! I have deleted and re-added the integration, tried re-enabling the API socket with new keys, and still nothing. Any suggestions, I am a noob so take it easy on me. Home Assistant 2023.10.5 Supervisor 2023.10.1 Operating System 7.1 Frontend 20231005.0 - latest

try doing this, effectively putting the same changes back in as before

Go to your HA /config/custom_components/remootio/

edit manifest.json file and change the line with requirements to look like the below "requirements": ["aioremootio @ git+https://github.com/GITHUBUSERID/aioremootio.git"], but change GITHUBUSERID to yours

edit this file /config/custom_components/remootio/cover.py to make the suggested changes

as shown here 0f1b0c1

restart HA and see if that works. Other than that will need someone with more skills than me

So you will have to change a few lines of code at the cover.py

That should fix it this has been a problem prior - let's us know if you get stuck

Thanks for the help! So originally, I did fork my own. However being a noob I did not know I had to add it as a custom repositor in HACS. After deleting the OP repository repository and adding my own and making all of the changes listed above, everything works!!! Thanks again!

[alpha520098]

Glad I could help, considering to make a Facebook page for quick help page

[ant415]

I was tempted by the todo lists in the latest version and updated everything.

Core: 2023.11.0 Supervisor: 2023.10.1 Operating System: 11.1 Frontend: 20231030.1

I had this fix running from back in September but haven't been able to get it running again. I updated as per following but hasn't worked.

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

Any more tweaks for the latest updates?

[alpha520098]

Could you explain what is not working? The actual interface with doors or just not integrating?

Did you fork your repo?

[ant415]

Hi, thanks for the reply

There is no error on the remootio integration. The actual interface of the cover is listing it as unavailable.

I was using my original fork of the master ivgg-me/aioremootio. To rule out any updates since then I have deleted my fork and recreated a fresh copy. I updated the "requirements" values, checked the "manifest.json"file in HA has the correct address to my repo still and rebooted HA.

I tried this

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

and this to rule out options

aiohttp>=3.8.5 pycryptodome>=3.17 async-class>=0.5.0, voluptuous>=0.13.1

Still unavailable at this stage.

[alpha520098]

https://github.com/sam43434/remootio/issues/12#issuecomment-1784446373

Follow this to resolve your cover issues- and if you got back up on this thread you can read more about it

[alpha520098]

Fresh install here. After following this thread to a T I was finally able to get the integration to start and add my device, a ghost controls gate opener. However I do not have any entities! I have deleted and re-added the integration, tried re-enabling the API socket with new keys, and still nothing. Any suggestions, I am a noob so take it easy on me. Home Assistant 2023.10.5 Supervisor 2023.10.1 Operating System 7.1 Frontend 20231005.0 - latest try doing this, effectively putting the same changes back in as before

Go to your HA /config/custom_components/remootio/

edit manifest.json file and change the line with requirements to look like the below "requirements": ["aioremootio @ git+https://github.com/GITHUBUSERID/aioremootio.git"], but change GITHUBUSERID to yours

edit this file /config/custom_components/remootio/cover.py to make the suggested changes

as shown here 0f1b0c1

restart HA and see if that works. Other than that will need someone with more skills than me

So you will have to change a few lines of code at the cover.py

That should fix it this has been a problem prior - let's us know if you get stuck

[ant415]

Thankyou, I got it working! For me it was the changes to cover.py that I needed to update (missed that this was now needed).

As a more completed summary of what worked for me to help anyone else:

1.

Followed the instruction per this post - https://github.com/sam43434/remootio/issues/12#issuecomment-1646500225

EXCEPT - The values listed in Step 2 for the requirements.txt are out of date. Both of the below options worked for me. From above posts I gather that Option B is intended to better future proof against changes and is the option I finally went with.

OPTION A: requirements.txt

aiohttp>=3.8.5 pycryptodome>=3.17 async-class>=0.5.0, voluptuous>=0.13.1

OPTION B: requirements.txt

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

2.

Updated the cover.py file as per instructions here - https://github.com/sam43434/remootio/issues/12#issuecomment-1712426072

A couple notes:

• I did NOT need to delete the integration from HA. The cover became available again after making the edits
• I did not need to add my repo as a custom repository in HACS
• Worked for latest version per below

Core: 2023.11.0 Supervisor: 2023.10.1 Operating System: 11.1 Frontend: 20231030.1

[alpha520098]

Gents, I've just created a Facebook group that is here:

https://www.facebook.com/profile.php?id=61553050806894&mibextid=LQQJ4d

When issues come up please feel free to post

[marioalfaro75]

I gave this a go, integration now loads with no errors but the entity still not working.

Logs error:

Log Details (ERROR) Logger: homeassistant.components.cover Source: helpers/entity_platform.py:621 Integration: Cover (documentation, issues) First occurred: 5:37:40 pm (1 occurrences) Last logged: 5:37:40 pm

remootio: Not adding entity with invalid device info: Invalid device info {'manufacturer': 'Assemblabs Ltd', 'name': 'Remootio Device (Host: 192.xxx.xxx.xxx, S/N: xxxxxxxxxxxxxxxxxx)'} for 'remootio' config entry: device info must include at least one of identifiers or connections

Any ideas?

Thankyou, I got it working! For me it was the changes to cover.py that I needed to update (missed that this was now needed).

As a more completed summary of what worked for me to help anyone else:

Followed the instruction per this post - #12 (comment)

EXCEPT - The values listed in Step 2 for the requirements.txt are out of date. Both of the below options worked for me. From above posts I gather that Option B is intended to better future proof against changes and is the option I finally went with.

OPTION A: requirements.txt

aiohttp>=3.8.5 pycryptodome>=3.17 async-class>=0.5.0, voluptuous>=0.13.1

OPTION B: requirements.txt

aiohttp>=3.8.5,==3.8. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

Updated the cover.py file as per instructions here - #12 (comment)

A couple notes:

• I did NOT need to delete the integration from HA. The cover became available again after making the edits
• I did not need to add my repo as a custom repository in HACS
• Worked for latest version per below

Core: 2023.11.0 Supervisor: 2023.10.1 Operating System: 11.1 Frontend: 20231030.1

[alpha520098]

1. So have you forked your repo?

[alpha520098]

@yarafie Hey mate after the lastest update seems that the intergation is broken could you please check it out? I have downgraded my home assistant to get remootio to work again. seems that its a 3.9.1 aiohttp issue - but thats a educated guess

[yarafie]

@yarafie Hey mate after the lastest update seems that the intergation is broken could you please check it out? I have downgraded my home assistant to get remootio to work again. seems that its a 3.9.1 aiohttp issue - but thats a educated guess

Unfortuantly I'm travelling so won't be able to test soon, don't want to break anything while I'm awsy for the family :) If you are game to test just change in ur copy of aioremootio requirements.txt to be aiohttp 3.9.1

aiohttp>=3.8.5,==3.8 to aiohttp>=3.9.0,==3.9.

[jasbuck]

@yarafie Hey mate after the lastest update seems that the intergation is broken could you please check it out? I have downgraded my home assistant to get remootio to work again. seems that its a 3.9.1 aiohttp issue - but thats a educated guess

Unfortuantly I'm travelling so won't be able to test soon, don't want to break anything while I'm awsy for the family :) If you are game to test just change in ur copy of aioremootio requirements.txt to be aiohttp 3.9.1

aiohttp>=3.8.5,==3.8 to aiohttp>=3.9.0,==3.9.

This worked for me. thank you!

[yarafie]

@yarafie Hey mate after the lastest update seems that the intergation is broken could you please check it out? I have downgraded my home assistant to get remootio to work again. seems that its a 3.9.1 aiohttp issue - but thats a educated guess

Unfortuantly I'm travelling so won't be able to test soon, don't want to break anything while I'm awsy for the family :) If you are game to test just change in ur copy of aioremootio requirements.txt to be aiohttp 3.9.1 aiohttp>=3.8.5,==3.8 to aiohttp>=3.9.0,==3.9.

This worked for me. thank you!

Great. I bit the bullet and based on your comment went ahead. I confirm it works by updating to aiohttp 3.9.1

[alpha520098]

I've done something wrong could someone put theres up?

this is mine:

aiohttp>=3.8.1,<3.9.0 pycryptodome>=3.15.0,<3.20.0 async-class==0.5.0 voluptuous>=0.13.1,<0.14.0

[nivek1612]

Change to aiohttp>=3.9.0,==3.9. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

Should fix it. I’m not home to test

[yarafie]

I've done something wrong could someone put theres up?

this is mine:

aiohttp>=3.8.1,<3.9.0 pycryptodome>=3.15.0,<3.20.0 async-class==0.5.0 voluptuous>=0.13.1,<0.14.0

aiohttp>=3.9.1,==3.9. pycryptodome>=3.17 async-class>=0.5.0,==0.5. voluptuous>=0.13.1,==0.13.*

[alpha520098]

just so that i know cut and paste this with or without the astericks?

[nivek1612]

just so that i know cut and paste this with or without the astericks?

With