Correct.
The module is a LM465, so no softstart.
The macro command starts (from AHP timer) with a 'on' (not 100% command) command for the LM465.
The log shows the on command for the LM465 (and the LM465 module responds). I believe the software doesn't report 'slave' devices like the chime.
Ok, I think I'm starting to get the picture. I need a little more clarification, though:
Have you tried creating a test macro with ONLY the chime in it, to see what happens?
Have you tried adding the chime to the macro (even though it should come on when the light does), to see what happens?
Have you tried running your macro with the Lamp Module unplugged, to see if the chime reacts? It is possible that the lamp module might be loading down the signal, and it is too weak by the time it gets to the chime to activate.
You might also try changing the chime to a different Unit code than the lamp (mixing module types on the same Unit code can cause strange behavior), and then adding it into the macro as a separate action after the lamp.
Finally, what version of AHP are you running?