Julian Waller

Should this be targetting 2.2 or 2.3? In 2.3 this class is being marked as deprecated with the intention of being removed or rewritten in 2.4

This has been seen before, and is generally caused by a module updating its list of actions or feedbacks way too often. There was a suggestion the other day to...

From the logs I can see: * Approx every second 'Execute CageXState' fires. This causing a `schedule_refresh` to be emitted, and also causes the `bitfocus-companion` module to update its actions...

For those 2 cases I found, almost all the data being sent is unnecessary and can be concluded to be unnecessary much cheaper than doing a full diff. But I...

@amcchord could you update and try again? https://github.com/bitfocus/companion/commit/aa6596daa0c98e787dd52f644a69e3a5e3de3f5a should fix the part of the issue caused by triggers firing Also interesting that is is a few mb of traffic, from...

That is good to hear, but is interesting as I can only account for it using in the range of 20KB/s. But I can live with not knowing why it...

I pushed some other changes that will help reduce the amount of data a little, but only by I would guess at most half. Once the module is fixed it...

@amcchord in 2.3 there is proper json diffing being done, so I hope that this has gone away now. Could you confirm if it is better?

I am unsure if this is an issue with the atem module, or companion itself. It sounds similar to #1992, and as many other users are using companion with an...

I think this is now possible through a workaround. The execute shell command action can write the result to a custom-variable. Leaving this open to do the proper solution