Open Wilmshurst opened 1 year ago
@Caleb-Wishart
@Wilmshurst, What version of the module are you running. There was a known issue with the version initially bundled in companion 3.0 release (See #14).
Hi Caleb, companion v3.0.0(3.0.0+6049-stable-126f27e8) Module inside companion says: Aja helo v2.0.1
After reading ticket #14
I updated to beta 3.1.0(3.1.0+6142-beta-56d157f4) which is publicly avaliable from bitfocus.
I can confirm the issue persists in the version
I'll investigate this further.
For context are you using Helo Classic or Helo Plus?
I am aware that the modules doesn't provide the best logging.
I believe I have identified the issue.
The program should be working correctly and all commands sent to the Helo are actually actioned in other words the connection is actually fine but there is an issue with the feedback and the module incorrectly diagnoses it as a connection failure.
I will do a proper test ASAP and push an update so that the module status isn't incorrect.
thanks caleb, i can confirm that it is the helo classic
Finding the same problem w/ the classic here as well. Thanks to everyone working on this.
Finding the same problem w/ the classic here as well. Thanks to everyone working on this.
I brought in the latest beta of companion that included the changes on the issue. Works for me now.
Companion should be moving 3.1 into the main release soon. Looking forward to being able to close out the issue for good :)
Hi, my previous version of companion i was running was v2.4.1, and helo (classic) ran flawlessly. since updating to 3.0.0 my connection fails frequently at boot.
reconnecting can take 2 or 3 attempts.
once reconnected the connection drops as soon as a command is issued from companion to the helo
i am running firmware 4.3.0 on my helo, and this has not changed.
Issue is not network related...
Log attached does not show much. procedure undertaken durnig log
all other attempts to send other commands result in the same response "debug: Command result: {}"
HELO Log.txt