read/write Bytestring NodesIds

[dostojewskyi]

Hi all,
I try to read/write Nodes from an OPCua Server which only has ByteString Node IDs.
I'm able to get_nodes('ns=x;'). But always when calling get_value() or get_data_value() I receive errors, that not value exist on the decoded Bytestring Node. Or I'm even noch able to read any value from any node.
Looking at the OPCua Server Side, I see, that the addressed Nodes have Values to represent.

[schroeder-]

Pass a bytestring instead of a string:
get_nodes(b'ns=x;')

[dostojewskyi]

already tried this.

try:
 n = client.get_node(b"ns=3;b=EBA=") #bytetring
 logger.info(f'node: {n}')

raises error Exception can't get node

try: 
 n= client.get_node("ns=3;b=EBA=") #string
...
try: 
 await n.read_data_value()

raises error Exception no Value on node ns=3;b=0x4542413d

using Bytestring at get_node() also hints for type error Expected type 'Node | NodeId | str | int', got 'bytes' instead

asyncua version is 1.0.4

[schroeder-]

Sry my bad.
client.get_node(ua.NodeId(b'EBA=', 3))

[dostojewskyi]

I do remember coming from using ua.NodeId.
But receiving the same issue:
[__main__ ] INFO no value on node ns=3;b=0x4542413d

this happens with:
client.get_node(ua.NodeId(b'EBA=', 3, ua.NodeIdType.ByteString)) and also w/o NodeIdType client.get_node(ua.NodeId(b'EBA=', 3))

I have the feeling I do misunderstand something completely. But I have no clue what I'm currently lacking.
this is the frontend of my OPC server GUI looking for this node:

should be allowing read & histRead

[dostojewskyi]

so found something.
I create a new Variable on Server Side w/ Opaque type..
I name it: 0x4542413d which ends up in RUJBPQ== - I can use add_node(b'EBA=') but not add_node(b'RUJBPQ=='), nor add_node(b'0x4542413d'). But I only have the list of RUJBPQ== typed elements. How can I encode them back to EBA= - can I find the logic of this somewhere?

screenshot of the Node I have created.

code snippet:

n = client.get_node(ua.NodeId(b'EBA=', 3, ua.NodeIdType.ByteString))
V = await n.read_value()

logs

INFO     node: ns=3;b=0x4542413d
INFO     value: -0.7516713

[schroeder-]

You can convert a hex string to a bytes like this:
bytes.fromhex('4542413d') -> b'EBA='
Is there a reason why using oqaque instead of other identifiers? Because if you want it readable use string and if you want speed use integer as nodeid.

[dostojewskyi]

our historian only hosts opaque as identifier.
So reverse engineered I have RUJBPQ== as ID, which I can call as EBA= which again is represented in a hex string as 4542413d this hex string is same for both.

Since on Server Side it is shown as RUJBPQ== and on Client side it's called as EBA=, and I only have the RUJBPQ== representation, how do I get to the EBA= representation (which is for all other nodes unknown to me)?