<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Jaunius,<div class=""><br class=""></div><div class="">I don’t know of any automatic facility to do this. A counter/timer to be used in the case of a can bus message setting setpoint to zero makes sense as a workaround.</div><div class=""><br class=""></div><div class="">However, it is probably worth looking elsewhere in that CAN bus message to see if there is any flag that changes to indicate the value is stale. You can get a CAN bus dump of this message, along with the one for CC on/off, and see if there is any correlation.</div><div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 4 Mar 2020, at 3:06 AM, Jaunius K. <<a href="mailto:jaunius@gmx.com" class="">jaunius@gmx.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class=""><p class="">Hi Mark,</p><p class="">Thanks again for the tip, however it seems that the 0 is sent
just before the CC is turned off. <br class="">
So to avoid that I guess I need to set a delay to update the
metric each n seconds to give enough time for the CC to go in to
OFF state.<br class="">
</p><p class="">Is there any built in way of doing that, or do I have to add my
own function?</p><p class="">Currently that code part looks like this:</p>
<div style="color: #333333;background-color: #f5f5f5;font-family: 'Droid Sans Mono', 'monospace', monospace, 'Droid Sans Fallback';font-weight: normal;font-size: 14px;line-height: 19px;white-space: pre;" class=""><div class=""><span style="color: #aaaaaa;font-style: italic;" class=""> // setpoint gets reset on CC off, so we only update it while it can be actually changed</span></div><div class=""><span style="color: #333333;" class=""> </span><span style="color: #4b69c6;" class="">if</span><span style="color: #333333;" class=""> </span><span style="color: #777777;" class="">(</span><span style="color: #7a3e9d;" class="">StandardMetrics</span><span style="color: #777777;" class="">.</span><span style="color: #7a3e9d;" class="">ms_v_env_heating</span><span style="color: #777777;" class="">-></span><span style="color: #aa3731;font-weight: bold;" class="">AsBool</span><span style="color: #777777;" class="">()</span><span style="color: #333333;" class=""> </span><span style="color: #777777;" class="">||</span><span style="color: #333333;" class=""> </span><span style="color: #7a3e9d;" class="">StandardMetrics</span><span style="color: #777777;" class="">.</span><span style="color: #7a3e9d;" class="">ms_v_env_cooling</span><span style="color: #777777;" class="">-></span><span style="color: #aa3731;font-weight: bold;" class="">AsBool</span><span style="color: #777777;" class="">())</span></div><div class=""><span style="color: #333333;" class=""> </span><span style="color: #777777;" class="">{</span></div><div class=""><span style="color: #333333;" class=""> </span><span style="color: #7a3e9d;" class="">float</span><span style="color: #333333;" class=""> setpoint_float </span><span style="color: #777777;" class="">=</span><span style="color: #333333;" class=""> </span><span style="color: #7a3e9d;" class="">d</span><span style="color: #777777;" class="">[</span><span style="color: #9c5d27;" class="">4</span><span style="color: #777777;" class="">]</span><span style="color: #333333;" class=""> </span><span style="color: #777777;" class="">/</span><span style="color: #333333;" class=""> </span><span style="color: #9c5d27;" class="">2</span><span style="color: #777777;" class="">;</span></div><div class=""><span style="color: #333333;" class=""> </span><span style="color: #7a3e9d;" class="">m_climate_setpoint</span><span style="color: #777777;" class="">-></span><span style="color: #aa3731;font-weight: bold;" class="">SetValue</span><span style="color: #777777;" class="">(</span><span style="color: #333333;" class="">setpoint_float</span><span style="color: #777777;" class="">);</span></div><div class=""><span style="color: #333333;" class=""> </span><span style="color: #777777;" class="">}</span></div></div><p class="">Regards,<br class="">
Jaunius<br class="">
</p>
<div class="moz-cite-prefix">On 2020-02-14 11:11, Mark Webb-Johnson
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:B3EDF4E4-7327-403D-8F3F-E9F57BE0C25E@webb-johnson.net" class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
The ’stale’ system simply sets a flag on the metric - it doesn’t
modify the metric value at all.
<div class=""><br class="">
</div>
<div class="">Auto-stale works by having a timer that is reset
every time the metric is updated. If the timer expires then the
metric is automatically marked as stale.</div>
<div class=""><br class="">
</div>
<div class="">So, to se a metric to zero value, you must have some
code that explicitly does that. Maybe when the climate control
is turned off it sends zero values for set point on the can bus?
In the Tesla Roadster code, I have specific code to ignore
temperature updates when aux12v (used to be ‘awake’) is off - as
I know the updates are not real, and I want the metric to go
stale.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 14 Feb 2020, at 7:33 AM, Jaunius Kapkan
<<a href="mailto:jaunius@gmx.com" class="" moz-do-not-send="true">jaunius@gmx.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div style="font-family: Verdana;font-size: 12.0px;" class="">
<div class="">Hi,</div>
<div class=""> </div>
<div class="">Let me come back to this topic.</div>
<div class="">I have re-made the metrics somewhat
accoding to your recomendations, but I am having an
issue with the setpoint value:</div>
<div class="">
<pre id="output" class=""><strong class="">OVMS#</strong> <kbd class="">metrics list v.e.cab</kbd>
v.e.cabin.fan 6
v.e.cabin.fanlimit 7
v.e.cabin.intake recirc
<strong class=""><span style="background-color:#ffff00;" class="">v.e.cabin.setpoint 28°C
</span></strong>v.e.cabin.vent screen|feet
v.e.cabintemp 0°C
<strong class="">OVMS#</strong> <kbd class="">metrics list v.e.cab</kbd>
v.e.cabin.fan 0
v.e.cabin.fanlimit 7
v.e.cabin.intake unknown
<strong class=""><span style="background-color:#ffff00;" class="">v.e.cabin.setpoint 0°C</span></strong>
v.e.cabin.vent off
v.e.cabintemp 0.5°C</pre>
<div class=""> </div>
<div class=""> bascailly as soon as climate control
is truned off this <span style="background-color:#ffff00;" class="">value</span>
goes back to default. Should I use a different <span style="background-color:#ff8c00;" class="">STALE</span>
parameter?</div>
<div class=""> </div>
<div class="">
<div class="">
<div class="">m_climate_setpoint =
MyMetrics.InitFloat("v.e.cabin.setpoint", <span style="background-color:#ff8c00;" class="">SM_STALE_NONE</span>,
0, Celcius);</div>
</div>
</div>
</div>
<div class="">
<div class="">
<div class="">Regards,</div>
<div class="">Jaunius</div>
<div class=""> </div>
<div name="quote" style="margin:10px 5px 5px 10px;
padding: 10px 0 10px 10px; border-left:2px solid
#C3D9E5; word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class="">
<div style="margin:0 0 10px 0;" class=""><b class="">Sent:</b> Monday, November 11, 2019
at 7:51 AM<br class="">
<b class="">From:</b> "Mark Webb-Johnson" <<a href="mailto:mark@webb-johnson.net" class="" moz-do-not-send="true">mark@webb-johnson.net</a>><br class="">
<b class="">To:</b> "OVMS Developers" <<a href="mailto:ovmsdev@lists.openvehicles.com" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a>><br class="">
<b class="">Subject:</b> Re: [Ovmsdev] Nissan
LEAF: HVAC Metrics</div>
<div name="quoted-content" class="">
<div class="">
<div class=""> </div>
I will look into this, and let you know. The
fan speeds, etc, can normally be represented
as a percentage of maximum (to make it
easier for Apps).
<div class=""> </div>
<div class="">Can you explain what your car
offers, and what the proposed settings
are:</div>
<div class=""> </div>
<div class="">
<ul class="MailOutline">
<li class="">v.e.cabin.fan 0-100% (cabin
fan speed)</li>
<li class="">v.e.cabin.setpoint 999C
(cabin temperature set point)</li>
<li class="">v.e.cabin.intake
fresh/recirc (cabin air intake mode)</li>
<li class="">v.e.cabin.vent feet | face
| screen (or comma-separated list)</li>
</ul>
<div class=""> </div>
<div class="">But not sure what remotecool
and remoteheat are?</div>
<div class=""> </div>
<div class="">Does that match other car’s
capabilities? Or suggestions for more?</div>
<div class=""> </div>
<div class="">Regards, Mark.
<div class="">
<blockquote class="">
<div class="">On 11 Nov 2019, at
5:15 AM, Jaunius Kapkan <<a href="mailto:jaunius@gmx.com" target="_blank" class="" moz-do-not-send="true">jaunius@gmx.com</a>>
wrote:</div>
<div class="">
<div class="">
<div style="font-family:
Verdana;font-size: 12.0px;" class="">
<div class="">Hi,</div>
<div class=""> </div>
<div class="">While doing Leaf
HVAC/Climate Control Metrics
I tought it would make sense
to put them under v.e. or a
new climate category like
v.h or <a href="http://v.cc/" target="_blank" class="" moz-do-not-send="true">v.cc</a>
and agree on general metrics
that would be used by all
cars.</div>
<div class="">Such as:</div>
<div class="">v.e.fan.speed 6<br class="">
v.e.remotecool no<br class="">
v.e.remoteheat yes<br class="">
v.e.setpoint 21°C<br class="">
v.e.intake def/fresh/recirc<br class="">
v.e.vent
def/def-feet/face/face-feet/feet</div>
<div class=""> </div>
<div class="">Then later it
would be much easier to make
them visible in an app.</div>
<div class="">Also
"maxfanspeed" could be added
to the config so that the
GUI could take the required
amount of bars for each car.</div>
<div class=""> </div>
<div class="">Regards,</div>
<div class="">Jaunius</div>
<div class="">
<div style="margin: 10.0px
5.0px 5.0px
10.0px;padding: 10.0px 0
10.0px 10.0px;border-left:
2.0px solid
rgb(195,217,229);" class="">
<div style="margin: 0 0
10.0px 0;" class=""><b class="">Sent:</b> Monday,
November 04, 2019 at
1:09 PM<br class="">
<b class="">From:</b> "Jaunius
Kapkan" <<a href="mailto:jaunius@gmx.com" target="_blank" class="" moz-do-not-send="true">jaunius@gmx.com</a>><br class="">
<b class="">To:</b> "OVMS
Developers" <<a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a>><br class="">
<b class="">Subject:</b> [Ovmsdev]
Nissan LEAF: HVAC
Metrics</div>
<div class="">
<div class="">
<div class="">
<div class="">Hi,
<div class=""> </div>
<div class="">I
have enhanced
Nissan LEAF HVAC
metrics as well
as added
additional ones
under <a href="http://xnl.cc/" target="_blank" class="" moz-do-not-send="true">xnl.cc</a></div>
<div class=""> </div>
<div class="">I
have built and
tested the
changes and so
far all works as
intended.</div>
<div class=""> </div>
<div class="">I
have also
updated
documentation.</div>
<div class=""> </div>
<div class="">So I
think it is time
to merge this in
to current edge
build, but I
just wanted to
check with you
if all the code
style and naming
conventios are
according to
standards.</div>
<div class=""> </div>
<div class="">Would
appreciate if
someone could
review and
advise if
something needs
to be corrected.</div>
<div class=""> </div>
<div class="">Here
is the link to
the repo and
main file I
worked on: <a href="https://github.com/mjkapkan/Open-Vehicle-Monitoring-System-3/commits/master/vehicle/OVMS.V3/components/vehicle_nissanleaf/src/vehicle_nissanleaf.cpp" target="_blank" class="" moz-do-not-send="true">https://github.com/mjkapkan/Open-Vehicle-Monitoring-System-3/commits/master/vehicle/OVMS.V3/components/vehicle_nissanleaf/src/vehicle_nissanleaf.cpp</a></div>
<div class=""><br class="">
Kindly,
<div class="">
<div class=""> </div><p class="MsoNormal"><b class=""><span class="">Jaunius
Kapkan </span></b><i class="">[Sent
from
cellphone]</i></p><p class="MsoNormal"><span class="">Global
Market
Operations</span></p><p class="MsoNormal"><span class=""><span class="">Cell:
</span><span class=""> </span><span class=""> <a class="" moz-do-not-send="true">+370 650
11 752</a></span></span></p>
</div>
<div class="">
<blockquote class="">On
2019-10-17, at
15:14, Jaunius
Kapkan <<a href="mailto:jaunius@gmx.com" target="_blank" class="" moz-do-not-send="true">jaunius@gmx.com</a>>
wrote:<br class="">
</blockquote>
</div>
<blockquote class="">
<div class="">
<div style="font-family:
Verdana;font-size: 12.0px;" class="">
<div class="">Thanks
Mark,</div>
<div class=""> </div>
<div class="">[renaming
subject]</div>
<div class=""> </div>
<div class="">In
regards to
config store.
Where would
you recommend
placing the
timers? I was
thinking about
putting them
under vehicle
conf:</div>
<div class="">
<pre id="output" class=""><strong class="">OVMS#</strong> <kbd class="">config list vehicle</kbd>
vehicle (readable writeable)
bms.alerts.enabled: yes
bms.dev.temp.alert:
bms.dev.temp.warn:
bms.dev.voltage.alert:
bms.dev.voltage.warn:
cctimer.evening: 1715-1730
cctimer.morning: 0800-0815
id: ******
minsoc: 20
name:
timezone: EET-2EEST,M3.5.0/3,M10.5.0/4
timezone_region: Europe/Helsinki
units.distance: K</pre>
</div>
<div class="">Any
other
suggestions?</div>
<div class=""> </div>
<div class="">Regards,</div>
<div class="">Jaunius</div>
<div class="">
<div style="margin:
10.0px 5.0px
5.0px
10.0px;padding:
10.0px 0
10.0px
10.0px;border-left:
2.0px solid
rgb(195,217,229);" class="">
<div style="margin:
0 0 10.0px 0;" class=""><b class="">Sent:</b> Monday,
October 14,
2019 at 4:01
AM<br class="">
<b class="">From:</b> "Mark
Webb-Johnson"
<<a href="mailto:mark@webb-johnson.net" target="_blank" class="" moz-do-not-send="true">mark@webb-johnson.net</a>><br class="">
<b class="">To:</b> "OVMS
Developers"
<<a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a>><br class="">
<b class="">Subject:</b> Re:
[Ovmsdev]
WifiConsole
V1.0</div>
<div class="">
<div class="">Probably
not. The
majority of
power
consumption is
from the
modems
(cellular and
wifi).
<div class=""> </div>
<div class="">Regards,
Mark</div>
<div class=""> </div>
<div class="">P.S.
If all you
need is a 10
second
notification,
you can pubsub
subscribe to
the standard
event
ticker.10.</div>
<div class="">
<div class="">
<blockquote class="">
<div class="">On
14 Oct 2019,
at 7:22 AM,
Jaunius Kapkan
<<a href="mailto:jaunius@gmx.com" target="_blank" class="" moz-do-not-send="true">jaunius@gmx.com</a>>
wrote:</div>
<div class="">
<div class="">
<div style="font-family:
Verdana;font-size: 12.0px;" class="">
<div class="">
<div class="">Delayed
events seem to
be working
fine, thanks
for the
examples!</div>
<div class="">However,
do you think
spamming the
events API
every 10
seconds might
substantially
increase power
consumption?</div>
<div class="">
<div class=""> </div>
<div class="">
<ul id="eventlog" class="">
<li class=""><code class="">[2:17:04
AM]</code>usr.CCtimer.heartbeat</li>
<li class=""><code class="">[2:17:04
AM]</code>usr.CCtimer.Night.stopped</li>
<li class=""><code class="">[2:17:14
AM]</code>usr.CCtimer.heartbeat</li>
</ul>
</div>
<div class="">Regards,</div>
<div class="">Jaunius</div>
<div style="margin:
10.0px 5.0px
5.0px
10.0px;padding:
10.0px 0
10.0px
10.0px;border-left:
2.0px solid
rgb(195,217,229);" class="">
<div style="margin:
0 0 10.0px 0;" class=""><b class="">Sent:</b> Sunday,
October 13,
2019 at 8:54
PM<br class="">
<b class="">From:</b> "Michael
Balzer" <<a href="mailto:dexter@expeedo.de" target="_blank" class="" moz-do-not-send="true">dexter@expeedo.de</a>><br class="">
<b class="">To:</b> <a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a><br class="">
<b class="">Subject:</b> Re:
[Ovmsdev]
WifiConsole
V1.0</div>
<div class="">Sending
notifications
is now also
supported
directly:<br class="">
<br class="">
<a href="https://docs.openvehicles.com/en/latest/userguide/scripting.html#ovmsnotify" target="_blank" class="" moz-do-not-send="true">https://docs.openvehicles.com/en/latest/userguide/scripting.html#ovmsnotify</a><br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 13.10.19 um
16:09 schrieb
Jaunius
Kapkan:<br class="">
> Great,<br class="">
><br class="">
> Will try
that out!<br class="">
><br class="">
> Regards,<br class="">
> Jaunius<br class="">
><br class="">
>> Sent:
Sunday,
October 13,
2019 at 11:20
AM<br class="">
>> From:
"Michael
Balzer" <<a href="mailto:dexter@expeedo.de" target="_blank" class="" moz-do-not-send="true">dexter@expeedo.de</a>><br class="">
>> To: <a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a><br class="">
>>
Subject: Re:
[Ovmsdev]
WifiConsole
V1.0<br class="">
>><br class="">
>>
Jaunius,<br class="">
>><br class="">
>> I've
added
scheduled
(delayed)
events &
the native
OvmsEvents
API:<br class="">
>> <a href="https://docs.openvehicles.com/en/latest/userguide/scripting.html#internal-objects-and-functions-methods" target="_blank" class="" moz-do-not-send="true">https://docs.openvehicles.com/en/latest/userguide/scripting.html#internal-objects-and-functions-methods</a><br class="">
>><br class="">
>> So
you can now
also implement
millisecond
resolution
timeouts and
intervals in
scripts.<br class="">
>><br class="">
>>
Regards,<br class="">
>>
Michael<br class="">
>><br class="">
>><br class="">
>> Am
11.10.19 um
10:36 schrieb
Jaunius
Kapkan:<br class="">
>>>
Thanks
Michael,<br class="">
>>> <br class="">
>>> 1
second will do
just fine as
this is for
climate
control timer
plugin I'm
doing. Will
try to use
that event
listener. Of
course some
standartized
way would<br class="">
>>>
be better.<br class="">
>>> <br class="">
>>>
Regards,<br class="">
>>>
Jaunius<br class="">
>>> <br class="">
>>>
*Sent:* Friday,
October 11,
2019 at 8:48
AM<br class="">
>>>
*From:* "Michael
Balzer" <<a href="mailto:dexter@expeedo.de" target="_blank" class="" moz-do-not-send="true">dexter@expeedo.de</a>><br class="">
>>>
*To:* <a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a><br class="">
>>>
*Subject:* Re:
[Ovmsdev]
WifiConsole
V1.0<br class="">
>>>
Jaunius,<br class="">
>>><br class="">
>>>
setTimeout()
is not a
standard
Javascript
function, it's
a method of
the browser
window object.<br class="">
>>><br class="">
>>> <a href="https://developer.mozilla.org/de/docs/Web/API/WindowTimers/setTimeout" target="_blank" class="" moz-do-not-send="true">https://developer.mozilla.org/de/docs/Web/API/WindowTimers/setTimeout</a><br class="">
>>><br class="">
>>>
As a
workaround,
subscribe to
the "ticker.1"
event as shown
in the
foglight
example:<br class="">
>>><br class="">
>>> <a href="http://docs.openvehicles.com/en/latest/components/ovms_script/docs/foglight.html#listen-to-events" target="_blank" class="" moz-do-not-send="true">http://docs.openvehicles.com/en/latest/components/ovms_script/docs/foglight.html#listen-to-events</a><br class="">
>>><br class="">
>>>
Resolution is
limited to 1
second though.
I thought
about
scheduled
events some
time ago, i.e.
being able to
tell the event
system to
trigger an
event after a<br class="">
>>>
specific
delay. That
would also
offer a clean
& simple
solution for
this. Another
option would
be a script
API for the
timer service.<br class="">
>>><br class="">
>>>
I'll have a
look at
scheduled
events.<br class="">
>>><br class="">
>>>
Regards,<br class="">
>>>
Michael<br class="">
>>><br class="">
>>> <br class="">
>>>
Am 11.10.19 um
08:29 schrieb
Jaunius
Kapkan:<br class="">
>>><br class="">
>>>
Thanks Mark,<br class="">
>>> <br class="">
>>>
One other
thing I
stumbled upon
is that
standard setTimeout()
does not seem
to work. Is
there any
workaround for
this? Sample
Code:<br class="">
>>><br class="">
>>>
|function
intervalFunc()
{ print('Next
try in 1.5s')
}
setInterval(intervalFunc,
1500)|<br class="">
>>><br class="">
>>> <br class="">
>>>
Basically I
need the
script to
check certain
conditions
each n
seconds.<br class="">
>>> <br class="">
>>>
Regards,<br class="">
>>>
Jaunius<br class="">
>>>
*Sent:* Thursday,
October 10,
2019 at 3:35
AM<br class="">
>>>
*From:* "Mark
Webb-Johnson"
<<a href="mailto:mark@webb-johnson.net" target="_blank" class="" moz-do-not-send="true">mark@webb-johnson.net</a>><br class="">
>>>
*To:* "OVMS
Developers"
<<a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a>><br class="">
>>>
*Subject:* Re:
[Ovmsdev]
WifiConsole
V1.0<br class="">
>>> I
think in v2
that could
have been the
case (as we
didn’t have
any
standardised
functions for
things like
climate
control). But
in the v3
architecture
we<br class="">
>>>
now have these
and the
vehicle
modules should
support the
standard
functions to
the best of
their
abilities.<br class="">
>>><br class="">
>>>
If we still
need mappings
like Homelink
1 ->
Climate On,
then that
should be done
either by
scripts or by
some
centralised
mapping
framework.<br class="">
>>><br class="">
>>>
Regards, Mark.<br class="">
>>><br class="">
>>>
> On 9 Oct
2019, at 2:19
PM, Jaunius
Kapkan <<a href="mailto:jaunius@gmx.com" target="_blank" class="" moz-do-not-send="true">jaunius@gmx.com</a>>
wrote:<br class="">
>>>
><br class="">
>>>
> I am
making a
couple of
plugins
(initially for
leaf) and the
JS functions
are great for
that. However
I assume the
functions are
not unifed
accross<br class="">
>>>
different
vehicles. For
example for
leaf to turn
on pre-heat
you need to
issue Homelink
1 instead of
ClimateControl.
What would be
the best way
to change<br class="">
>>>
this? Or is
this something
that need to
be changed on
the lower
level?<br class="">
>>>
><br class="">
>>>
>
Greetings,<br class="">
>>>
> Jaunius<br class="">
>>>
><br class="">
>>>
>> Sent:
Tuesday,
October 08,
2019 at 9:05
AM<br class="">
>>>
>> From:
"Michael
Balzer" <<a href="mailto:dexter@expeedo.de" target="_blank" class="" moz-do-not-send="true">dexter@expeedo.de</a>><br class="">
>>>
>> To: <a href="mailto:ovmsdev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">ovmsdev@lists.openvehicles.com</a><br class="">
>>>
>>
Subject: Re:
[Ovmsdev]
WifiConsole
V1.0<br class="">
>>>
>><br class="">
>>>
>> Mark,<br class="">
>>>
>><br class="">
>>>
>> yes,
the OLEDs are
perfect for
these things,
bright enough
for daylight
use with very
little energy
usage.<br class="">
>>>
>><br class="">
>>>
>>
Thanks for the
link to that
combined ESP32
module, that's
a real beauty,
even includes
a LiPo supply
/ charger. I
need to check
that one out.<br class="">
>>>
>><br class="">
>>>
>>
Regarding our
Javascript
support, I
already had
stunned some
users with the
foglight
plugin, they
thought stuff
like this
would need
builtin<br class="">
>>>
>>
support. That
brought me
back to my
point about
how little
users know
about our
capabilities,
so I added an
explanation to
our docs:<br class="">
>>>
>><br class="">
>>>
>> <a href="http://docs.openvehicles.com/en/latest/components/ovms_script/docs/foglight.html" target="_blank" class="" moz-do-not-send="true">http://docs.openvehicles.com/en/latest/components/ovms_script/docs/foglight.html</a><br class="">
>>>
>><br class="">
>>>
>> But
we really need
something like
an OVMS cheat
sheet as an
overview of
what is
possible.<br class="">
>>>
>><br class="">
>>>
>>
Regards,<br class="">
>>>
>>
Michael<br class="">
>>>
>><br class="">
>>>
>><br class="">
>>>
>> Am
08.10.19 um
05:40 schrieb
Mark
Webb-Johnson:<br class="">
>>>
>>>
Michael,<br class="">
>>>
>>><br class="">
>>>
>>> I
really like
those little
OLED SSD1306
based
displays. I
use them on my
esphome+hassio
projects like
this little
water tank
level (using
an<br class="">
>>>
>>>
ESP32, a
BME280
pressure/humidity/temperature
sensor,
waterproof
ultrasonic
distance
sensor, and
SSID1306 OLED
yellow/blue
display):<br class="">
>>>
>>><br class="">
>>>
>>><br class="">
>>>
>>>
Adding a
display to a
project makes
it so much
more useful
and easy to
diagnose
problems.<br class="">
>>>
>>><br class="">
>>>
>>>
AliExpress has
them very
cheap:<br class="">
>>>
>>><br class="">
>>>
>>> *
<a href="https://www.aliexpress.com/item/32844104782.html" target="_blank" class="" moz-do-not-send="true">https://www.aliexpress.com/item/32844104782.html</a><br class="">
>>>
>>>
US$2 for the
0.96”
yellow/blue
128x32<br class="">
>>>
>>>
US$3 for the
1.3” white
128x64<br class="">
>>>
>>><br class="">
>>>
>>><br class="">
>>>
>>>
There is also
a 4MB ESP32
with a 0.96”
OLED display
on-board:<br class="">
>>>
>>><br class="">
>>>
>>> *
<a href="https://www.aliexpress.com/item/32822105291.html" target="_blank" class="" moz-do-not-send="true">https://www.aliexpress.com/item/32822105291.html</a><br class="">
>>>
>>>
US$9 plus
shipping<br class="">
>>>
>>><br class="">
>>>
>>><br class="">
>>>
>>>
Glad that you
are finding a
use for our
JavaScript
support. I
really think
that has so
many
possibilities.<br class="">
>>>
>>><br class="">
>>>
>>>
Regards, Mark<br class="">
>>>
>>><br class="">
>>>
>>>>
On 6 Oct 2019,
at 10:43 PM,
Michael Balzer
<<a href="mailto:dexter@expeedo.de" target="_blank" class="" moz-do-not-send="true">dexter@expeedo.de</a>
<<a href="mailto:dexter@expeedo.de" target="_blank" class="" moz-do-not-send="true">mailto:dexter@expeedo.de</a>>>
wrote:<br class="">
>>>
>>>><br class="">
>>>
>>>>
FYI: I've just
implemented an
OVMS v3 style
replacement
for the
SimpleConsole:<br class="">
>>>
>>>><br class="">
>>>
>>>>
<a href="https://github.com/dexterbg/WifiConsole" target="_blank" class="" moz-do-not-send="true">https://github.com/dexterbg/WifiConsole</a><br class="">
>>>
>>>><br class="">
>>>
>>>>
V3 makes it
pretty easy
now to add
stuff like
this. It's
using a script
plugin to
provide custom
functions via
the web API.<br class="">
>>>
>>>><br class="">
>>>
>>>>
Regards,<br class="">
>>>
>>>>
Michael<br class="">
>>>
>><br class="">
>>>
>> --<br class="">
>>>
>>
Michael Balzer
* Helkenberger
Weg 9 *
D-58256
Ennepetal<br class="">
>>>
>> Fon
02333 / 833
5735 * Handy
0176 / 206 989
26<br class="">
>>>
>><br class="">
>>>
>>
_______________________________________________<br class="">
>>>
>>
OvmsDev
mailing list<br class="">
>>>
>> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
>>>
>> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>>>
>><br class="">
>>>
>
_______________________________________________<br class="">
>>>
> OvmsDev
mailing list<br class="">
>>>
> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
>>>
> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>>><br class="">
>>>
_______________________________________________<br class="">
>>>
OvmsDev
mailing list<br class="">
>>> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
>>> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>>> <br class="">
>>> <br class="">
>>><br class="">
>>>
_______________________________________________<br class="">
>>>
OvmsDev
mailing list<br class="">
>>> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
>>> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>>><br class="">
>>> <br class="">
>>>
--<br class="">
>>>
Michael Balzer
* Helkenberger
Weg 9 *
D-58256
Ennepetal<br class="">
>>>
Fon 02333 /
833 5735 *
Handy 0176 /
206 989 26<br class="">
>>>
_______________________________________________
OvmsDev
mailing list <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>>><br class="">
>>>
_______________________________________________<br class="">
>>>
OvmsDev
mailing list<br class="">
>>> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
>>> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>> --<br class="">
>>
Michael Balzer
* Helkenberger
Weg 9 *
D-58256
Ennepetal<br class="">
>> Fon
02333 / 833
5735 * Handy
0176 / 206 989
26<br class="">
>><br class="">
>>
_______________________________________________<br class="">
>>
OvmsDev
mailing list<br class="">
>> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
>> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
>><br class="">
>
_______________________________________________<br class="">
> OvmsDev
mailing list<br class="">
> <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
> <a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
<br class="">
--<br class="">
Michael Balzer
* Helkenberger
Weg 9 *
D-58256
Ennepetal<br class="">
Fon 02333 /
833 5735 *
Handy 0176 /
206 989 26<br class="">
<br class="">
_______________________________________________<br class="">
OvmsDev
mailing list<br class="">
<a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
OvmsDev
mailing list<br class="">
<a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</blockquote>
</div>
</div>
_______________________________________________ OvmsDev mailing list <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</div>
</div>
</div>
</div>
<span class="">_______________________________________________</span><br class="">
<span class="">OvmsDev
mailing list</span><br class="">
<span class=""><a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a></span><br class="">
<span class=""><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></span></div>
</blockquote>
</div>
</div>
</div>
_______________________________________________ OvmsDev mailing list <a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a href="mailto:OvmsDev@lists.openvehicles.com" target="_blank" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</blockquote>
</div>
</div>
</div>
_______________________________________________ OvmsDev mailing list <a href="mailto:OvmsDev@lists.openvehicles.com" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" target="_blank" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a href="mailto:OvmsDev@lists.openvehicles.com" class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>