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

Bump deCONZ to 2.05.81 #1573

Merged
merged 10 commits into from Sep 22, 2020
Merged

Bump deCONZ to 2.05.81 #1573

merged 10 commits into from Sep 22, 2020

Conversation

pattyland
Copy link
Contributor

@MartinHjelmare MartinHjelmare changed the title deconz: Bump deCONZ to 2.05.81 Bump deCONZ to 2.05.81 Sep 15, 2020
@frenck
Copy link
Member

frenck commented Sep 15, 2020

I think we should not.

A) As we decided before with 2.05.80 (beta of this release), it removed the possibility to update. As the release notes of clearly state only manual updates work at this point:

image

There was a fix: dresden-elektronik/deconz-rest-plugin#3256
But considering the warning, we can't tell its enough. Although it appears to be fixed, the release notes don't add up.

Lastly, (B) 2.05.82 is already tagged, but not released yet. Apparently a hotfix is inbound as well??

image

@fi-sch
Copy link
Contributor

fi-sch commented Sep 16, 2020

@frenck
That's cleared out in this issue that I've created in DE repository: dresden-elektronik/deconz-rest-plugin#3266
Manual update requirement isn't the case with the latest deCONZ – update via Phoscon will work.
That note in release notes is just for those that don't update deCONZ...

V2_05_82_2 is out now but it's just a pre-release with no significant changes.

Copy link
Contributor

@fi-sch fi-sch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the value be set to "2.05.81"?

deconz/config.json Outdated Show resolved Hide resolved
deconz/CHANGELOG.md Outdated Show resolved Hide resolved
@pvizeli
Copy link
Member

pvizeli commented Sep 16, 2020

@pattyland would be nice if you can test it next time...

So we have the issue now, aarch64 have no 2.5.81

@manup is it possible to get an 2.5.81 release for aarch64? I don't need to be tagged as stable, only available :)

@manup
Copy link
Contributor

manup commented Sep 16, 2020

Good hint, yes but will take a bit, the aarch64 needs to be integrated into the normal stable/beta builds.
Should be ready till Friday.

@manup
Copy link
Contributor

manup commented Sep 16, 2020

Note however that the 2.5.82 (beta) is already available also for aarch64, compared to 2.5.81 there are some new device support related changes. https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_82_1

http://deconz.dresden-elektronik.de/raspbian/alpha/deconz-dev_2.05.82-debian-stretch-beta_arm64.deb

@manup
Copy link
Contributor

manup commented Sep 16, 2020

Clarification for the firmware update, since .81 the update via REST-API and Phoscon App is enabled again with the same firmware which was part of .79 release. The release fixes some bugs which people had while updating the firmware.

The new firmware mentioned above, is too young to roll out "automatically" yet, hence until battle tested it remains to be installed manually, likely a candidate for the next release.

@pvizeli
Copy link
Member

pvizeli commented Sep 16, 2020

@manup thanks for you hard work. What do you like that we should use, stable or beta for long term? Do you have plans to make more stable releases (sure stable is a hard word :) ) because of device updates? Since people make also issues on your site, I will give you a voice for what we should distribute to our users.

@manup
Copy link
Contributor

manup commented Sep 19, 2020

@pvizeli Thanks :) I think the safest approach is to use the stable versions. We are aiming to to make a stable version 2–3 weeks after each beta version. The beta versions are scheduled for the 15th of each month and may include larger patches and new device support PR's. Based on the beta the stable versions are mainly focused on fixing bugs.

In that hindsight stable will get new devices, with a delay of roughly a month behind beta.

I've cleaned up the aarch64 uploads into new /debian/{stable | beta}/ folders. The beta was formerly uploaded to /raspbian/alpha/ where it doesn't belong, the files are still available there to not break downloads, but will eventually be removed in a few months.

http://deconz.dresden-elektronik.de/debian/beta/deconz_2.05.82-debian-stretch-beta_arm64.deb

http://deconz.dresden-elektronik.de/debian/stable/deconz_2.05.81-debian-stretch-stable_arm64.deb

@ArniPL ArniPL mentioned this pull request Sep 19, 2020
@dedepene
Copy link

I hate to be "that guy" but is there any ETA for merging this and making it widely available? I have a little project that hangs in the air, waiting for the support of devices the latest Deconz brings...thanks!

@frenck
Copy link
Member

frenck commented Sep 20, 2020

@dedepene The answer is always: No, there is no ETA.

@fi-sch
Copy link
Contributor

fi-sch commented Sep 22, 2020

Is there any chance of bumping this to the latest stable version anytime soon?

@PolestarWx
Copy link

@fi-sch
Do not ask for ETA please

@fi-sch
Copy link
Contributor

fi-sch commented Sep 22, 2020

I'm not asking for ETA. This is a simple question, any answer would be appreciated (yes/no). I just wanted to know if this could possibly take two months or two weeks. No pressure from my side.

I know that it's not a commercial product and a lot of volunteer work is going on. I do respect and appreciate that also.

@stigvi
Copy link

stigvi commented Sep 22, 2020

@fi-sch
Do not ask for ETA please

But it would be nice to have a release based on a stable version instead of a beta/pre-release as we have now as the current version. I don't know about others, but I have to restart HA almost every day because of websocket problems with the deconz add-on. It got a lot better with version 0.115, but I would very much have a version with release notes like "This stable release contains mainly bug fixes and robustness improvements."

@home-assistant home-assistant locked as off-topic and limited conversation to collaborators Sep 22, 2020
@pvizeli pvizeli merged commit c0791f8 into home-assistant:master Sep 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants