You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The updated Mennekes lock in controller FW V8.1.0 lincomatic/open_evse#141 has both an automatic and a manual mode. In manual mode, the lock can be controlled via RAPI.
A useful basic function for this manual mode would be to provide a toggle on the web interface to set the lock mode:
Automatic
Permanently Locked
Permanently Unlocked
Manual mode is non-volatile, therefore must be enabled on boot. It would be a good idea to show the lock status on the /status info page.
S5 A|M|0|1 - Mennekes lock setting
A = enable automatic mode - locked when connected, unlocked otherwise
M = enable manual control mode
0 = unlock (valid only in manual mode)
1 = lock (valid only in manual mode)
n.b. requires MENNEKES_LOCK. manual mode is volatile - always boots in automatic mode
G5 - get Mennekes settings
response: $OK state mode
state: 0 = unlocked
1 = locked
mode: A = automatic mode - locked when connected, unlocked otherwise
M = manual control mode
Note: lock mode is also indicated by ECVF_MENNEKES_MANUAL
n.b. requires MENNEKES_LOCK
The lock will also need to be implemented via OCPP and HTTP/MQTT API.
The text was updated successfully, but these errors were encountered:
I'm planning to add the Menneke lock actuator to my EVSE for testing and finilising this feature. @jeremypoulter I haven't checked yet, does the openevse_lib already implemented it?
The updated Mennekes lock in controller FW V8.1.0 lincomatic/open_evse#141 has both an automatic and a manual mode. In manual mode, the lock can be controlled via RAPI.
A useful basic function for this manual mode would be to provide a toggle on the web interface to set the lock mode:
Manual mode is non-volatile, therefore must be enabled on boot. It would be a good idea to show the lock status on the
/status
info page.The lock will also need to be implemented via OCPP and HTTP/MQTT API.
The text was updated successfully, but these errors were encountered: