109.4 update causes wiserheatingapi to get deleted

[scooper1]

wiser api still being deleted and needing reinstall after update to 109.4
this is still happening after the comma fix

[asantaga]

I have no idea.. It works perfectly on my instance and Adam on https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/117 says it now works fine (after the comma fix)...

I'll create a clean virtual environment and test it out tomorrow... So from memory, you need to log using portainer (so your using docker) and manually pip install the library right?

[scooper1]

yes normal docker install
i have send this behaviour both machines I have access to
no other libraries (not checked that there are libraries) that are installed via hacs have this problems - i don't know how libraries are handled during a update but really would not expect them to get deleted unless the complete docker image is being replaced ?

[msp1974]

Not seeing either. Just updated to 109.4 and all was fine.

[chris-github1975]

I have the latest HA, HACS, and Wiser and have no errors. I'm running it all on a VMware guest. Chris

…

________________________________ From: Mark Parker <notifications@github.com> Sent: Thursday, May 7, 2020 12:06:07 AM To: asantaga/wiserHomeAssistantPlatform <wiserHomeAssistantPlatform@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [asantaga/wiserHomeAssistantPlatform] 109.4 update (#105) Not seeing either. Just updated to 109.4 and all was fine. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOIHQAQNUH72I6ID62TVCMTRQHUN7ANCNFSM4M2SA6YQ>.

[scooper1]

Maybe just a interaction on my systems
Any idea what would cause library to get deleted during a supervisor update ?

[asantaga]

I have no idea.,. Im assuming your using the official (if it thats what we call it) home assistant docker image from docker hub right?

If so then perhaps delete the container, any assigned volumes and then recreate the container.. That said when u upgrade the container would be blitzed anyway..

[scooper1]

yes using official image
I accept that problem is something strange on my systems
just trying to understand how it happens to be able to fix it
just happened again on 109.5 update

[asantaga]

lets sync up again in a couple of days, happy to hold a zoom with you and help debug this.. im very curious to why this is happening..

[scooper1]

Ok I would be up for that.
Normally use discord but I try to get zoom account
Thanks

[scooper1]

I think my hacs install might be a bit corrupted around wiser component as yesterday it was giving a title with no spaces between words (ok now) and i think today the readme.md is not showing as formatted texted instead in gives a raw link

is the anyway to rebuild the hacs database without - might try deleting the wiser component and re-installing

should the config\deps folder contain a copy of the wiserheatingapi or a link
mine is empty
documentation implies that this contains a copy of any dependencies required after docker container restart - this may just be out of date info

[msp1974]

Only thing i can think of worth looking at is

https://community.home-assistant.io/t/ha-0-103-0-update-broke-hacs-requirements-for-hacs-not-found-aiofiles-0-4-0/154896/9

I don't know if your other HACs integrations need to download any dependancies.

Other people on various similar issues have suggested taking a snapshot, delete and reinstall docker env and then restore shapshot. Never done this so dont know how much it does or does not keep...on you!

[asantaga]

Hey @scooper1 , I have a zoom account, so zoom isnt a problem..

Not sure you need to create a snapshot of the docker env. If you configured it correctly all your config is mapped to a volume on your filesystem.. (ie the -v flag)

You should be able to delete the docker container, delete the image (just in case) and then recreate the container.. thats the beauty of docker

[asantaga]

oh, and yeah I would definitively also delete the wiser directory in custom_components

[scooper1]

the docker container appears to be recreated on each upgrade
it appears to me that hacs does a scan of the manifest files and reinstalls the requirements
but on my system the it misses the wiserheatingapi
so I have deleted the wiser custom components and then reinstalled via hacs then done the 109.6 upgrade that deletes the hassioassistant container and recreates it
still same problem I had to pull wiserheatingapi manually

[asantaga]

Sorry bank holiday got me..

i have no clue..

Can we try one more thing..

Can you create a "NEW" HA container, pointing to a new config directory, ie a different -v mapping..

Lets see if it happens there too, if it works then there is something with the HA config we need de-debug,.

[scooper1]

I am not sure how to do a new container
but turn on debugging for hacs
uninstall wiser restarted and then installed wiser restarted
at no point did I get any debug messages about installing the wiserheatingapi
tried a few other like breaking changes - still did not see any checking for requirements
thinking that my hacs is broken from the data I have in the config directory

[asantaga]

Hey, let me know when we can do a zoom and I'll have a nose.. I do think somethings wrong with HA but worth being sure. Ping me an email , see any of the files, and we'll sort this out offline

[scooper1]

the problem maybe because I have a growing ha system and its tripped this problem
on update
https://community.home-assistant.io/t/ha-0-103-0-update-broke-hacs-requirements-for-hacs-not-found-aiofiles-0-4-0/154896

[scooper1]

cant find a private email account
I set up a temporary test user that you should be able to see my ha server via duckdns address - but I only want to send login details to private email address - not this public platform

[scooper1]

this problem seems to fixed in 1.10b0
beta installed without needing to pull wiserheatingapi
did notice some new log entries
2020-05-14 01:56:07 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify WiserSwitch to extend SwitchEntity
2020-05-14 01:56:07 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify WiserSmartPlug to extend SwitchEntity
2020-05-14 01:56:07 WARNING (MainThread) [homeassistant.components.climate] ClimateDevice is deprecated, modify WiserRoom to extend ClimateEntity

[msp1974]

Have been made aware of this on my jag integration. However, these new entity types are only available in v0.110 onwards which seems a little premature to give depreciation warnings in the logs. We will need to work out how we deploy these changes as people who have not upgraded to v0.110 will not be able to use it.

[msp1974]

Probably a good reason to get this into the main repo which we keep stopping Angelo doing with requests for fixes/upgrades. Me included! ;-)

[asantaga]

Joy!!!

0.110 is due out may 20, i'll wait till then , then fix the warnings

[asantaga]

closing this one, opening new issue