Update Changelog and README for version 8.3.0 release, highlighting new features including configurable RS-485 transmit pacing, improved startup resilience, latitude/longitude overrides, version check enhancements, Docker improvements, and updated Node.js requirements.

Author: tagyoureit

Changelog

@@ -1,6 +1,6 @@
 # Changelog
 
-## 8.3.0 (UNRELEASED)
+## 8.3.0
 1. Configurable RS‑485 transmit pacing via new `controller.txDelays` for finer collision avoidance and throughput tuning.
 2. Startup & config resilience: empty or invalid `config.json` now auto‑recreated from defaults, corrupt originals backed up.
 3. Latitude / longitude environment overrides to eliminate early heliotrope warnings prior to UI configuration.
@@ -10,6 +10,23 @@
 7. Runtime requirements: elevated minimum Node.js version to 20+, safe dependency and security/patch updates.
 8. Documentation updates.
 
+## 8.1.2
+1. Regal Century pump support added.
+2. Enhanced error handling: replaced EquipmentNotFoundError with InvalidEquipmentIdError for improved clarity.
+3. Improved error handling in NixieBoard, NixieCircuitCommands, and NixieValveCommands.
+4. Refactored tolerance handling in TouchChemControllerCommands to ensure data integrity.
+5. Added new expansion board configuration for SunTouchBoard.
+
+## 8.1.1
+1. Enhanced REM server integration with packet capture functionality.
+2. Improved error handling in REMInterfaceServer methods.
+3. Refined chlorinator message processing logic in MessagesMock.
+4. Adjusted mock port checks across various components for consistency.
+5. Refined logic for Nixie schedules.
+6. Fixed documentation links for bindings integrations.
+7. Enhanced queueBodyHeatSettings to handle processing timeouts and improve error logging.
+8. Fixed typo in valveModes.
+
 ## 8.1.0
 1. Support for dual chlorinators with REM chem controllers.  It is now possible to have two separate chlorinators controlled in 'dynamic' mode by two separate REM chems.  Note: In order for REM chem to control each chlorinator, each needs to be on a dedicated RS-485 port (not shared with an OCP or any other chlorinator).
 

README.md

@@ -1,7 +1,7 @@
 ```diff
 - INTELLICENTER USERS: Do not upgrade Intellicenter to 2.006.  Rollback to 1.064 to use this application. 
 ```
-# nodejs-poolController - Version 8.1
+# nodejs-poolController - Version 8.3.0
 
 ## What is nodejs-poolController
 
@@ -26,6 +26,16 @@ Equipment supported
 ## Latest Changes
 See [Changelog](https://github.com/tagyoureit/nodejs-poolController/blob/master/Changelog)
 
+## What's new in 8.3.0?
+
+1. Configurable RS‑485 transmit pacing via new `controller.txDelays` for finer collision avoidance and throughput tuning.
+2. Startup & config resilience: empty or invalid `config.json` now auto‑recreated from defaults, corrupt originals backed up.
+3. Latitude / longitude environment overrides to eliminate early heliotrope warnings prior to UI configuration.
+4. Version check enhancements: git detection, safer redirects, throttled polling, warning suppression.
+5. Docker improvements: fixed Dockerfile and added docker‑compose example with named volumes & environment variable guidance.
+6. Add workflow to build and publish docker images to GitHub Container registry.
+7. Runtime requirements: elevated minimum Node.js version to 20+, safe dependency and security/patch updates.
+
 ## What's new in 8.1?
 
 Support for dual chlorinators with REM chem controllers.  It is now possible to have two separate chlorinators controlled in 'dynamic' mode by two separate REM chems.  Note: In order for REM chem to control each chlorinator, each needs to be on a dedicated RS-485 port (not shared with an OCP or any other chlorinator).
@@ -73,9 +83,10 @@ For a very thorough walk-through, see [this](https://www.troublefreepool.com/thr
 #### Upgrade Instructions
 Assuming you cloned the repo, the following are easy steps to get the latest version:
 1. Change directory to the njsPC app
-2. `git pull`
-3. `npm i` (not always necessary, but if dependencies are upgraded this will bring them up to date)
-4. Start application as normal, or if using `npm run start:cached` then run `npm run build` to compile the code.
+2. **Important**: Ensure you have Node.js v20 or higher installed (`node --version`). If not, upgrade Node.js first.
+3. `git pull`
+4. **Important**: Run `npm i` to update dependencies. This is especially important when upgrading to version 8.3.0+ as it requires Node 20+ and has updated dependencies.
+5. Start application as normal, or if using `npm run start:cached` then run `npm run build` to compile the code.
 
 ### Docker instructions