Closed sanderdw closed 4 years ago
Also, on which HA version are you testing the new plugwise-beta versions?
Home Assistant 0.109.6 plugwise-beta version 0.2.4rc1 v0.2.5 - Working
plugwise-beta version 0.2.7rc0 v0.2.4 - Not working v0.2.5 - Not working v0.2.6 - Not working v0.2.7 - Not working
Thanks. Looks like the plugwise-beta-code could be the reason. Are you still seeing the "timed out" errors in the log?
You write: Smile is connected to LAN. Via WiFi or via an UTP-cable? How is you Pi connected to the LAN, and your production-server? All via UTP-cables?
Yes everything is connected with UTP only.
I remember i got timeout error's but didn't test this with an specific version. So if you want me to test this let me know.
Lets diff versions
(just ranting out loud) It sort of makes sense that they become unavailable - as per the upstream review we had to change to ConfigEntryNotReady (instead of PlatformNotReady) together with DUC (DataUpdateCoordinator) - so somewhere between these there is inconsistency w.r.t being available. But DUC combined with configentry not ready should trigger retries, so that's why I don't understand why they remain at unavailable. This is mostly 21e7e67
One thing I do see is that here we conformed to upstream not to have PNR in there in favour of CENR, but we still call PNR => if it hits timeouts or whatnot it shouldn't be working (since it doesn't know about PNR).
Back to ranting out loud - everything being unavailable reeks of DUC issues, I had those when trying to convert everything as well. Which would make sense, but your log clearly shows DUC is working as it shows 'Updating Smile thermostat (something:40 seconds) and as well calls for updates.
@bouwew I think we should first replace the PNRs with ConfigEntryNotReady's and try again if @sanderdw is still willing and enthused - at the very least it should diverge so that just a config entry (that is, one of the entities) is acting up versus the whole platform.
We could also add the 0.2.10 vs PR-63 for invalidauth in there, but that shouldn't be the issue. If the above rant sort of looks plausible lets at least see if #64 works better (i.e. shows what configentry is wrong instead of bugging the whole platform -> if I understand those workings correctly).
Yes, agree, lets try Smile 0.2.10 plus #64 first.
Please see if/how 0.2.10b0
is doing
@sanderdw please first remove the plugwise-beta integration from HA, then reboot HA, then install the new version via HACS and add&configure the integration again. Please follow this process to make sure nothing carries over from the old version.
Unfortunately not working:
I'm getting more and more the idea that your Pi cannot connect to the Smile. Have you set up the networking on the Pi correctly? Can you open the Smile-website on a browser-windows on the Pi? Or can you ping the Smile IP successfully?
But the same pi with 0.2.4rc1 is working fine? Also my second pi with the build-in Plugwise integration is also just working fine?
And yes i can connect with my browser:
@sanderdw please try the latest version v0.2.11rc2 and let us know the result.
Seems to work! I had to update to Home Assistant 0.110.2
Great news, thanks!
@sanderdw We are missing a piece of data/info from the legacy Anna with firmware 1.8. Would you please take a look at what is shown at these URLs?
http://
Or, was your Anna updated to a v3 or v4 firmware? Then you don't need to look :)
Hi @bouwew, i don't use the Anna anymore. I switched to Tado because of independent zone control. So i'm adraid i can't help you guys anymore.
As requested by @bouwew (https://github.com/home-assistant/core/issues/28947#issuecomment-607419232) i installed the new plugwise-beta component in my clean home assistant test setup.
Plugwise Anna version: v1.8.20 (so the old version)
Installing: Adding this Repo to HACS went fine and also adding the integration was easy. Maybe you could document it somewhat clearer that you have to add this git repo to HACS, but i figured it out anyway.
After adding the integration it's also added to Lovelace:
But it is a water_heater instead of a climate component?
This are the entity's that were added by this component:
Also the reported temperature (33) is not correct. Currently it's 20.1 and climate is set to 20. So it's seems it's reporting the boiler temperature in the first screenshot. direct_objects.zip
Let me know what to check next?
Thanks for developing this nice component!