Hi, fixed up the device, and you should see logs now.
The issue was that last summer we have changed our logging environment. Supervisors released before before that change couldn’t handle this new logging, but any supervisor after 7.16.6 does natively use the new logging system (that is in OS version 2.15.1, so all versions above have never have issues with logging)
For older supervisors, we created patched versions that enabled them to also use the new logging system. On currently running devices we can do that update with a very small supervisor update in place. That’s what we did on your device.
There are other options, like you yourself update the device to newer OS version that pulls in the new supervisor (in the self-service OS updates section of the device)
We’ve also backported the supervisor changes as new revisions of the minor version of the OS (that’s the same OS, but pached supervisor so it works out of the box, even if older than our change). For example
2.13.6+rev2 are such backports for your device type. If you need to deploy older versions now, would recommend using them.
Does this help and clarify things? Do you need any other devices unblocked, if not as above?