[Ovmsdev] 3.0.991

Thu Mar 8 23:33:01 HKT 2018

Greg,

there are better Apps than ZeroConf browser to list mDNS services, that also offer opening in a browser without needing to copy&paste the IP.

For example: https://play.google.com/store/apps/details?id=jp.deci.tbt.andro.bonjoursearch

Actually mDNS _is_ supported by the Android libs, it's just not in the resolver, so is not available for Apps that don't implement it explicitly. Stupid decision.

Regards,
Michael

Am 07.03.2018 um 22:43 schrieb Greg D.:
> Hi Michael,
>
> Yes.  ZeroConf Browser used to be my default mDNS scanner, but I thought to try another, and that one worked.  The app is "Service Browser" by Andriy Druk. 
> And, it's open source.  But, I wouldn't call the system all that robust; tried it again today, and it took a long time for the new software to stop spinning
> and to reveal something.  During that time, the old software was reporting no services, as it did when I first tried it.  Overall, a lot quicker and more
> reliable to read the (presumed) OVMS documentation and follow the instructions to 192.168.4.1...
>
> But when it finally worked, it worked on both Android 7 & 8.1.  I didn't try to go to the text name, only the revealed IP address, which the app conveniently
> can copy to the phone's clipboard for pasting into the browser address line.  Trying"ovms.local" today didn't work at all, with either Chrome or Firefox. 
> Neither could find it, and both ran off to search for it on the Web.  {sigh}
>
> Greg
>
>
> Michael Balzer wrote:
>> Greg,
>>
>> so you did get it to work on Android 7 & 8? Or was it just the ZeroConf App that showed the mDNS registry info?
>>
>> 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?
>>
>> 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.
>>
>> Regards,
>> Michael
>>
>>
>> Am 07.03.2018 um 05:28 schrieb Greg D.:
>>> 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).
>>>
>>> Of course, since my phone got a 192.168.4.2 IP Address, it wasn't too hard to guess where the module was.
>>>
>>> Greg
>>>
>>>
>>> Mark Webb-Johnson wrote:
>>>> It does work on my iOS devices.
>>>>
>>>> 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.
>>>>
>>>> Regards, Mark.
>>>>
>>>>> On 7 Mar 2018, at 10:29 AM, Greg D. <gregd2350 at gmail.com <mailto:gregd2350 at gmail.com>> wrote:
>>>>>
>>>>> Yeah, probably more complicated and proprietary than we need.  Just need to put 192.168.4.1 in the manual, after all.  Done.
>>>>>
>>>>> Greg
>>>>>
>>>>>
>>>>> Mark Webb-Johnson wrote:
>>>>>> From my understanding, Zeroconf / mDNS rely on a pre-existing IP network. They don’t address the wifi side of things at all.
>>>>>>
>>>>>> 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):
>>>>>>
>>>>>>     https://www.espressif.com/en/products/software/esp-touch/overview
>>>>>>
>>>>>>
>>>>>> Regards, Mark.
>>>>>>
>>>>>>> On 7 Mar 2018, at 7:24 AM, Greg D. <gregd2350 at gmail.com <mailto:gregd2350 at gmail.com>> wrote:
>>>>>>>
>>>>>>> Hi Michael,
>>>>>>>
>>>>>>> I trying to figure out how Zeroconf is supposed to work, given the
>>>>>>> networking services that the module currently supports.  Perhaps I don't
>>>>>>> understand mDNS well enough, but don't we need some means to broadcast
>>>>>>> our presence, separate from the network?
>>>>>>>
>>>>>>> I was able to run the ZeroConf Browser on my Android phone (Google
>>>>>>> Pixel2, latest code), and it did discover the module.  But that was only
>>>>>>> when the module and phone were both connected by wifi to the home
>>>>>>> network.  When it was running in AP mode, with the phone connected to
>>>>>>> the home network, there is no way for the phone to see the mDNS service
>>>>>>> announcement packets.
>>>>>>>
>>>>>>> I did a wireless trace of the wifi beacons, thinking it might be
>>>>>>> broadcast in there, but didn't find anything service-oriented other than
>>>>>>> the usual stuff.  The only wifi adapter that I could get to cooperate
>>>>>>> with me today was a really old one (11b-only), so perhaps there's
>>>>>>> something at an 11g/n level that I can't see?
>>>>>>>
>>>>>>> I'm thinking we need some out-of-band channel for the broadcasts, for
>>>>>>> example, Bluetooth.  Isn't there a service there for this purpose?  How
>>>>>>> is this supposed to work?
>>>>>>>
>>>>>>> Greg
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Michael Balzer wrote:
>>>>>>>> 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
>>>>>>>> that. It doesn't work on Android 7, so is not usable as a general solution.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> OvmsDev mailing list
>>>>>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.teslaclub.hk
>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>
>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>> -- 
>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180308/bc9538ac/attachment.htm>