Zigbee2MQTT 2 failed to start

The new version of Zigbee2MQTT (Z2M) adds new features and improvements, but occasionally, they can break compatibility with existing devices :). Most of the breaking changes are about removing legacy features that have been deprecated for years.

If your PTVO-based devices do not work in the latest version (Z2M shows the “Unsupported” status for your device), it seems, you should update a custom converter for it.

Note: Z2M stops loading external converters after the first broken converter. If some of your DIY devices are “unsupported” now, this does not mean that you should update converters for all devices.

Firstly, now, all external converters should be in the “zeegbee2mqtt/data/external_converters” folder.

1. Create the “external_converters” folder within the “data” folder.
2. Copy all *.js files from the “data” to the new folder.
3. Z2M loads all converters from the new folder automatically. You do not need to add them to the configuration (configuration.yaml).

How to fix broken converters

Option #1

You can re-create a converter in the latest version of Firmware Configurator, update it in the “data/external_converters” folder, and restart Z2M.

Option #2

Or, if you cannot remember a configuration of your old device, and therefore re-create a converter, you can edit the existing file:

1. Find your custom converter “.js” file in the “data/external_converters” folder of your Z2M installation.
2. Remove the following identifier with the trailing comma from a string where it is present.
3. Restart Z2M.

Remove the highlighted identifier

fromZigbee: [fz.ignore_basic_report, fz.ptvo_multistate_action, fz.legacy.ptvo_switch_buttons, fz.ptvo_on_off, fz.ptvo_on_off_config,],