oroulet

But that code looks fine, as far as I could see. Saving to DB inside callback is ok. This is what we do in the event history stuff. What is...

The crash here says you have a variable'data' that is a string and that you seem to think is a dict. This is not related to opcua

Well programming is not magical. The error above says that data is a string. And python crashes because of that

Can you test with opcua-asyncio, sync API? I think optional fields are missing at some places in python-opcua. But this is the old format and it is not supported. try...

The problem i that optional fields are not implemented in the parsing of xml form the server. Here is the code: https://github.com/FreeOpcUa/opcua-asyncio/blob/master/asyncua/common/structures.py#L137 one should create that "Encoding" dataclass menember if...

I can merge anything. But if the bugs exist for both then it would be very nice with a bug fix in asyncua

Looking at code of get_chilfren() and using the low level api you can do whatever you want. It would have been an easy solution. But i am interested to know...

but is your example over valid? it looks really like something that is made to break things and should not be allowed by spec (but it might if they screwed...

OK. but we need to make 100% sure this matches the spec and the second ";" is never used in some corner situation

What we should look at is th description of the string format of a nodeid. Not sure where it is...