

12:07, EET

February 20, 2025

Hello,
I’m working with OPC UA’s MonitoredItems and have a specific use case where I want to avoid receiving the initial value notification when creating a monitored item. According to the OPC UA specification (Part 4, Section 5.12.2 https://reference.opcfoundation.org/Core/Part4/v104/docs/5.12.2), the server performs initialization processing when a MonitoredItem is added.
Currently, I can work around this by implementing a boolean flag in my data change listener to skip the first notification. However, I’m wondering if there’s any native filtering mechanism in the Java Client SDK to suppress this initial value notification without requiring custom filtering logic.
Is there a more elegant solution available in the SDK?
Most Users Ever Online: 1919
Currently Online:
76 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 791
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1538
Posts: 6493
Newest Members:
Phillipbus, Oscarsat, WilliamJer, WilliamTunse, mvsjonah79, RaymondSmutt, Merlin AI pap, patlawrence98, opcua_1232141232321, DavidGadayModerators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0
Administrators: admin: 1