The developers of this module are in no way endorsed by or affiliated with Open Charge Alliance, or any associated subsidiaries, logos or trademarks.
Adapter to connect an OCPP 1.6 supported wallbox
- (foxriver76) revert changes of 0.12.4
- (foxriver76) allow deactivating
numberPhases
by setting `null
- (foxriver76) ensure main connector is always created even if no status received there
- (foxriver76) we now also detect feature profiles if clients add unallowed whitespaces
- (foxriver76) the
idTag
for remote transactions is nowioBroker
persistent over all transactions - (foxriver76) implemented the management of authentication list
- (foxriver76) only create states if supported by profile (closes #22)
- (foxriver76) increased stability on first connection
- (foxriver76) we now correctly detect data type and role of configuration attributes
- (foxriver76)
idTag
is now read correctly fromstartTransaction
message (closes #21) - (foxriver76) implemented possibility to trigger
hard
andsoft
reset
- (foxriver76) implemented state to control number of phases used for charging
- (foxriver76) we now avoid not implemented logging if
chargeLimit
is set to null (deactivated)
- (foxriver76) we removed states from main connector which are not allowed there
- (foxriver76) we now synchronize configuration into adapter
- (foxriver76) we added ack flag to
availability
state - (foxriver76) we added ack flag for
charge limit
states - (foxriver76) we optimized error logging
- (foxriver76) we now allow changing charger configuration via adapter
- (foxriver76) we improved reconnect handling
Please delete all states of connector 0 once
- (foxriver76) only log the
errorCode
if it is different fromNoError
- (foxriver76) make
transactionId
matchingconnectorId
again
- (foxriver76) we now support wallboxes with multiple connectors (closes #16)
- (foxriver76) we added a new state
lastTransactionConsumption
- (foxriver76) implemented a
transactionId
handling The structure of the datapoints has changed to support wallboxes with multiple connectors. Please delete states once and adjust your scripts!
- (foxriver76) we have introduced a state to sepcify if chargeLimit is in watts or ampere
- (foxriver76) we now handle
DataTransfer
messages
- (foxriver76) we have optimized some log messages
- (foxriver76) added possibility to define the
idTag
of the transaction (closes #13)
- (foxriver76) implemented authentication
- (foxriver76) fixed default value of
info.connection
- (foxriver76) set 'TxDefaultProfile' instead of 'TxProfile' if charging starts, else it may block overriding the limit during transaction
- (foxriver76) set charging profiles on stack level 0, because some chargers do not support higher levels
- (foxriver76) if wallbox offers multiple meter values they will now alle be represented
- (foxriver76) admin is no longer needed on the same host (multihost)
- (foxriver76) close server on unload for compact mode
- (foxriver76) fixed the message type
- (foxriver76) limit state is now in Ampere and should work now
- (foxriver76) we are requesting config of new clients too
- (foxriver76) we fixed a bug with limitState not respected on
startTransaction
- (foxriver76) make sure we use no outdated connection
- (foxriver76) small optimizations
- (foxriver76) updated dependencies
- (foxriver76) fixed error on sending commands if device name containts dots
- (foxriver76) we also log repsonse errors from now on
- (foxriver76) switch to updated OCPP fork
- (foxriver76) minor optimizations
- (foxriver76) we now replace dots in device names by underscores
- (foxriver76) added possibility to limit the charging process to given Wh if supported by ChargePoint
- (foxriver76) we fixed name of availability state
- (foxriver76) we fixed unnecessary comma in
info.connection
state
- (foxriver76) we added the meterValue state
- (foxriver76) we added state to control availability
- (foxriver76) we can now enable/disable a charger
- (foxriver76) initial release
MIT License
Copyright (c) 2022 Moritz Heusinger moritz.heusinger@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.