<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
We can also add the "sufficient SOC/range reached" notifications,
the low SOC alert and the low 12V alert to the framework.<br>
<br>
Porting the low 12V detection is on my list for today/tomorrow. For
the sufficient SOC/range notifications, I currently still (mis-)use
the topoff state, which is irritating to users.<br>
<br>
Notification config should include a channel selection for each, so
users can choose which of them to get by SMS. May be combinable,
i.e. instead of a bool, use a set of ("ip", "sms")?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 25.04.2018 um 03:13 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:53F5886B-6F46-42F9-B7BB-6B23D9D19B44@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
It is time to implement vehicle notifications (charge started,
charge completed, charge interrupted, etc) in the vehicle modules
I am supporting. It seems that this can be done in the
vehicle.{h,cpp} framework in a standard manner, and work across
all vehicle types. However, I guess that will break any
notifications already being produced by other vehicle types.
<div class=""><br class="">
</div>
<div class="">My suggestion is:</div>
<div class=""><br class="">
</div>
<div class="">
<ol class="MailOutline">
<li class="">A config parameter ‘notifications’, with
individual instances to turn on/off the notifications.
Default is all enabled.<br class="">
<br class="">
</li>
<li class="">OvmsVehicle::MetricModified picks up metric
changes and issues the standard notifications (checking
‘notifications’ parameter appropriately).</li>
<ul class="">
<li class="">charge_mode=>charging: Notify charge started</li>
<li class="">charge_mode=>topoff: Notify charge started</li>
<li class="">charge_mode=>heating: Notify battery heating
started</li>
<li class="">charge_mode=>done: Notify charge completed</li>
<li class="">charge_mode=>stopped: Notify charge
interrupted</li>
<li class="">valet_mode=>on: Notify valet mode enabled</li>
<li class="">valet_mode=>off: Notify valet mode disabled</li>
<li class="">alarm=>on: Notify alarm is sounding</li>
<li class="">alarm=>off: Notify alarm is off<br class="">
<br class="">
</li>
</ul>
<li class="">All the above should be suppressed for the
initial setting of each parameter. I will have to look into
metrics to see how best that should be done; one neat way is
to keep a modification count (rather than the current
m_defined boolean).</li>
</ol>
</div>
<div class=""><br class="">
</div>
<div class="">Does that make sense? Any objections/suggestions?</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>