Hi.
I know that version 1.5.1 has some big breaking changes and there’a an update procedure that must be followed.
I delayed that update for too long, and now new versions came out, 1.6.0, then 1.7.0 and now 1.7.1.
By jumping from 1.4.0 to 1.7.1 is there something particular to be careful about, or is the same as updating from 1.4.0 to 1.5.1?
Thanks.
Hi.
I did a snapshot and then tried.
I updated zigbee2mqtt, but no backup of configuration.yaml has been created in /share/zigbee2mqtt.
Obviously, zigbee2mqtt does not start.
What can I try before rolling back to snapshot?
In log I see this:
19-11-24 13:51:55 ERROR (MainThread) [hassio.addons.addon] Add-on 7ad98f9c_zigbee2mqtt have wrong options: not a valid value. Got {'data_path': '/share/zigbee2mqtt', 'devices': [], 'groups': 'groups.yaml', 'homeassistant': True, 'permit_join': False, 'mqtt': {'base_topic': 'zigbee2mqtt', 'server': 'mqtt://core-mosquitto', 'user': 'my_user', 'password': 'my_password'}, 'serial': {'port': '/dev/ttyACM0'}, 'advanced': {'pan_id': 6754, 'channel': 11, 'network_key': [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13], 'availability_blacklist': []}, 'ban': [], 'whitelist': [], 'queue': {}, 'socat': {'enabled': False, 'mast...
19-11-24 13:52:50 ERROR (MainThread) [hassio.addons.addon] Add-on 7ad98f9c_zigbee2mqtt have wrong options: not a valid value. Got {'data_path': '/share/zigbee2mqtt', 'devices': [], 'groups': 'groups.yaml', 'homeassistant': True, 'permit_join': False, 'mqtt': {'base_topic': 'zigbee2mqtt', 'server': 'mqtt://core-mosquitto', 'user': 'my_user', 'password': 'my_password'}, 'serial': {'port': '/dev/ttyACM0'}, 'advanced': {'pan_id': 6754, 'channel': 11, 'network_key': [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13], 'availability_blacklist': []}, 'ban': [], 'whitelist': [], 'queue': {}, 'socat': {'enabled': False, 'mast...
Hi.
Can someone please help me?
I reverted back to 1.4.0, but I’d like to update it.
Can someone link a guide?
thanks
I never had any problems updating zigbee2mqtt, but then I always use the official guide :
under: 6. (For later) Update Zigbee2mqtt to the latest version
But if your are talking about snapshots, you must be using another way to run zigbee2mqtt.
Thanks.
I’m using Hassio, so to update I just need to click on “update”.
The problem is that 1.5.1 introduced breaking changes, so when updating from 1.4.0 a particular procedure must be followed.
Warning: Breaking Changes in version 1.5.1
Version 1.5.1 contains breaking changes and requires re-formating of the add-on configuration. Please see the updated configuration documentation below.
Restoring Configuration after upgrading to 1.5.1
By default, when upgrading to v1.5.1, the add-on will create a backup of your configuration.yml within your data path: $DATA_PATH/configuration.yaml.bk. When upgrading, you should use this to fill in the relevant values into your new config, particularly the network key, to avoid breaking your network and having to repair all of your devices.
the automatic backup of configuration.yaml is not created, but ok, I can do it manually.
anyway if I open it I can’t find any network key, what is there is this:
devices:
'0x000d6ffffe688544':
friendly_name: '0x000d6ffffe688544'
retain: false
'0x00124b001938cbb1':
friendly_name: '0x00124b001938cbb1'
retain: false
'0x00158d00029aaf18':
friendly_name: '0x00158d00029aaf18'
retain: false
'0x00158d0002ade3a2':
friendly_name: '0x00158d0002ade3a2'
retain: false
'0x00158d0002e2e527':
friendly_name: '0x00158d0002e2e527'
retain: false
'0x00158d0002ec01a2':
friendly_name: '0x00158d0002ec01a2'
retain: false
'0x00158d00032d2ddc':
friendly_name: '0x00158d00032d2ddc'
retain: false
'0x7cb03eaa0a049085':
friendly_name: '0x7cb03eaa0a049085'
retain: false
'0x7cb03eaa0a059dc0':
friendly_name: '0x7cb03eaa0a059dc0'
retain: false
'0x7cb03eaa0a05c41a':
friendly_name: '0x7cb03eaa0a05c41a'
retain: false
homeassistant: true
mqtt:
base_topic: zigbee2mqtt
password: xxxxx
server: mqtt://homeassistant
user: DVES_USER
permit_join: false
serial:
disable_led: true
port: /dev/ttyACM0
Can I ask you what you did exactly after upgrading to 1.5.1?
Edit: snapshots: I simply mean that I took a snapshot before upgrading, and I reverted back to it because the add-on stopped working.
I am having issue trying to upgrade to newest version. I click on the update button below as shown. There is a spinning icon that last for a few seconds. It disappears. There is no feedback that zigbee2mqtt has been upgraded. Logs show no errors. I tried clicking on the update button a few times. No bueno.
Running Hassio 0.113
The zigbee2mqtt docs shows how to upgrade via the cli. I am running Hassio docker on a rpi 3. I do not know how to get to the cli.
# Stop zigbee2mqtt and go to directory
sudo systemctl stop zigbee2mqtt
cd /opt/zigbee2mqtt
# Backup configuration
cp -R data data-backup
# Update
git checkout HEAD -- npm-shrinkwrap.json
git pull
npm ci
# Restore configuration
cp -R data-backup/* data
rm -rf data-backup
# Start zigbee2mqtt
sudo systemctl start zigbee2mqtt
Cli won’t help if you run the add-on. Check the log from the zigbee2mqtt add-on to see what is happening.
Clicked the update button again. Waited a few seconds. Refresh the log unde zigbee2mqtt add-on log. Nothing. There should be something after 14:00.
I’ve enabled the auto update a few hours ago, but it hasn’t updated to new version.
.
.
.
zigbee2mqtt:info 2020-07-23 13:46:31: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":63,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:48:08: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":65,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:49:45: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":36,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:51:22: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":78,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:53:00: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":44,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:56:00: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":false,"linkquality":44,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:56:05: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":70,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 13:57:43: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":true,"linkquality":78,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
zigbee2mqtt:info 2020-07-23 14:00:43: MQTT publish: topic 'zigbee2mqtt/0x588e81fffe11693e', payload '{"occupancy":false,"linkquality":78,"update_available":false,"battery":87,"requested_brightness_level":254,"requested_brightness_percent":100}'
@francisp
Maybe a fluke. I tried again a few hours later to update and it works AND I think it was the missing link of another issue I was facing in regards to all sensors showing unknown after every restart of HA.