Update every node?
-
After Release of a new branch (2.0 for example), should I re-compile and re-upload all my sketches to my nodes and also to my Gateway? Or should I just use the new releases on future nodes?
-
@siod You can keep them in their current state should be compatible.
-
We might implement features in 2.0 that's not backwards compatible with 1.x. Specifically signing is not compatible. And other features sneak in right now, that needs 2.0.0 in both ends of a link (controller and gateway)
-
@tbowmo what is the expected release date?
-
@vikasjee
We were thinking of releasing 2.0 when we were having the MySensors meetup/BBQ at my house 9th of July.
-
@hek said:
@vikasjee
We were thinking of releasing 2.0 when we were having the MySensors meetup/BBQ at my house 9th of July.So using the term "release-party" is also valid here
-
mmh, sounds like a lot of work if you have a lot of nodes...especially if you have to expect that more/higher versions will be released in the future, too...
-
and thats the point where you thoink about OTA updates as a very handy tool...
Suggested Topics
-
Day 1 - Status report
Announcements • 23 Mar 2014, 22:45 • hek 24 Mar 2014, 20:12 -
JSN SR04T - Temperature Influencing Readings
Troubleshooting • 6 Sept 2019, 07:51 • Timbergetter a day ago -
Compiling Sensor code using BME280 and ESP8266
Troubleshooting • 26 Feb 2025, 00:32 • dpcons 26 Feb 2025, 06:22 -
Echo request is not set
Troubleshooting • 12 Aug 2024, 15:36 • kamilb85 3 Sept 2024, 08:58 -
NODs stop responding, but ping works.
Troubleshooting • 21 days ago • Marcin 21 days ago -
Getting system time from the controller
Troubleshooting • 27 Feb 2025, 01:39 • dpcons 27 days ago