In the no news is good news category, I am moving v1.13.1 to production:

Per the beta topic:

This should bring to an end this writing cycle, for those of you tiring of the updates.  Should move to a period of stability with just debug unless someone comes up with a brainwave of a new feature.  I am much happier with the stability and maintainability of the plugin now.

This minor update focused on the start-up which was very repetitive and hard on the gateways with too many polls for data.

I also really did not understand much of the polyglot ecosystem when I started this plugin ; feeling better about that now, especially how persistence and parameters work.

 

1.13.1
DONE refactor controller discovery, put, get, goodip functions
DONE refactor controller startup, config, params, naming, logging
DONE refactor cmdSetPos

@sjenkinsSeems to be running according to the AC but PG3 shows this message

9 hours ago, GTench said:

@sjenkinsSeems to be running according to the AC but PG3 shows this message

Can you restart and send me logs please. 

@sjenkinsOK here is the log file. AC shows it as connected but programs not working

HunterDouglas_10-5-2025_102538_AM.zip

@GTench, can you go to the log tab in the plugin then hit the download log package a minute or two after a restart.  Gives me more than the system log.  Thanks.

@sjenkinsOK here it is

HunterDouglas_10-6-2025_110206_AM.zip

The logs look quite clean & without error except for a timeout in start-up gathering parameters, but they are ok too.

It looks like the startup is taking longer on your machine than the timeout allows, which is why the messages.

I think you are on a Polisy, correct?  That may be why its a it slower.

I have raised it & pushed to production.

Please re-install the production version in the same slot as your current & let me know how it goes.

thanks again for your patience....

@sjenkinsthanks again for looking into this. The reinstall worked without raising the error message. I am running on eisy and have been since it was introduced

Good news!  Interesting that they are starting up at such a different speed.  I learned something on this one.  The timer should be significant anyway, well out on the normal curve, as its just to flag if something isn't right.

ok, please stress test the plugin.  I don't currently have anything else in the development pipeline.  (although my logging could have been better in this case).

If anyone has features they would like, toss them out for discussion.

On 10/7/2025 at 10:54 AM, GTench said:

@sjenkinsthanks again for looking into this. The reinstall worked without raising the error message. I am running on eisy and have been since it was introduced

@GTench,

Putting this here, so that if others are interested they can check their install.log (if you don't know what I mean and don't have any issues, don't worry about it)

I did notice something in your install.log where the aiohttp was failing to pip install.  Seems it's a thing in freebsd in certain cases, but as its part of the "optional" bits of aiohttp, it seems to not affecting the running plugin.  I do not know why it's good on mine and not on others.  Anyway, based on my research, I made some changes to my requirements.txt and added a precompiled version in vendor-wheels directory.

Would you mind installing from the non-production store into a separate plugin slot.  You don't need to add any configuration.  Let it go for about 5 minutes and pull the logs from the plugin log tab.  The install.log will have what I want.  Hoping this solves that issues & doesn't create any others.  You can delete the plugin after that.

Thanks!

 

@sjenkinsso far everything is working just fine. I will let you know if I run across any problems. Here are the logs from the non production install

HunterDouglas_10-9-2025_124159_PM.zip

3 hours ago, GTench said:

@sjenkinsso far everything is working just fine. I will let you know if I run across any problems. Here are the logs from the non production install

HunterDouglas_10-9-2025_124159_PM.zip 6.06 MB · 0 downloads

Thanks , good to hear all is well, looks like the install.log is happy as well. I might have over engineered the solution and just needed to peg the version so it doesnt try to compile a new one.