-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
break-out after upgrade #15
Comments
@felisida : thanks for reporting - it seems the climates do have a different status name - i tried to fix this now. Please NoticeI think this will effect everyone who had the integration activated before: I changed the way how the entities are numbered and identified - so we can have multible sensors from a single device. Due to this the old entities are no longer available (thats why home-assistant will show them with the red exclamation mark). How to fix this:To get a fresh start with the integration do the following:
if you have renamed the vimar entities in home-assistant you will need to set the name again. |
Thanks a lot, |
2020-07-29 15:21:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hpprinter which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. |
Meh.. I really thought that non unique id issue has been resolved .. |
I'm sorry, I don't know what happened, because when I only putted the new folder in custom_component, I saw all the sensors, but after following the steps you recommended, it no longer loaded them. if you need any other information ask me. |
@felisida : i just pushed another version with some more debug code. please try again. maybe we find something |
@felisida in regards of that other message in the log above
not sure where your hass installation is running, but maybe have a look here, if this error persists: |
thanks a lot for your tip, at the moment I'm using HA from my iMac, I will study this error |
Hi, |
according to the log, the integration only gets those two sensors - but each of them 10 times : |
no way, |
It does see all the sensors.. |
Great job!!!!!!! this stringiest is due tu your componente? |
Finally! Great! This error seems from upnp integration |
ah ok I know I have some trouble with this component. |
hi,
this morning I upgraded your component, and I confirm that energy guard are working,
but now:
I'm attaching some screenshot and the logs
LOGS.docx
The text was updated successfully, but these errors were encountered: