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
I am currently using a wall-mounted EV charger branded as Timxon, model EAW-A007T, running firmware version A0-V2.1.0-beta2.
Although the charger is connected via OCPP 1.6 JSON to server through 4G LTE (Quectel EG915U), we are experiencing reliability issues in connection stability, especially during idle states.
This affects automated charging scenarios in smart home environments.
Current Behavior
The charger disconnects from the OCPP server roughly every 60 minutes when idle (no car connected).
Heartbeat messages are not sent when the charger is idle, leading to WebSocket closure either by the LTE modem or the server.
We are using Home Assistant as our automation controller, which triggers RemoteStartTransaction commands at scheduled times using input_datetime.
However, if the charger is disconnected from the OCPP server at the scheduled time, the charging session does not start, and the command is lost.
❓ Main Question
Is it possible to store a scheduled charging command directly on the charger itself, so that:
A future charging time (e.g., "Start charging at 02:00 AM") is stored inside the charger
The charger can begin charging at that time even without active connection to the OCPP server or Home Assistant
The schedule is retained across disconnections or reboots
If this is not currently supported, we would like to know:
Whether this feature is being considered for future firmware versions
If there's any local API or interface (Modbus, MQTT, direct GPIO trigger) that could be used to implement such fallback behavior
Why This Matters
In smart energy systems, EV charging is often optimized based on electricity tariffs or solar production.
These systems (like Home Assistant) need reliable execution of scheduled charging, even in case of temporary internet or OCPP disconnection.
Charger Info
Brand: Timxon (OEM variant of Morek)
Model: EAW-A007T
Firmware: A0-V2.1.0-beta2
Network: 4G via Quectel EG915U
Protocol: OCPP 1.6 JSON
Request Summary
Can the charger support locally stored scheduled charging?
Is there any workaround (e.g. trigger by external switch or time-based rule) to enable this behavior?
If not currently possible, is this functionality planned in future firmware updates?
We appreciate your clarification or guidance regarding offline autonomous scheduled charging support.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Question: Local Scheduled Charging Capability
I am currently using a wall-mounted EV charger branded as Timxon, model EAW-A007T, running firmware version
A0-V2.1.0-beta2.Although the charger is connected via OCPP 1.6 JSON to server through 4G LTE (Quectel EG915U), we are experiencing reliability issues in connection stability, especially during idle states.
This affects automated charging scenarios in smart home environments.
Current Behavior
RemoteStartTransactioncommands at scheduled times usinginput_datetime.However, if the charger is disconnected from the OCPP server at the scheduled time, the charging session does not start, and the command is lost.
❓ Main Question
Is it possible to store a scheduled charging command directly on the charger itself, so that:
If this is not currently supported, we would like to know:
Why This Matters
Charger Info
Request Summary
We appreciate your clarification or guidance regarding offline autonomous scheduled charging support.
Beta Was this translation helpful? Give feedback.
All reactions