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

Problems with fieldname in event message #765

Open
powidian opened this issue Dec 23, 2024 · 0 comments
Open

Problems with fieldname in event message #765

powidian opened this issue Dec 23, 2024 · 0 comments

Comments

@powidian
Copy link

powidian commented Dec 23, 2024

Hello,
I noticed that there was probably a problem with the field names contained in the event message payload.
The field names "EventType", "SourceNode", "ConditionId" have their field names automatically replaced by their "BrowseName" because they are of type "NodeId" ("ns=??;s=????").
Thus, once the event message is received, it is no longer possible to find the information "EventType", "SourceNode", "ConditionId" since their unique names are replaced by an unpredictable reference.
This regression occurred with commit 5823ae6 of August 2023. The addition of lines 240,241,242,243 are the cause. Deleting these lines makes this problem disappear.
I do not know the need that required the addition of these lines.
Can you update the code so that it no longer makes the identity of these fieldname disappear?
Thanks in advance

@powidian powidian changed the title Problems with filename in event message Problems with fieldname in event message Dec 23, 2024
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

1 participant