You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16 lines
1.6 KiB
16 lines
1.6 KiB
\section{Conclusion}\label{conclusion}
|
|
|
|
The project has been successfully deployed in the hackerspace and is now an essential part of home-automation development and deployment.
|
|
|
|
The update infrastructure has been the crucial point for decisions towards the framework for most members.
|
|
Enabling the developers to do updates in combination with the shared configuration and behavior provided by the framework resulted in a massive speedup when it comes to project deployment.
|
|
Before that, the cost for an change after deployment was estimated so high, that most projects tend to delay deployment until all required and wanted features are implemented.
|
|
Now, as the devices are deployed as soon as the hardware is considered stable, these devices start to provide functionality early and therefore the developers can get better feedback on the provided functionality.
|
|
|
|
Most of the devices running the update-enabled firmware have undergone multiple major updates without any problems.
|
|
This includes a major network configuration change and a big stability fix for network communication.
|
|
All devices applied the update successfully and started to work without any manual interaction required afterwards.
|
|
|
|
The project will be continued to extend the functionality with features already being in development.
|
|
The latest development includes enhanced checksum verification where the firmware can be signed using cryptographic methods and will be verified during the update process.
|
|
In addition, the information provided by the device about the firmware status will be enhanced to allow better control and reduce maintenance effort even more.
|