Conversation
|
With this commit, after doing yarn install and yarn build, I'm not getting past the repeating "sending subscription command". Companion logs attached:
|
|
Does Companion truly not connect, i.e. you cannot send commands to the Wing or does it simply not show the green checkmark? |
|
I think this has to do with a logic flaw in the connection handling. The checkmark, circle, etc. are only status indicators, and the actual status might be different. I currently observe the exact same behavior, but once I send a command to the Wing it is executed and the green checkmark appears. Can you try that? |
|
I opened #177 that should address the status issue |
5dc6fc3 to
d1f5971
Compare
d1f5971 to
52dd20a
Compare


The console status is not kept properly. This probably comes from the prior deletion of a second OSC command with each command that is sent.
Sending the second command without an argument makes the console reply with the current status for that path, which is then used by the module to update the internal status.
Since the console returns the status after an OSC command, I think there should be a way of parsing this return value to something useful. The problem currently is that not all returned values come in the form that we would expect.
Closes #174