EO: Difference between revisions
Added a "regaining access" section based on initial investigation of the files pulled from a Smarthome Raspberry Pi. I'm not anywhere near a working solution but it does seem like it would be fairly straightforward to pull out the server communication code and implement a degree of local control |
|||
Line 44: | Line 44: | ||
The Mini Pro 2 units don't have any physical controls either on the wall unit or control unit, so the app is currently the only way to interact with the charger. | The Mini Pro 2 units don't have any physical controls either on the wall unit or control unit, so the app is currently the only way to interact with the charger. | ||
== Regaining access (WIP) == | ==Regaining access (WIP)== | ||
In the case of the "Smarthome" unit, an additional control box is installed alongside what appears to be a unit identical to the Mini Pro 2. | In the case of the "Smarthome" unit, an additional control box is installed alongside what appears to be a unit identical to the Mini Pro 2. | ||
Line 54: | Line 54: | ||
Initial investigation seems to indicate that much of the control is handled over a USB->serial adaptor (Genius) which is hard-wired in to the Smarthome HV board. This indicates it should be fairly trivial to send the required commands to alter charging levels, start/stop/lock the charger, at least for owners of the Smarthome unit. | Initial investigation seems to indicate that much of the control is handled over a USB->serial adaptor (Genius) which is hard-wired in to the Smarthome HV board. This indicates it should be fairly trivial to send the required commands to alter charging levels, start/stop/lock the charger, at least for owners of the Smarthome unit. | ||
Custom firmware, that allows to set schedules and control the charger via LAN is now available for the eomini charger: https://github.com/minceheid/openeo | |||
==Products== | ==Products== |