Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node-Red "ot-sim out" modules don't affect tag value #8

Open
SleepyHIpster opened this issue May 23, 2024 · 3 comments
Open

Node-Red "ot-sim out" modules don't affect tag value #8

SleepyHIpster opened this issue May 23, 2024 · 3 comments

Comments

@SleepyHIpster
Copy link

I'm trying to use Node-Red to modify tag values. When testing, I've found that the 'ot-sim out' nodes don't actually affect the value of tags in the message bus. When using the tags in the same node-red flow, they appear to be changed, but the values do not change for other ot-sim modules.

@activeshadow
Copy link
Member

Hi @SleepyHIpster I would need to see a way to reproduce this. We have many examples of the ot-sim out node successfully affecting tag values within other OT-sim modules via the message bus.

@SleepyHIpster
Copy link
Author

Specifically, I'm having issues with messages updating across node-RED instances. For example, I'm trying to use one instance to modify input data, and another as an HMI of sorts.

Instance 1:
ot-sim in [tag1] --> ot-sim out [tag2]

Instance 2:
ot-sim in[tag2] --> debug

When looking at the debug, there are messages coming through, but the value is 0.

@activeshadow
Copy link
Member

@SleepyHIpster so are you running two OT-sim NodeRED modules on the same OT-sim device?

If you can, please provide the OT-sim config file(s) you're using so I can try to reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants