Updating from 0.1.18 to 0.2.1 broke plugin

[rcarmo]

Describe The Bug:

I am running Homebridge 4.66.0, and upgrading the plugin to 0.2.1 from 0.1.18 broke the integration.

To Reproduce:

See above. Manually reverting to 0.1.18 restored functionality.

Expected behavior:

Logs:

There was nothing remarkable in the logs. I just stopped getting updates from devices.

Tasmota Device Config:

Please include the Tasmota Module Type / Configuration and Template ( if used )

Screenshots:

Environment:

• Tasmota Version: various
• Plugin Version: 0.2.1
• Homebridge Version: 4.66.0
• Node.js Version: 23
• NPM Version: 10
• Operating System: Ubuntu

[NorthernMan54]

Am going to need more details to dig into this further. I expect the plugin had an issue with a device, and did not setup the status update for it. It would have logged something during startup, but likely it scrolled away.

As part of the upgrade I did do a lot of testing with the various device types I have available. So am wondering if one of your devices happens to break status updates for it. Can you share the Tasmota device config of a device that is not updating status, and I will try to recreate the device and the issue.

As an alternate approach you could setup Homebridge on another device ( don't join it to your home in the Home app ), and run just the plugin with DEBUG logging enabled, and the share log. If you have a lot of devices you can filter it down to a particular device with the config option filterAllow. And just list the device your having issues with.

      "filterAllow": [
        "130C86"
      ],

In that example, 130C86 is the unique ID from tasmato of the device that is part of the MQTT discovery topic

[rcarmo]

Well, I have at least 12 devices, and I have no idea which one might have been responsible - but I was unable to see anything unusual in the logs - the only difference I noticed was that when I reverted the updates came immediately, whereas in the newer version they appeared not to be logged at all.

[NorthernMan54]

Where they marked as not responding or just no status updates ? Regardless am thinking a log with debug enabled from the startup of the plugin would be helpful. It is pretty verbose during startup, as it enables each device.