<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Greg,<br>
<br>
so you did get it to work on Android 7 & 8? Or was it just the
ZeroConf App that showed the mDNS registry info?<br>
<br>
ZeroConf shows the device on my Android phone (7) and tablet (6) as
well, but both are unable to resolve the host name in all other
Apps. Have you installed something along with the App or done some
additional config?<br>
<br>
Without a moduleid, the mDNS hostname defaults to "ovms.local",
which is of course much easier to type than an IP address. We need
to mention both options in the user guide, but we could recommend
first trying "ovms.local" for the platforms supporting ZeroConf.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 07.03.2018 um 05:28 schrieb Greg D.:<br>
</div>
<blockquote type="cite"
cite="mid:71ce6835-f971-f079-6de1-7f6cfb45cd66@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Ha! Change what I said... Must not have waited long enough. As
you did, simply joining the AP, the 'Service Browser' app
eventually did discover the module at 192.168.4.1, with my car's
ID. The 'ZeroConf Browser' app had a problem with it (said there
was something there, but no information). This on both my phone
(Android 8.1) and tablet (Android 7.0).<br>
<br>
Of course, since my phone got a 192.168.4.2 IP Address, it wasn't
too hard to guess where the module was.<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:193C9CF2-8A0F-4959-BDAE-1A92C4F98D6A@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
It does work on my iOS devices.
<div class=""><br class="">
</div>
<div class="">For the module in my car, I’m currently using an
iPad. I join the Access Point, then ssh to
<vehicleid>.local. Web browsing to that address works as
well.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 7 Mar 2018, at 10:29 AM, Greg D. <<a
href="mailto:gregd2350@gmail.com" class=""
moz-do-not-send="true">gregd2350@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""> Yeah,
probably more complicated and proprietary than we
need. Just need to put 192.168.4.1 in the manual,
after all. Done.<br class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br
class="">
</div>
<blockquote type="cite"
cite="mid:E41C89F7-0161-458E-80A2-715A71B6D223@webb-johnson.net"
class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
From my understanding, Zeroconf / mDNS rely on a
pre-existing IP network. They don’t address the wifi
side of things at all.
<div class=""><br class="">
</div>
<div class="">There are some approaches to dealing
with simplifying wifi configuration (involving
flashing lights, bluetooth adverts, etc), but they
are all proprietary. Espressif has one called
ESP-TOUCH (aka Smart Config):</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none;
padding: 0px;" class="">
<div class=""><a
href="https://www.espressif.com/en/products/software/esp-touch/overview"
class="" moz-do-not-send="true">https://www.espressif.com/en/products/software/esp-touch/overview</a></div>
</blockquote>
<div class="">
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 7 Mar 2018, at 7:24 AM, Greg
D. <<a href="mailto:gregd2350@gmail.com"
class="" moz-do-not-send="true">gregd2350@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi Michael,<br class="">
<br class="">
I trying to figure out how Zeroconf is
supposed to work, given the<br class="">
networking services that the module
currently supports. Perhaps I don't<br
class="">
understand mDNS well enough, but don't we
need some means to broadcast<br class="">
our presence, separate from the network?<br
class="">
<br class="">
I was able to run the ZeroConf Browser on
my Android phone (Google<br class="">
Pixel2, latest code), and it did discover
the module. But that was only<br class="">
when the module and phone were both
connected by wifi to the home<br class="">
network. When it was running in AP mode,
with the phone connected to<br class="">
the home network, there is no way for the
phone to see the mDNS service<br class="">
announcement packets. <br class="">
<br class="">
I did a wireless trace of the wifi
beacons, thinking it might be<br class="">
broadcast in there, but didn't find
anything service-oriented other than<br
class="">
the usual stuff. The only wifi adapter
that I could get to cooperate<br class="">
with me today was a really old one
(11b-only), so perhaps there's<br class="">
something at an 11g/n level that I can't
see? <br class="">
<br class="">
I'm thinking we need some out-of-band
channel for the broadcasts, for<br
class="">
example, Bluetooth. Isn't there a service
there for this purpose? How<br class="">
is this supposed to work? <br class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
Michael Balzer wrote:<br class="">
<blockquote type="cite" class="">Zeroconf
/ mDNS allows to address the module
using the name "<moduleid>.local",
but is not supported on all systems. It
should work on iOS, but I can't test<br
class="">
that. It doesn't work on Android 7, so
is not usable as a general solution.<br
class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a
href="mailto:OvmsDev@lists.teslaclub.hk"
class="" moz-do-not-send="true">OvmsDev@lists.teslaclub.hk</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre class="" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk" moz-do-not-send="true">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br
class="">
OvmsDev mailing list<br class="">
<a href="mailto:OvmsDev@lists.teslaclub.hk" class=""
moz-do-not-send="true">OvmsDev@lists.teslaclub.hk</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk" moz-do-not-send="true">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/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>