Thanks @jens_rossbach - I've just released 2.1.2 that should fix all of the issues raised here.
I tested it with both of your nodes and the others mentioned (although I never did find out which nodes @Hypnos was referring to).
If you still see any odd behaviours, please raise them as issues. As I've said, its important that we don't regress behaviour - even if we do update the best practices to follow.