This isn’t the case, but we’re blocked here – if we had the device in front of us, we could probably determine if this was happening on our side, or the Weiss side. Then, we could try to implement a bug fix or workaround depending on the underlying cause.
As it is, there’s not much we can do without looking at this in a development environment. We have tried to reach out to Weiss but we haven’t had any luck.
We’ll circle back and see if we can make any progress, but we are as frustrated as you are to not have their help resolving this.