<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I've found the issue: gradle build variables don't work correctly
anymore. I need to set the target SDK version manually on both
modules.<br>
<br>
Sharkcow, I'll merge your PR and do the changes I suggested.<br>
<br>
<br>
<div class="moz-cite-prefix">Am 28.12.20 um 19:57 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite"
cite="mid:3d18c5e4-e3dd-5f32-2f80-cb301fb544e0@expeedo.de">Sharkcow,
<br>
<br>
according to your PR you want to add the service interval info to
the "S" (status) message. IMO that's not the most appropriate
place. I'd rather add this to the "F" message, as that's already
carrying the VIN, and also is meant to be updated less frequently.
<br>
<br>
Also, we should pass through new fields to the Intent broadcast by
default, to avoid stumbling upon missing fields as with the HVAC.
So please add the respective puts to getBroadcastData().
<br>
<br>
Can you do these changes short term?
<br>
<br>
Regards,
<br>
Michael
<br>
<br>
<br>
Am 28.12.20 um 18:36 schrieb sharkcow:
<br>
<blockquote type="cite">bad news for some might be good news for
others... maybe that way my
<br>
recent pull request has a chance of making it into the next
version? :)
<br>
<br>
Thanks,
<br>
<br>
sharkcow
<br>
<br>
<br>
Am 28.12.20 um 18:13 schrieb Michael Balzer:
<br>
<blockquote type="cite">Chris,
<br>
<br>
I thought "of course, should be a matter of minutes"… and
*zapp* came
<br>
Google along. It doesn't let me upload the new APK, keeps
telling me it
<br>
needs to be targeted for API 29, which it is built for
according to
<br>
Android Studio, but apparently the APK manifest keeps API 28
despite all
<br>
my config efforts. I'll need to spend some more hours
investigating
<br>
this… *sigh*
<br>
<br>
Regards,
<br>
Michael
<br>
<br>
<br>
Am 28.12.20 um 16:54 schrieb Chris van der Meijden:
<br>
<blockquote type="cite">Cool ...
<br>
<br>
Could you perhaps compile a 3.17.3 with that one?
<br>
<br>
Would also give me the new images "officially" :-)
<br>
<br>
Thanx
<br>
<br>
Chris
<br>
<br>
<br>
Am Montag, den 28.12.2020, 16:31 +0100 schrieb Michael
Balzer:
<br>
<blockquote type="cite">Done.
<br>
<br>
Am 28.12.20 um 16:26 schrieb Michael Balzer:
<br>
<blockquote type="cite">Chris,
<br>
<br>
nice :-)
<br>
<br>
Just checked: the App doesn't yet transmit the HVAC flag
via the
<br>
update intent, but that's really simple to add. I'll do
that right now.
<br>
<br>
Regards,
<br>
Michael
<br>
<br>
<br>
Am 28.12.20 um 14:53 schrieb Chris van der Meijden:
<br>
<blockquote type="cite">The app is up and running.
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/devmarxx/OVMS-Fireplace">https://github.com/devmarxx/OVMS-Fireplace</a>
<br>
<br>
This is still very, very beta. It just does what it
needs to do,
<br>
without any checks on user entries or responses from
the vehicle.
<br>
<br>
But it works and makes me smile :-))
<br>
<br>
Regards
<br>
<br>
Chris
<br>
<br>
<br>
Am Montag, den 28.12.2020, 11:15 +0100 schrieb Michael
Balzer:
<br>
<blockquote type="cite">Chris,
<br>
<br>
TL;DR: simply add the command to execute after the
"7," intro, e.g.
<br>
"7,climatecontrol on".
<br>
<br>
The SendCommand API was built around the V2 message
protocol, so you
<br>
need to send commands as MP commands, see
<br>
<a class="moz-txt-link-freetext" href="https://docs.openvehicles.com/en/latest/protocol_v2/commands.html">https://docs.openvehicles.com/en/latest/protocol_v2/commands.html</a> for
<br>
a
<br>
list. MP command code 7 passes standard text (former
SMS) commands
<br>
to
<br>
the shell, that's what the Wiki example shows (for
V2 command
<br>
"STAT?").
<br>
<br>
You can get the command response by listening to the
CommandResult
<br>
intent and reading the "cmd_data" extra. Be aware
all command result
<br>
will be sent as intents, so you need to check if a
result matches
<br>
your
<br>
command (could possibly be improved if needed).
<br>
<br>
Regards,
<br>
Michael
<br>
<br>
<br>
Am 28.12.20 um 10:34 schrieb Chris van der Meijden:
<br>
<blockquote type="cite">I'm writing a little Android
app with Cordova to do something
<br>
similar
<br>
as Tesla's "Romance mode". The app will turn
climate control on or
<br>
off
<br>
and will show a burning log fire while the car is
heating.
<br>
<br>
As cordova uses HTML and Javascript you can see an
online preview
<br>
here:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.arachnon.de/fire/test.html">http://www.arachnon.de/fire/test.html</a>
<br>
<br>
When you click or tap on the fireplace the
countdown for turning
<br>
"climatecontrol" on ticks down for 17 seconds.
After that the fire
<br>
starts "moving" and on webkit browsers you will
hear a tickling
<br>
sound.
<br>
When you click or tap again the tickling will stop
and you will get
<br>
a
<br>
static image again. You will also get a red bar
for 10 seconds,
<br>
turning
<br>
"climatecontrol" off and blocking any new commands
for those 10
<br>
seconds.
<br>
<br>
When you click or tap on the yellow bar you will
be able to store
<br>
your
<br>
OVMS credentials (vehicle ID and password). Cave:
this is done in
<br>
plain
<br>
text with window.localstorage so the password will
be plain
<br>
readable
<br>
from the local storage within the browser on your
device.
<br>
<br>
The credentials are needed to communicate with the
Android OVMS
<br>
app, as
<br>
I am planning to use the "SendCommand Broadcast
Intent data"
<br>
functionality of the OVMS app. I should be able to
do that via this
<br>
cordova plugin:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/cordova-misc/cordova-webintent">https://github.com/cordova-misc/cordova-webintent</a>
<br>
<br>
I read the OVMS "SendCommand Broadcast Intent
data" documentation
<br>
here:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/openvehicles/Open-Vehicle-Android/wiki/SendComma">https://github.com/openvehicles/Open-Vehicle-Android/wiki/SendComma</a> <br>
nd-B
<br>
roadcast-Intent-data
<br>
<br>
but it is not clear to me, how I can initiate the
"climatecontrol
<br>
on"
<br>
shell command over the broadcast. So would like to
ask for help on
<br>
that
<br>
:-)
<br>
<br>
Once the app is up and running it should be usable
for any vehicle
<br>
with
<br>
OVMS climate control implemented.
<br>
<br>
Just a little gimmick. But fun :-))
<br>
<br>
Regards
<br>
<br>
Chris
<br>
<br>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
<br>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:OvmsDev@lists.openvehicles.com"><mailto:OvmsDev@lists.openvehicles.com></a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
-- <br>
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
<br>
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
<br>
<br>
<br>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
<br>
</blockquote>
_______________________________________________
<br>
OvmsDev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
<br>
<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>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>