Hi,
A while back I received a message that my copy of Domoticz should be updated. I followed the advice
and I then needed two days to get anything working, as the need to upgrade the OS had been omitted.
My system is now working successfully...back with the old version of Domoticz, together with HA-Bridge and our good friend Alexa.
However, once again I am being offered the "opportunity" to upgrade my version of Domoticz...this time to version 11995.
Much as I want to do this I cannot face the rebuild that I went through before. So, here is my question.
I have given my current version of Domoticz below and also the current version of the OS. Will it be sufficient for me to execute a sudo update / sudo upgrade to update the OS and packages and then to install the new DOmoticz, or do I have to make a fresh build?
Domoticz version: 3.8153
Build Hash: 494fff7
Compile Date: 2017-07-30 11:19:41
OS Version
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Thank you for your help
George
Upgrade to Version 11995 ---low risk or.....?
Moderator: leecollings
-
- Posts: 13
- Joined: Monday 16 September 2013 18:02
- Target OS: Linux
- Domoticz version:
- Contact:
-
- Posts: 116
- Joined: Saturday 13 July 2013 13:28
- Target OS: Linux
- Domoticz version: Latest
- Location: Hilversum, The Netherlands
- Contact:
Re: Upgrade to Version 11995 ---low risk or.....?
You need buster/Debian 10 for the latest domoticz.
Just google how to do this, then the upgrade to the latest domoticz is easy.
Just google how to do this, then the upgrade to the latest domoticz is easy.
Rasp Pi 2B: 3x DS18S20 (1-wire), BME280 (i2c)
Cubietruck 1: Aeotec Z-Wave+, RFXtrx433XL+P1, RFXtrx868, TE923 display, SolarEdge API
Cubietruck 2: Aeotec Z-Wave, Voltcraft CO-20
Cubietruck 1: Aeotec Z-Wave+, RFXtrx433XL+P1, RFXtrx868, TE923 display, SolarEdge API
Cubietruck 2: Aeotec Z-Wave, Voltcraft CO-20
-
- Posts: 13
- Joined: Monday 16 September 2013 18:02
- Target OS: Linux
- Domoticz version:
- Contact:
Re: Upgrade to Version 11995 ---low risk or.....?
Hi,
Thanks....I did Google the upgrade path and I found two approaches...one is the fu re-image and re install of everything. As I have a lot of services, UPS and more installed, this could be heavy. I also found an in-situ upgrade from a couple of places Is this the method that you refer to as "easy".....?
George
Thanks....I did Google the upgrade path and I found two approaches...one is the fu re-image and re install of everything. As I have a lot of services, UPS and more installed, this could be heavy. I also found an in-situ upgrade from a couple of places Is this the method that you refer to as "easy".....?
George
-
- Posts: 116
- Joined: Saturday 13 July 2013 13:28
- Target OS: Linux
- Domoticz version: Latest
- Location: Hilversum, The Netherlands
- Contact:
Re: Upgrade to Version 11995 ---low risk or.....?
If you have a lot installed, then make a backup first.
I have done upgrades from major Debian releases in the past. They all succeeded, but it can always go wrong.
If you have succeeded in upgrading to Debian 10, then the upgrade to the latest Domoticz version can be done via the webinterface.
I have done upgrades from major Debian releases in the past. They all succeeded, but it can always go wrong.
If you have succeeded in upgrading to Debian 10, then the upgrade to the latest Domoticz version can be done via the webinterface.
Rasp Pi 2B: 3x DS18S20 (1-wire), BME280 (i2c)
Cubietruck 1: Aeotec Z-Wave+, RFXtrx433XL+P1, RFXtrx868, TE923 display, SolarEdge API
Cubietruck 2: Aeotec Z-Wave, Voltcraft CO-20
Cubietruck 1: Aeotec Z-Wave+, RFXtrx433XL+P1, RFXtrx868, TE923 display, SolarEdge API
Cubietruck 2: Aeotec Z-Wave, Voltcraft CO-20
-
- Posts: 13
- Joined: Monday 16 September 2013 18:02
- Target OS: Linux
- Domoticz version:
- Contact:
Re: Upgrade to Version 11995 ---low risk or.....?
Thanks for that...I am indeed planning a backup and recovery path should the "easy" process go pear-shaped or worse. The basic idea is not to reach a point where there is no guaranteed recovery.
Some of my code has been running for so long that it is hard to remember all the details of installation...across several Rasbian versions and pi implementations. I know of no solution to these problems..and please don't mention documentation. It would be nice to have well-structured top-down documentation...but I am coming round to the idea of consistent implementation style(assuming the versions of Rasbian allow this) and a significant investment in go-nogo start-up processes for my various services and so on. Also makes the task more reliable and interesting..than a "get it working and run" approach.
This all sounds like a task for next week. Once again, thanks for the help
George
Some of my code has been running for so long that it is hard to remember all the details of installation...across several Rasbian versions and pi implementations. I know of no solution to these problems..and please don't mention documentation. It would be nice to have well-structured top-down documentation...but I am coming round to the idea of consistent implementation style(assuming the versions of Rasbian allow this) and a significant investment in go-nogo start-up processes for my various services and so on. Also makes the task more reliable and interesting..than a "get it working and run" approach.
This all sounds like a task for next week. Once again, thanks for the help
George
Who is online
Users browsing this forum: No registered users and 1 guest