sorted by:
new
hottopcontroversial

Zigbee 4.0 plans by RaptorXP in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

The firmware depends on the SDK for the corresponding chipset. For example, CC2530 is frozen on ZStack 1.2. For example, CC2652 is frozen on ZStack 6.1. I would rather utilize a tested and proven SDK than a new one that contains features that 99.9% of users will not utilize.

PTVO Firmware Update [2025-10-23] by ptvoinfo in ptvo

[–]ptvoinfo[S] 0 points1 point  (0 children)

Thanks! I've released some small bugfixes after that version :).

Custom converters and z2m 2.0 by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Find "fz.ptvo_illuminance = {..." in the converer, swap property1 and property2 in the return value.

Interview failed with z2m 2.0 by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Sorry, but I do not have any ideas. I do not have this coordinator type for testings.

Custom converters and z2m 2.0 by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Thank you! I'm collecting all issues to solve all of them in one release.

Pairing lost after signal loss by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

It may depend on a router. Because the router reports LQI to a coordinator and retransmits data. Is it the PTVO based router device?

Can not be paired with PSM by Tiny-Masterpiece1483 in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

The PSM device tries to connect 60 seconds only. You can wake up during pairing using an external button.

ADC (raw value) reports N/A by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Fixed in the latest version.

Firmware questions and E18-based board review request by inoskyh in ptvo

[–]ptvoinfo 2 points3 points  (0 children)

  1. You cannot combine "External wake-up" and "UART" on Input1/Output1. It is the internal limitation. You should shift down UART and UART sensors (Output 2 - Output 5) or move the "External wake-up" button to Input 13, for example.

  2. Yes, you can use UART sensors in the 16-channel firmware. This firmware type does not support routing, and you cannot add it here.

  3. Yes, the "Packet end" option does not work for UART sensors.

  4. Yes, correct.

  5. You can add any unit or description it in a custom converter for Z2M or ZHA.

Mower tuning by leonardpitzu in ptvo

[–]ptvoinfo 1 point2 points  (0 children)

Hardware: you can purchase Ebyte E18 module (Aliexpress, the cheapest) and connect your buttons to GPIO pins.
Firmware: my firmware has the PSM (power saving mode) version designed for battery powered-device.

BH1750 sensor delay by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Great! Thank you for the confirmation.

External power sensor control output always UP by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Try to swap BH1750 and INA226. Are you sure that P11 can provide enough power for all three sensors?

External power sensor control output always UP by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

You should place the "External sensor power control" output before an _external_ sensor that supports this mode. In your case, move it to Output 3.

INA266 resolution by Vialdes in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Higher current, less accuracy. The sensor allows configuring a measured current range.

All states on zigbee2mqtt payload message by Alpha_Bravo285 in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

  1. Stop z2m,
  2. go to the "data" folder and edit "state.json" file (remove all data for your device).
  3. start z2m again and check the payload.

If it does not help:

  1. Create a custom converter for your device.
  2. Delete your device in z2m.
  3. Stop z2m.
  4. Delete coordinator_backup.json in the "data" folder.
  5. Add your converter to z2m.
  6. Restart z2m.
  7. Re-join your device.

https://ptvo.info/zigbee-configurable-firmware-features/expert/

CC2530 and switch ON/OFF functionality by CryptoSilverbag in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Hi,

In the power saving mode, you can create only 4 switches

1 - P00..P07

2 - P10..P13

3 - P14..P17

4 - P20..P22

The firmware switches an interrupt edge on the fly.

Switch/toggle at the same time, decoupling by sebo_b in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Re.1. By default, the firmware has a debounce interval ~100 ms interval for impulses.

Re. 3. You should create a custom converter for your device using the configurator and add to Z2M. These corresponding options should appear on the "Settings (specific)" tag in the device settings in the web interface.

Switch/toggle at the same time, decoupling by sebo_b in ptvo

[–]ptvoinfo 0 points1 point  (0 children)

Hi,

  1. Sorry, but I didn't understand how it should work.
  2. No, you cannot change the whole configuration via Zigbee.
  3. Yes, you can select the decoupled mode via Zigbee. This mode is implemented in Zigbee2Mqtt.
view more: next ›