Northern Man

Am thinking that is `debug` level logging, can you disable that

Looking at the code, and debug is triggering that output. Do you have `DEBUG=*` in your environment ? https://github.com/NorthernMan54/homebridge-tcc/blob/0aed8ed56c037775b13f294dacab9ae6dd0c28d2/lib/tcc.js#L361

Sorry mis spoke earlier This is the line causing the log https://github.com/NorthernMan54/homebridge-tcc/blob/0aed8ed56c037775b13f294dacab9ae6dd0c28d2/lib/tcc.js#L365 It is triggered by any unhandled err condition

@DominikPalo I have been watching the development of that new device discovery method for the last year, and at the present time I have not started exploring adding this functionality....

The homebridge-mqttthing plugin is for devices you want to manually add

You should be able to easily tweak the section of code around motion detection and switch it to different portion of the RTL_433 Response. The line that detects motion is...

Maybe update NodeJS to the latest version will reset the node environment ? Also was there anything interesting in this file - /home/homebridge/.npm/_logs/2023-10-14T15_50_28_220Z-debug-0.log

Nothing in there jumps out to me I'm stumped

That message is pretty typical after an update of NodeJS, and the usual fix it to run npm rebuild or just install the plugin again.

Homebridge won't rebuild its dependencies automatically What about creating a new container, and restoring a homebridge UI backup from the existing container ? It should install / update all you...