Releases: Tknika/iombian
IoMBian 2.2.1
This bugfix release upgrades the base operating system to Debian Bullseye (2023-12-05-raspios-bullseye).
Happy testing and thanks for your support! 👍🏻
What's Changed
Full Changelog: v2.2.0...v2.2.1
IoMBian 2.2
IoMBian 2.2 is finally here!
Since IoMBian 2.1 version was released (Mar 14, 2022) many things have changed:
- A brand new logo has been designed:
- Raspberry Pi OS base operating system has been updated to: 2023-05-03-raspios-bullseye
- WeTTY service has been introduced, so users are able to establish a local SSH connection directly from the browser
- Node-RED has been updated to version 3.1.0
- The IoMBian Configurator platform has been greatly improved:
- A new logo and colors has been introduced
- The webapp can be installed as a PWA on mobile and desktop
- IoMBian services can be opened from the browser if the device is in the same network
- IoMBian services can be opened from a remote location thanks to a new tunnel service (based on boringproxy)
We hope it was worth the wait and that you will be able to take advantage of the new features.
Many thanks to our testers and stay tuned for new updates! 🆕
What's Changed
- Add WeTTY service by @bodiroga in #16
- Update iombian-confinit service by @bodiroga in #18
- Add IoMBian Tunnels Handler service by @bodiroga in #17
- Add IoMBian Services Uploader service by @bodiroga in #19
- Add IoMBian System Info Uploader service by @bodiroga in #20
- Update iombian-remote-configurator service by @bodiroga in #21
- Update pi-gen (2022-11-09) by @bodiroga in #22
- Update Node-RED to version 3.0.2 by @bodiroga in #23
- Fix WiFi activation problem by @bodiroga in #24
- Fix iombian-services-uploader's old 'db' reference by @bodiroga in #26
- Improve publisher GitHub Action by @bodiroga in #27
- Add new logo and icon by @bodiroga in #28
- Add action to upload artifacts as comments to PR by @bodiroga in #25
- Define image generation stages manually by @bodiroga in #29
- Add stage 2 to stage list by @bodiroga in #31
- Update pi-gen to 2023-05-03 version by @bodiroga in #33
- Upload image artifact after each push to master by @bodiroga in #34
- Build with bullseye by @bodiroga in #36
- Update PyZMQ by @bodiroga in #37
- Update Node-RED to version 3.1 by @bodiroga in #30
Full Changelog: v2.1.0...v2.2.0
IoMBian 2.2 Beta 10
This new version updates de iombian-services-uploader service to fix a simple bug: an old 'db' field reference was kept by mistake.
Sorry! 🙃
IoMBian 2.2 Beta 9
This release fixes a problem with the activation of the WiFi connection.
Thanks for your support! 👍🏻
IoMBian 2.2 Beta 8
This release addresses a couple of issues:
- Firestore related services now wait until time is synchronized before starting
- All service will be killed earlier if they get stuck
Happy testing!
IoMBian 2.2 Beta 7
The iombian-config-file-handler service has been updated to stop itself before rebooting the device, in order to avoid any lock state.
Thanks for your feedback!
IoMBian 2.2 Beta 6
All Firebase related projects has been updated:
- iombian-remote-configurator
- iombian-services-uploader
- iombian-system-info-uploader
- iombian-tunnels-handler
The firestore server response timeout has been increased to be more flexible with network delays.
We are really close to the release candidate (RC) version 🎉
IoMBian 2.2 Beta 5
This new beta version updates the following packages:
- Node.js: from 14.x to 18.x
- WeTTY: from 2.3.0 to 2.5.0
- Boringproxy: from v0.9.1 to v0.10.0
Another step closer to the final version, thanks for your help 👍🏻
IoMBian 2.2 Beta 4
This new beta removes the Raspberry Pi OS configuration wizard introduced with Bullseye, as IoMBian handles the user (name and password) creation.
We are closer to the final 2.2 release, stay tuned! 🎉
IoMBian 2.2 Beta 3
All services that connect to the iombian-configurator platform (firebase) have been rewritten to improve the reconnection logic. The services are smarter now to detect when the network connection is down and retry the connection until it succeeds. This should fix the sudden filling problem of the microSD card, because the reconnection logic is handled manually and not by the google-cloud-firestore library.
Feedback is always welcomed!