Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade 1.3.0 > 1.6.0 fails with firmware 20190109 #1980

Closed
tubededentifrice opened this issue Sep 15, 2019 · 15 comments
Closed

Upgrade 1.3.0 > 1.6.0 fails with firmware 20190109 #1980

tubededentifrice opened this issue Sep 15, 2019 · 15 comments

Comments

@tubededentifrice
Copy link

tubededentifrice commented Sep 15, 2019

#1787 Bug Report

What happened

After upgrading from 1.3.0 to 1.6.0 (with ./update.sh), zigbee2mqtt wouldn't start.
Logs can be found at https://pastebin.com/Q2RuWwJt
CC2531 is on firmware 20190109 and I had it running for months perfectly fine.

After downgrading to 1.3.0 with git checkout 00ebd44; rm -rf node_modules; npm install, everything starts just fine again: https://pastebin.com/2JUKP6Hm

I haven't tried to re-flash the CC2531 while on 1.6.0, so it could really be an incompatibility issue beweek 20190109 firmware and 1.6.0. However I haven't seen any such incompatibility disclosed anywhere on the releases page.

What did you expect to happen

Painless, in-place upgrade

How to reproduce it (minimal and precise)

  • Get a CC2531 on 20190109
  • Check that everything works fine on 1.3.0
  • run ./update.sh to go to latest version
  • Check that it doesn't start anymore

Debug Info

zigbee2mqtt version: 1.3.0 to 1.6.0
CC253X firmware version: 20190109

@tubededentifrice
Copy link
Author

NB: Problem persists with CC2531 on 20190608 (tried on another CC I had though): https://pastebin.com/vcMeQKwN

v1.3.0 is working properly on that CC2531 with 20190608

@str3000
Copy link

str3000 commented Sep 15, 2019

Hello,
only additional info because I had the same problem.
I go back to V1.5.1 and zigbee2mqtt starts now. Puhhh

Differents:

  • CC2531: CC2531_SOURCE_ROUTING_20190619
  • nuc i3

2019_09_15_V1.6-logs.txt

@Koenkk
Copy link
Owner

Koenkk commented Sep 15, 2019

@tubededentifrice can you provide the log when starting with DEBUG=* npm start

@tubededentifrice
Copy link
Author

@Koenkk sure thing, here is one: https://pastebin.com/Mc4gEZ8v

@tubededentifrice
Copy link
Author

@str3000 I've tried 1.5.1 (commit #ac3b924) but I've the same problems on my install

@tubededentifrice
Copy link
Author

tubededentifrice commented Sep 15, 2019

Other tests:
1.3.0 => 1.3.1: Works fine
1.3.1 => 1.4.0: Works fine
1.4.0 => 1.5.0: Works fine
1.5.0 => 1.5.1: Doesn't work
So it looks like the bug was introduced in 1.5.1

EDIT: Downgraded from 1.5.1 to 1.5.0 and now it doesn't work anymore on 1.5.0... weird...
mosquitto/now 1.6.4-0mosquitto1~stretch1 armhf

(running on a rpi 3b+)

@str3000
Copy link

str3000 commented Sep 15, 2019

ac3b924 works in my environment.
It seems that everything works fine.
mosquitto version 1.5.8

@Koenkk
Copy link
Owner

Koenkk commented Sep 16, 2019

@tubededentifrice can you check if the dev branch works properly for you? This is a zigbee-shepherd bug and I prefer not to fix any bugs there anymore (it's a waste of time because it will completely be replaced by zigbee-herdsman which is in the current dev #1888)

@tubededentifrice
Copy link
Author

@Koenkk indeed, the dev branch seems to be working fine, thanks a lot :) when is it "scheduled" to be GA?

@Koenkk
Copy link
Owner

Koenkk commented Sep 19, 2019

No ETA, first extensive testing needs to be done (as most of the zigbee2mqtt code base has been replaced/touched)

@Koenkk Koenkk closed this as completed Sep 19, 2019
@jamesawebb
Copy link

FWIW confirmed that a 1.4.0 restore fixes this issue for me.
/ht @tubededentifrice

@negmos
Copy link

negmos commented Sep 30, 2019

I have the same problem and falling back to 1.4.0 or Dev version doesn't solve it.
My system is:
CC2531: CC2531_SOURCE_ROUTING_20190619
Device: PI3B
Using Docker container

@HarrisonPace
Copy link

HarrisonPace commented Oct 2, 2019

I am also having this issue.

EDIT: Using DEV Branch fixes the issue, seems Zigbee-Sheppard isn't working under 1.6 when upgrading, so I advise all users experiencing this issue, to install DEV branch in the interim given zigbee-herdsman will become standard as Koenkk stated.

@andreas-bell
Copy link

I also had the issue when upgrading from 1.3.1 to 1.6.0:
zigbee2mqtt did not start, rebooted, unplugged, hit reset, copied the config again, tried the previous firmware, the default 20190608 and the source routing 20190619 firmware, nothing worked with 1.6.0 (different errors).
I then upgraded to the dev branch: (in combination with the source routing 20190619 firmware)
payload '{"version":"1.6.0","commit":"ba92f73"
and then for the first time since the upgrade zigbee2mqtt started again and is processing messages.
I'm not sure if I should stay on the dev branch with my production system, or if I could downgrade to 1.6.0 again.

@Koenkk
Copy link
Owner

Koenkk commented Oct 11, 2019

Dont worry on staying on the dev branch, this uses zigbee-herdsman (#1888) which is much better than zigbee-shepherd (zigbee2mqtt 1.6). Also this will be close to what zigbee2mqtt 1.7 will be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants