Jump to content

TotalConnect Error - "Discovery failed please check logs for a more detailed error"


Go to solution Solved by bpwwer,

Recommended Posts

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.  

  • Like 1
Link to comment

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?

Link to comment

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.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...