Monitoring app issues writes after get log failure

Hello, I would much appreciate you helping me to solve a mystery.

I have a nvme device that does not support get smart log command.

The app Issues “smartctl -H” command, and this command sends get log command to the device, which returns with an error since it is not supporting it.
Apparently I noticed that after a few get log commands that fail to the device, a write command is being sent to it to offset 0, size 4096 bytes.

I would like to know if this behavior is defined by nvme spec or if it is unexpected (a bug in the app).

Many thanks in advance,