I’ve just upgraded to version 0.12.4.1 and I cant get the integration to initialize. I’ve been using it for ages and not had problems with upgrades before. I have a PowerMax Complete accessed by an ESPHome ESP D1 Mini which is still working without problems which I can access it fine from the ESPHome web page. I have rebooted Home Assistant several times and done a full cold boot of the HASS device. I’ve also cold started the PowerMax by disconnecting and reconnecting the battery to no avail. I’ve put Visonic diagnostics on the log file and got this output:
Hi and welcome,
There are 2 possibilities I think:
The configuration migration has failed
This text Timeout waiting for config entry f8fd3cfd273db828de1222aee42e32dd to load implies that the configuration has failed to load in the 10 second timeout I give it, do you have a particularly large system i.e. lots of integrations?
There are 2 things that you can try:
If you have access to the python code, search for self.getEntryID(), 10 in client.py and change the 10 to maybe 30 to give it a longer timeout
Delete the configuration and set it up again, I suggest that you download the diagnostics file first as that contains all of your existing settings that you can put back when your recreate it.
You might want to update to release 0.12.4.4 but it won’t make a difference with this problem.
Also, I used 10 seconds as the timeout as that’s what I found in other integrations that I copied the code from.
Let me know how you get on with it please, especially if making the timeout 30 seconds works, but if this doesn’t work then please create a specific issue on the wiki with an appropriate title
EDIT: Just to add, it is not getting to the point in the code where it makes the connection to your panel, it is nothing to do with the panel or ESPHome or your D1 Min, this is a problem in HA and the device you’re running it on.
Hi Dave,
thanks for the quick response, I had a go at editing the code to up the timeout to 30secs, as you can see from the logs it did wait 30 secs before again timing out…
so that didn’t do the trick, I did also try 0.12.4.4 same result. I’ve since downgraded back to version 0.12.3.2 and that is working again, so it would seem to be something that has changed in the latest versions. The only other thing I’ve noticed on downgrading again as that it’s telling me that the Visonic integration is not proving the Arm/Disarm sensors for the zones which are very useful.
Hi,
I added the check in 0.12.4.0 to make sure that the integration’s configuration is loaded in Home Assistant before I start to use it, it’s the first thing that I do in the code. I was getting a few errors reported that the configuration wasn’t loaded when I tried using it (i.e. all the setting that you enter when you create the integration).
Leave it with me and I’ll dig into it a bit more, I might be checking for it being loaded too early i.e. i’m checking for it being loaded but this might be stopping HA loading it, do you see what I mean.
I’ve just pushed 0.12.4.6 to Github, are you able to grab the zip file and give it a try?
I’ve basically undone what I did and put it back to how it was, so I don’t check that the configuration is loaded. I’ll see how things go and if I get problem reports about it.
Hi Dave, I upgraded back to 0.12.4.4, downloaded the zip and just replaced in the 3 changed files. It’s now working again but I still have the problem I mentioned earlier that the Arm/Disarm zone entities I used to have are showing as not provided.
I’m not sure what you mean, do you mean the arm/bypass select entities?
In any case, I suggest that you create an Issue on the wiki, with an appropriate title and with a debug log file as described here and I’ll take a look.
Hi all,
I just wanted to say that I’ve released a new version 0.12.4.7 on Github, also available from HACS.
Please read the release notes, they include this: If you installed a previous 0.12.4 release then please go through the configuration settings to check and correct them to your needs. Go to the integration and click on the Configure Cog.
Hi Dave, it was the arm/bypass select entities and it must have been the earlier 0.12.4 update that reset the bypass sensors setting to off in the config. So I’ve updated to 0.12.4.7 and now set the bypass sensors to on again and all is good, so no need for an issue to be raised.
