Hey everyone,
I am having an issue while trying to have two vision clients with different users open for the same gateway and project. If one client and user changes the value of a tag, my audit page is saying the other client is trying to change it back, one true and one false going back and forth. This is only stopped if one client is terminated from the gateway. Example, one client turns off a pump, the other tries to write it on if it is selected on, on its side. Has anyone had an issue with that?
Sounds like a programming error, where your UI has some kind of property change script that does this. Please show the audit records--they should include the write method.
2 Likes
Sorry, here's the redacted audit log.
And that audit log is only for the Off target, its the same pattern for the On target as well. The script for that HOA button is an old truth table. If one user/client changes the HOA state, it should reflect on the other correct? First time I'm running into this.
I can imagine the order of writes mattering, if you pass through an invalid state--causing the other script to try to "fix" it. Best to not fix invalid states from UIs--just ignore that combination in the controlled device.
Or use a single integer for the states from which the controlled device derives the true mode. Then the UIs only perform consistent writes.
If you're using bidirectional bindings, this doesn't happen; without more context, we're flying blind, but you said "script", and that's immediately suspect. If it's truly a script, add debug logging to find out why it's firing, and work backwards from there.
They are multi-state buttons and they are not currently bi-directional. How would you add debugging to that?
So there's a change script on the button ? Add the logging there.
But you can probably rework this to not use a script at all.
