straten Posted May 31, 2024 Posted May 31, 2024 Attached is my logile - anyone have a solution? TotalConnect_5-31-2024_65500_AM.txt
bpwwer Posted May 31, 2024 Posted May 31, 2024 Looks like the library being used by the plug-in has a bug. Likely, that bug was not something that older versions of Python flagged but newer versions do. The library was released in Oct. 2020 so It's now 4 years old and has had many, many changes since them. The TotalConnect plug-in will need to be updated to use a newer version of the library, but there's a high probability that attempting to do so, will cause more issues and require more debugging/updates to the plug-in. I believe this plug-in is currently unmaintained. However, I can make a quick attempt to update the library and see what happens. 1
Solution bpwwer Posted May 31, 2024 Solution Posted May 31, 2024 It worked fine, my fears were unfounded. Version 2.0.5 has been pushed to the store. This should fix the error.
straten Posted June 1, 2024 Author Posted June 1, 2024 Thanks so much! I will attempt the update when I return to this site. Thank you sir!
straten Posted June 4, 2024 Author Posted June 4, 2024 So now I see the 2.05 version of TotalConnect is PG3 . . . . . and I am still running the TotalConnect version on PG2 Mainly because I have been reluctant to migrate all my PG2 and ISY products over - - - in fear of creating more problems to a fairly stable system on my ISY (hardly nothing is on my POLISY yet) But I guess unless i perform the migration to Polisy and PG3 I am stuck regarding TotalConnect, is that reasonably accurate?
bpwwer Posted June 4, 2024 Posted June 4, 2024 ahh, I think only the original author has the ability to modify the PG2 version. I don't have access to the code, but my changes to the PG3 version probably are the same changes needed in the PG2 version.
Recommended Posts