-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Comments
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 |
Hello, Differents:
|
@tubededentifrice can you provide the log when starting with |
@Koenkk sure thing, here is one: https://pastebin.com/Mc4gEZ8v |
@str3000 I've tried 1.5.1 (commit #ac3b924) but I've the same problems on my install |
Other tests: EDIT: Downgraded from 1.5.1 to 1.5.0 and now it doesn't work anymore on 1.5.0... weird... (running on a rpi 3b+) |
ac3b924 works in my environment. |
@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) |
@Koenkk indeed, the dev branch seems to be working fine, thanks a lot :) when is it "scheduled" to be GA? |
No ETA, first extensive testing needs to be done (as most of the zigbee2mqtt code base has been replaced/touched) |
FWIW confirmed that a 1.4.0 restore fixes this issue for me. |
I have the same problem and falling back to 1.4.0 or Dev version doesn't solve it. |
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. |
I also had the issue when upgrading from 1.3.1 to 1.6.0: |
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. |
#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/2JUKP6HmI 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)
./update.sh
to go to latest versionDebug Info
zigbee2mqtt version: 1.3.0 to 1.6.0
CC253X firmware version: 20190109
The text was updated successfully, but these errors were encountered: