P200 connections becoming “corrupt” when installing new versions.

[obcocav]

Sometime in the last few betas my connections to 3 P200s have started crashing and becoming unable to connect after installing a new beta.

I tend to install the latest betas pretty regularly especially as I get my setup ready for V3. Somehow something has corrupted and now none of my connections to P200s connect. Creating a new connection works. I’ve tried reinstalling older betas but it seems the “damage” has been done. The original programmed connection never connect then crash. Log shows E22 connection refused.

Similar to the issue when the module was first updated.

[bryce-seifert]

When you say "unable to connect", is that only with Companion? Are you still able to connect to the P200 web ui or via some other application?

[obcocav]

Yes still able to talk to the cams via another control software, cam control, the dashboard, etc.  the companion module just tries to load then crashes.  On another PC loaded with companion and the config imported I am able to add a new instance and it connects ok.Thanks!Sent from my iPhoneOn May 15, 2023, at 20:39, bryce @.***> wrote: When you say "unable to connect", is that only with Companion? Are you still able to connect to the P200 web ui or via some other application?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[obcocav]

Hey @bryce-seifert. I think I may have found a lead for this issue. I finally noticed that some of my instance names previously had a space in the cam ie CAM 2 vs CAM2. When I go to import now they default to CAM_2 with the underscore without any interaction from me. Wondering if it is something with the instance naming in the install scripts?
Thanks!

[bryce-seifert]

Intersting. The instance rename is happening at the Companion level, not within the module itself. But that being said, I don't think this should affect the connection. Can you export a support bundle from the companion log page and send via slack, after the module crash occurs?

[obcocav]

@bryce-seifert Sent a couple replies via Slack. Sorry I guess I didnt realize how Slack and Github interact or don't. Didnt mean to scatter replies between them.

It looks like the other issue I had from right after the module update to 3.0 is back too. After I closed Companion and restarted it now will never finish loading the GUI and CPU is pegged at 100% . Guessing that's the same issue @Julusian and @krocheck found with the feedback drawing on the buttons from the cameras I think it was. Seems to be the same root issue again from this module though. Thanks for the help

[bryce-seifert]

Ah ok I think I see why this might be happening. I fixed the upgrade config issues, but I didn't actually release a new version for the beta builds. I'll work on that now

[bryce-seifert]

@obcocav The latest companion beta should have the fix for the upgrade error. Let me know if this resolves the issue

[obcocav]

@bryce-seifert.

Unfortunately like I mentioned I think the problem from earlier in the beta cycle is back. I am unable to even load the GUI in the last couple of builds. It takes 15 min or so the first time I launch companion for the “syncing” screen to appear but it never finishes loading even after a restart. One time the GUI did pop up but all modules were listed as “unknown” status and companion crashed. Since then I get to the sync page and it never finishes. @Julusian @krocheck

[obcocav]

Looks like 5889 is the last usable build I can get to open

[Julusian]

could you send me your db file? git@julusian.co.uk

[obcocav]

Looks like its solved with the latest updates! Thank you!