Z2M Errors on Start - JS out of memory

Note down what devices are missing at the moment and when you re-pair make sure you name them like the old names. Less hassle with dashboards and automations that way.

1 Like

Slowly coming back, few of the usual issues lol. Thanks for your help everyone :clap: :clap: :clap:

1 Like

Hi, writing this comment, to help other lost souls, because I had problems with the migration from zstack to ember with the error z2m: Error: [BACKUP] Current backup file is not for EmberZNet stack. even after changing the IEEE according to FAQ | Zigbee2MQTT (was a bit pain under W11 with WSL [see usbipd]), too.

  1. stop z2m
  2. backup from zigbee2mqtt (or data) directory (this is to make a clean rollback if needed)
  • configuration.yaml
  • coordinator_backup.json
  • database.db (warning: under VSCode it’s usually hidden!)
  • state.json
  1. rename coordinator_backup.json to e.g. coordinator_backup.save.json
  2. In the zigbee2mqtt/configuration.yaml
  • change serial adapter to adapter: ember (maybe port, for me it stayed port: /dev/ttyUSB0
  • maybe in advanced to transmit_power: 20
  1. start z2m to generate a new coordinator_backup.json
  • now the error occurs
  1. stop z2m
  2. in coordinator_backup.json
  • copy everything from coordinator_backup.save.json expect the first 2 blocks (metadata and stack_specific) and save
    For me I first tried to keep the new coordinator_ieee (although I changed and checked it according to the link above) and the extended_pan_id, which was a mess.
  1. start z2m again

For me this worked flawless after my initial fail