Add Zappi smartregs charge delay and "being tampered with" sensor - #81
Add Zappi smartregs charge delay and "being tampered with" sensor#81Computerwhz wants to merge 8 commits into
Conversation
|
So, it has to be asked: this is the result of testing, and at least 7-days of 'run-time' testing, with no evident adverse effects? For non-UK users; I understand the desire to cancel a regulatory charge start delay, but here in the UK, that does present a dilemma of circumventing what is in effect a legal requirement. That said, this element of the implementation is used at the Users discretion and risk. It can be merged after confirmation of testing; where necessary any documentation updates in the Readme, and confirmation of successful run-time testing. |
|
I have been running it without errors for several days now and so far so good but your correct I think giving it a few more days is a smart idea. I didn't really consider that but as you said user discretion and the fact that it can be done via the app already makes this a non-issue in my opinion of course. I will update the Readme and report how the next few days go. |
|
Correct me if I am wrong but looking the Readme the only thing that needs updating is the |
|
I've just checked the App and there are no facilities to cancel the random delay applied to charge start times; are we talking about different capability? Yes some more run-time testing will ensure it has no adverse effects, particularly any automated HA runs in quiet times. |
|
Just doing some very last testing and will mark as ready |
|
Ok done my testing but still have to add support to the cli and test that |
|
Ok all done CLI support is added and tested and runtime testing is complete |

Added
smartregs_charge_delaypropertybeing_tampered_withpropertycancel_smartregs_charge_delayfunction