Module does not start, only crashes

[heisjolly]

Make sure you're on the latest stable or beta build of both Companion and the module

• I have tested this on the latest stable or beta release

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm guessing I'm just doing something wrong as I don't see anyone else mentioning this, but I cannot get the module to not crash at all on 3.5.5, 4.2.0 or 4.2.2.

I'm hoping I can get it to work on my existing 4.2.2 Companion instance, talking to my 3.1 Behringer Wing Rack, using the stable 2.2.2 module.. but the module just constantly crashes until it gives up trying and says 'Connection not found or not running'. It does not load any configuration (e.g. no IP address field).

I've tried downloading the offline module bundle and re-importing everything.

Then I tried uninstalling Companion completely, deleting the appdata files, re-installing Companion from scratch, add the connection and same symptoms: Initialising -> Crashed, 3-4 times then gives up.

Any ideas?

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

- OS: 
- Browser: 
- Companion Version: 
- Module Version: 
- WING Firmware Version: 
- WING Model:

Additional context

No response

[janikwitzig]

Hi @heisjolly , sorry to hear that you are habing such a bad experience with this. There is a bug in the module (not Companion) version 2.2.2 does exactly as you are describing.

The solution is to use the newest Companion and first use the Wing module 2.1.0, establish a connection and then upgrade to 2.2.2