Release v1.3.10

👏 💪 Several good bug fixes from contributors in this update.

📝 Please note that the labeling of whether a CS node auto-connects at startup has changed. You can check this in the config dialog of the ocpp-cs-json node.

🐛 Bug Fixes:

#103 ( thx olivierpelet )

• Leak that occurred when EV chargers were disconnecting/reconnecting multiple times.
• Messages sent to the EV charger were also sent multiple times (due to the above)
• Fixed a scope issue on the wsrequest
• Add a routine check that clears dead/non-responsive websocket connections every 30 seconds

#104 (thx Rishabh Vaish )

• Fix for attribute typo — The had for="node-input-wsdealyconnect" (note the eal instead of ela), so clicking the label text didn't toggle the checkbox. Fixed to for="node-input-wsdelayconnect".
• Rename option — Changed from "Delay connection on startup" to "Delay auto-connect on startup" to make it clearer that this controls whether the node auto-connects, not some timeout delay.
• Clarify documentation — Updated the help text to explicitly describe both checked and unchecked behavior:
• Checked: connection is deferred until a type "99" connect message is sent
• Unchecked (default): node auto-connects to the CSMS on flow start
• Clarify inline comment in JS to match the renamed label.

Other

• Multiple Bumps of 3rd party libraries

v1.3.9

🚀 Feature

LOCAL_ commands

• LOCAL_SET_ALL_AUTH_EVSES: Send a Map of evse_name:passwords to connection validation
• LCOAL_GET_ONLINE_LIST: Returns a list of EVSEs that are assumed online with the server

🐛 Bug Fixes

• fix for undefined passwords being treated like zero-length passwords

V1.3.5 Fix for disconnected CP/CSMS and refactoring.

This release aims to address issues #47, #48, and #50 and add code from pull requests.

Thanks to @art #49
and @abkulaki #45
for their contributions

This release should have better tracking of EVSE connections.
There was also a spelling mistake in the ocpp section (listed as MessageID instead of MessageId) . Either is now supported to avoid a compatibility issue, but only the more official MessageId is listed in the documentation.

v1.3.4 "CP Client JSON" better reconnect support

Node-Red package:

• Bump required NodeJS version to 16
• Bump required Node-Red version to 2

CP Client JSON node:

• Replace 3rd party reconnecting-ws with local implementation
  • New config params for min/max/inc reconnection timings
  • Node show # of reconnect retries
• msgType 99 + command "ws_state" makes node output msg.ocpp.websocket with connection status

README.md

• Long overdue spellcheck 🙄

All other:

• Mainly removing "dead wood" commented out lines

v1.3.3 Bug Fix Release for "CP Client JSON"

This release fixes issue #23 and addresses a crash that could occur if the Central System (CSMS) URL is invalid.

NOTE : Only the node "CP Client JSON" was updated.

Thank you to those that reported the issue.

v1.3.2 Bug fix release

This release addresses the Issues:
#4
#35

Minor release v1.3.1

NOTE: If you use the the cp request node, this update is required
Fix broken require statement in ocpp-req node
Add check for websocket subprotocol in ocpp-server

Version 1.1.0 release

What's New in this Release

• Breaking Change: Requires node v10 or higher
• Enhancement: #7 Reconnecting-Websocket from pull request
  • Thanks https://github.com/chrisn-au
• Update: UUID to new instantiating format { u4: uuid }
• Bump: several 3rd party dependencies
• Fix: spelling mistakes on config dialogs

v1.0.11 Release

Update: to latest 3rd party modules only (in response to github security warnings)

v1.0.10 Release

• Update 3rd party dependencies
• Fix node status of CS request nodes to properly reflect connection to CP