Strange entries in Supervisor log

Configuration
1

I was advised to check the logs as part of another problem I have. I’ve never checked the logs before, not needed as HA was doing what I expected.

When I checked the Supervisor log I found the following warnings …
2026-01-03 07:56:42.542 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Traccar’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.564 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Grocy’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.591 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Folding@home’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.690 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘InfluxDB’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.714 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Log Viewer’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.747 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘MQTT IO’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.787 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Glances’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.799 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Nginx Proxy Manager’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:42.933 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Overseerr’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2026-01-03 07:56:43.053 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on ‘Tailscale’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

These seem to relate to add-ons I’ve not got, and never have had, ( apart from MQTT IO which I played with a few months ago). Most of the add-on names I don’t even recognise. ( I do recognise Tailscale, but it’s something I would never install !. )

What is going on ?

2

Thanks for this post. I don’t know the answer to this riddle, but you reminded me that I wanted to ask the same question a few weeks ago but forgot. I have a similar list as you, and the only add-on from that list I ever installed was InfluxDB (but it’s long gone).

‘Folding@home’
‘Glances’
‘Grocy’
‘InfluxDB’
‘Log Viewer’
‘MQTT IO’
‘Nginx Proxy Manager’
‘Overseerr’
‘Tailscale’
‘Traccar’

3

You can ignore all those warnings.

They are reported for every add-on in a repository you have defined even if you have not actually installed the add-on from the repository. It has been mentioned to the dev team that this is confusing for users and causes unneeded anxiety. They however are not interested in changing it :man_shrugging:

The warnings are for the code owners to update their add-ons. Nothing for you to do.

2 Likes
4

‘Tailscale’ is some kind of peer-to-peer VPN that’s managed by the cloud.
‘folding@home’ is some background process for determining protein folding. It sends and receives data from the web without telling you. .

Both of these are very scary to someone who doesn’t want their system talking to the web all the time.

The fact that the dev team are not interested in fixing this is worrying. How are end users supposed to know what is going on inside their system if they can’t trust the logs ?

5

If you want it fixed, go to each git repo and put in an issue or thumbs up an existing issue.
Otherwise ignore it.