Alexander Schrode

If compared the differences between python-opcua and asyncua and found the following:   I will make a fix to address the difference.

The default is an empty ExtensionObject. We must return a error AttributeIdInvalid if the ExtensionObject is empty. This change triggers some errors in some other code that does expect empty...

There is nothing in the spec about empty DataTypeDefinitions. Found the following: node-ua same as asyncua open62541 same as python-opcua I think we should return an error to keep some...

@om327 can you test it with fix #937 ? If it works we can merge it, if it doesn't help I will do some more research about the spec.

Ok DataTypeDefinition is optional as of https://reference.opcfoundation.org/v104/Core/docs/Part3/5.8.3/. So return BadAttributeIdInvalid is ok if it doesn't exists or is empty ExtensionObject.

You can construct your own ContentFilter to only get the event values you want. I add an example where you get EventType, Message, ActiveState/Id and ConditionName of an AlarmConditionType. ```...

Can you post the result of this print statement? `print(repr(my_event_type ))` I think it's most likely that either the server or client logic fails to provide a good eventfilter.

I think we have some issues resolving types in the correct order, i will try to work it out soon. In the mean time, you could try load_type_definitions instead.

@jmtatsch can you try my draft #901 and tell me if I fixed all errors?

Should be fixed in v0.9.95 otherwise there is another bug.