Device identification

Manufacturer ID, Manufacturer name – these identifiers contain information about a manufacturer. Usually, it does not matter.

Model ID – it is the unique identifier of a device type. High-level systems use this identifier to provide correct data parsing and handling from a device.

Location description – it is an optional user-defined description of a specific device.

Network security key – the device uses this key to connect to your Zigbee network. By default, the firmware uses the wide-used key “01030507090B0D0F00020406080A0C0D”. This key should match the key used on a coordinator (hub). The unique key minimizes the risks of attacks on your network.

Default reporting interval – this option allows you to set a custom default reporting interval for periodic reports. If this value is zero, periodic reports are disabled. If this option is disabled, the reporting interval is 60 seconds.

Disable configuring the interval remotely in run-time – if this option is disabled, you may use the “interval” command in Zigbee2MQTT and change the interval of periodic reports. Otherwise, the firmware always uses the default reporting interval.

Disable resetting of a device by a power on/off cycle – if this option is enabled, you cannot reset a device by switching power on/off three. If you didn’t configure a button on “Input 1”, you cannot reset or re-pair a device without reflashing it.

Update firmware’s timestamp – the program automatically sets the firmware creation date to the current date. Usually, this information is visible in a high-level system.

Wait for commands after a report in PSM – if this option is enabled, the firmware waits three seconds for additional commands from a coordinator. For example, a calibration command for some sensors, changing an output state, etc. Otherwise, the firmware goes to sleep mode immediately after a report. When the device sleeps, it does not accept any commands.

Enable watchdog timer – this option enables a built-in watchdog time in the chip. The timer resets the device if it froze for more that 1 seconds. I do not recommend using it in complex and untested configurations with many sensors. The device may unexpectedly reset.

Save custom converter for Z2M – The standard Z2M converter for PTVO devices implements only generic functions (switch, a sensor value). For example, the standard converter does not allow controlling PWM.

This button allows you to create a custom external converter for your configuration of the firmware. The custom converter allows implementing and controlling of all functions in a high-level system. The converter includes “exposes” for the configured channels. Therefore the Z2M frontend provides the correct interface for your device. Additionally, it provides smooth integration with other high-level systems based on Z2M like HomeAssistant, ioBroker, and others.

You should place the generated file in the “data” folder of your Z2M installation and add a link to it in the Z2M’s configuration.

Note: Custom converter are available in the Z2M version 1.18.2 and higher.


There are no comments.

Leave a Reply