I found out that this bug (keyframing property values is not working for custom nodes) seem to exist also in Animation Nodes on Blender 2.80, FYI @Jacques Lucke (JacquesLucke)

Hmm, it looks like the animated f-curve evaluates correctly in python console via D.node_groups['NodeTree'].animation_data.action.fcurves[0].evaluate() even though value shown in node is not updated.

@Lorenzo Celli (lorenzocelli) can you please test: is the animated value actually changing correctly, even though value is not shown updated on the node?

This is a fairly well known limitation. I'm not sure what is needed to make it work, but we should be able to figure that out.
For animation nodes, I usually advice people to not keyframe their nodes but create controller objects in the 3d view instead.

Should still be fixed though... Not sure if there is already another bug report for this.

@Tuomo Keskitalo (tkeskita) I tested it and to me it seems that the properties don't update at all, not in the UI and not by accessing them via python. The last keyframe you set just becomes the value for all frames, ignoring the other keyframes you set before

It looks like this goes down to somewhere in depsgraph/animation sources of Blender. Beyond my skills, so I hope someone more experienced can help. At least the F-curve is there apparently OK. Thanks @Lorenzo Celli (lorenzocelli) for confirmation.

Anything new? Maybe I'm missing another similar bug report

Hello everybody! Any news?

In T66392#749929, @Jacques Lucke (JacquesLucke) wrote:

This is a fairly well known limitation.

In that case I'll change this task from a Bug to a To Do, and put it in the appropriate work board. It would be nice to lift such a limitation at some point, but that probably would require doing some proper design work.

Most of my addon's interface is in the form of nodes with their own properties, so I would very much like to see this capability reimplemented.

In T66392#749929, @Jacques Lucke (JacquesLucke) wrote:

This is a fairly well known limitation. I'm not sure what is needed to make it work, but we should be able to figure that out.
For animation nodes, I usually advice people to not keyframe their nodes but create controller objects in the 3d view instead.

Should still be fixed though... Not sure if there is already another bug report for this.

Hello! Can you tell more about this controllers setup? I can't find informations about how to set it up. I mean in Animation Nodes, because in Node Editor it works when I use drivers

In T66392#900690, @Andrzej (endrju555) wrote:

Hello! Can you tell more about this controllers setup? I can't find informations about how to set it up. I mean in Animation Nodes, because in Node Editor it works when I use drivers

This is a bug tracker, not a support forum. Please visit https://animation-nodes.com/ for info about Animation Nodes.

Yes this is quite an annoying problem. I solved it by using bpy.app.handlers.frame_change_pre but...
EDIT: Seems like I just was able to call update but not to get the actual correct value from the property :-(.
EDIT2: Weird, in compositor for example I can see the good result but not when rendering even when using bpy.app.handlers.render_pre. Seems like when changing frame like when clicking or pressing arrow key the animated value is working but not during render. Is it related to T63548?