Hi
If I understand correctly the wifi will only work if the phone is close by
I read elsewhere that other smart watches will connect directly to wifi
even if the phone is not on
can someone please clarify & will this option come with future updates ?
Thanks
The phone needs to be only in a close range if you're connected by Bluetooth. If you're connected to a WiFi network, the phone just needs an internet connection and can be on the other side of the world.
foo said:
The phone needs to be only in a close range if you're connected by Bluetooth. If you're connected to a WiFi network, the phone just needs an internet connection and can be on the other side of the world.
Click to expand...
Click to collapse
Thanks Foo
But it doesn't seem to be the case with mine
If I am at home or at work it will connect easily with the Wifi but only if the phone is there
without the phone its saying disconnected , maybe I am missing something
I did a test recently with mine. I left my paired smartphone (Smartphone_A) far out of range of my watch (>100m within a company building). The watch signaled that it is disconnected as it was only connected by Bluetooth before. The smartphone itself was only connected to a 3G network (no WiFi active).
I used a second smartphone (Smartphone_B, obviously not paired with the watch) and activated the mobile hotspot on it. I connected the watch to the mobile hotspot using WiFi and was able to connect to my paired smartphone:
Code:
Watch<---WiFi<--->Smartphone_B<--------->3G mobile data<--------->Smartphone_A
<--------------------receive notifications-------------------------->
I was really surprised that this worked, but it did, so I'm pretty sure, that they do not have to be both connected to the same WiFi or be within a close range.
The question is, why is it not working for you. How do you check, that you are connected to the WiFi?
foo said:
I did a test recently with mine. I left my paired smartphone (Smartphone_A) far out of range of my watch (>100m within a company building). The watch signaled that it is disconnected as it was only connected by Bluetooth before. The smartphone itself was only connected to a 3G network (no WiFi active).
I used a second smartphone (Smartphone_B, obviously not paired with the watch) and activated the mobile hotspot on it. I connected the watch to the mobile hotspot using WiFi and was able to connect to my paired smartphone:
Code:
Watch<---WiFi<--->Smartphone_B<--------->3G mobile data<--------->Smartphone_A
<--------------------receive notifications-------------------------->
I was really surprised that this worked, but it did, so I'm pretty sure, that they do not have to be both connected to the same WiFi or be within a close range.
The question is, why is it not working for you. How do you check, that you are connected to the WiFi?
Click to expand...
Click to collapse
Strange
with my phone on no problems it shows my house & work network on the watch & connects showing the correct SSID
with phone off I tested it 2 ways 1 clicked on google app (disconnected ) 2 Settings- About -Connection (disconnected )
Brgds
I see the problem, I also may have misunderstood the actual problem.
The status (Google app/about) which you are referring to shows if you're connected to your watch. If your phone is off, the watch can't connect to the phone. Even if the watch is connected to your WiFi, the watch will not go directly to the internet, but will use the WiFi connection to connect to your phone (cloudsync).
You can check the WiFi connection in the WiFi setting. See if the watch was assigned an IP address, if there is one, then you're connected to the WiFi.
I think you expected that the watch can directly connect to the internet and use things like Google now directly. but this is not possible.
foo said:
I see the problem, I also may have misunderstood the actual problem.
The status (Google app/about) which you are referring to shows if you're connected to your watch. If your phone is off, the watch can't connect to the phone. Even if the watch is connected to your WiFi, the watch will not go directly to the internet, but will use the WiFi connection to connect to your phone (cloudsync).
You can check the WiFi connection in the WiFi setting. See if the watch was assigned an IP address, if there is one, then you're connected to the WiFi.
I think you expected that the watch can directly connect to the internet and use things like Google now directly. but this is not possible.
Click to expand...
Click to collapse
Yes
I checked a few things, my phone was on & the google app works, turn phone off & the google app says disconnected
in wifi settings even with phone off it says obtaining IP then connects so I thought it would connect to google app
so if I understand correctly it wont connect directly to internet but the phone (cloudsync) even if the phone is on or off
Thanks for taking the time to clarify
tclough said:
so if I understand correctly it wont connect directly to internet
Click to expand...
Click to collapse
correct
tclough said:
but the phone (cloudsync) even if the phone is on or off
Click to expand...
Click to collapse
it will connect to the phone by cloudsync only if the phone is on.
foo said:
correct
it will connect to the phone by cloudsync only if the phone is on.
Click to expand...
Click to collapse
Thanks
all seems a bit pointless to have a wifi connection but cant really use it do anything
maybe some apps or updates in the future that will utilize the wifi option ??
Thx
I guess wifi is just helpful if you get out of range of the Bluetooth connection.
At home I often get out of range of the Bluetooth connection so the watch connects to my wifi and reconnects to my watch via cloudsync as long as I stay out of Bluetooth range.
When the watch gets back in reach it connects via Bluetooth again, because this is much better for battery life.
So wifi is only there to increase range but unfortunately not for standalone functionality. I also have a Youtube client and a webbrowser on my watch (just for fun, not really useful). Both apps also need the watch and will not use a direct wifi connection to load videos/websites from the Internet.
Related
Hello, I updated my Moto 360 to the new version which enables wifi support and I have a weird problem, when I disconnect my phone bluetooth and wifi and enable wifi on moto 360 I notice that I don't get notifications for mails, facebook messages, tweets etc also voice commands won't work, but I can browse webpages with android wear internet browser.
Am I missing something ?
Isn't the whole idea of wifi support to be able to use the watch autonomously ?
If not by Bluetooth, your watch must still be on the same network as your phone to get notifications from your phone. You need to turn WiFi on your phone back on.
Hey RoyJ thanks for your reply, I see so the phone gets a notifications then pushes it to the watch via wifi, that's a shame, let's hope in a future update where the device would function autonomously without a phone.
Noticed the same thing. What I have found is that Bluetooth needs to be on regardless of whether the watch is connected to the phone or not. It is as if it is a switch to tell the android wear app whether or not to forward notifications. I can personally confirm that you do not need to be on the same WiFi network. I had my paired phone in my car at work with WiFi off and my phone connected to a hotspot I created with another phone and received all the notifications on my watch.
Sent from my LG-VS985 using Tapatalk
Also from what I read, voice commands might not work on WiFi, just notifications.
I've set this up according to Google's support page and can confirm that my Moto 360 connects to WiFi when out of range of the phone. However, it still remains disconnected from the phone, even though both phone and watch are using the same WiFi. The little cloud symbol with the line through it never disappears and none of the connected features work. As soon as I move back into range of the phone it switches back to bluetooth and reconnects again. So the switching to WiFi part is working OK, it just fails to communicate with the phone over WiFi. It's a Nexus 6, if that's relevant.
Any ideas?
EDIT: Never mind, it appears to be because the phone is using IPv6 but the watch only supports IPv4, oddly. If I force the phone to use IPv4 it works.
mijkz said:
EDIT: Never mind, it appears to be because the phone is using IPv6 but the watch only supports IPv4, oddly. If I force the phone to use IPv4 it works.
Click to expand...
Click to collapse
Really? Isn't IPv4 kicking the bucket officially real soon like?
I can't get this working either. I have no idea why the phone's bluetooth or IPv6 should make any difference at all for this feature. It's supposed to use the cloud, and as long as the phone and watch have a connection to the internet then it should work.......right?
Unfortunately it's the sort of feature that I will disable unless it is truly reliable. And so far I can't even get it to work at all, so it's only reliable in it's ability to connect to a wifi network and drain the battery.
aperry said:
I can't get this working either. I have no idea why the phone's bluetooth or IPv6 should make any difference at all for this feature. It's supposed to use the cloud, and as long as the phone and watch have a connection to the internet then it should work.......right?
Click to expand...
Click to collapse
No, that is NOT how it works. Your watch is a slave to your phone regardless of the WiFi feature; WiFi just gives you a longer leash. I'ts HIGHLY unlikely that the current iteration of Android Wear will allow you to "leave home without your phone" as someone suggested above. It's just not how it was designed, nor how Google envisions it. If that's what you want, you're best looking outside of Android Wear and into some of the fringe wearables that actually act as mobile devices.
thebobmannh said:
No, that is NOT how it works. Your watch is a slave to your phone regardless of the WiFi feature; WiFi just gives you a longer leash. I'ts HIGHLY unlikely that the current iteration of Android Wear will allow you to "leave home without your phone" as someone suggested above. It's just not how it was designed, nor how Google envisions it. If that's what you want, you're best looking outside of Android Wear and into some of the fringe wearables that actually act as mobile devices.
Click to expand...
Click to collapse
But Google's own descriptions of the Android Wear wifi feature states this:
If your watch has Wi-Fi, your watch can automatically connect to saved Wi-Fi networks when it loses the Bluetooth connection with your phone. This lets your watch and phone to automatically stay synced at any distance over the Internet. That way you can get notifications and use voice search on your watch throughout your home and work when you leave your phone in a different room.
Click to expand...
Click to collapse
Operative words being "This lets your watch and phone stay synced at any distance over the internet". Are you telling me that "any distance over the internet" actually means "only as far as your local wifi network covers"?
It also states "Could Sync" must be turned on for wifi to work. Why would I need a feature called "Cloud Sync" if it's not designed to sync over the cloud?
aperry said:
But Google's own descriptions of the Android Wear wifi feature states this:
Operative words being "This lets your watch and phone stay synced at any distance over the internet". Are you telling me that "any distance over the internet" actually means "only as far as your local wifi network covers"?
It also states "Could Sync" must be turned on for wifi to work. Why would I need a feature called "Cloud Sync" if it's not designed to sync over the cloud?
Click to expand...
Click to collapse
Imagine you could connect to many WiFi locations as long as you already connected and saved those WiFi locations. But a WiFi only tablet can't connect at all times, how can you expect your watch to?
Here's what I have found:
My setup: Nexus 6 with Moto 360 5.1.1
On WiFi (same network) - BT off, I can receive texts, reply to texts, send texts. Once I turn off the WiFi on my phone, I no longer get notifications because the phone no longer knows where the phone is to send the notifications to. I think that makes sense. As others have said, the watch is always slave to the phone, however it is connected - WiFi or BT. But I do think that it was not designed to be independent of the phone, so you can't simply leave your phone at home and go out and expect to have notifications even if the watch is connected on WiFi.
mohcho said:
Here's what I have found:
My setup: Nexus 6 with Moto 360 5.1.1
On WiFi (same network) - BT off, I can receive texts, reply to texts, send texts. Once I turn off the WiFi on my phone, I no longer get notifications because the phone no longer knows where the phone is to send the notifications to. I think that makes sense. As others have said, the watch is always slave to the phone, however it is connected - WiFi or BT. But I do think that it was not designed to be independent of the phone, so you can't simply leave your phone at home and go out and expect to have notifications even if the watch is connected on WiFi.
Click to expand...
Click to collapse
I don't understand why "slave" would require the watch and phone to be on the same network. If the data is synced via the Cloud then the watch can still operate as a slave, meaning it will receive but not generate notifications.
Furthermore, it still doesn't explain why Google states that this wifi feature allows us to "stay synced at any distance over the internet", and why they state that the wifi feature requires the Cloud Sync feature to be enabled. if Cloud Sync is not meant to sync notifications over the cloud, then what exactly IS being sync'd over the cloud?
When you set up the watch, you have to pair it via BT using the phone. That authenticates the watch hardware with your account on your phone. If the phone and watch are not on the same network, how would your watch authenticate against your account? It's not like there's any account login option for the watch itself, hence it slaved to your phone on the same WiFi network. Since the watch has no real input options other than voice and swiping, there's no way to authenticate your watch to your account. I think it's wise that they set it up this way, albeit, a bit confusing how they worded the WiFi capabilities.
mohcho said:
When you set up the watch, you have to pair it via BT using the phone. That authenticates the watch hardware with your account on your phone. If the phone and watch are not on the same network, how would your watch authenticate against your account? It's not like there's any account login option for the watch itself, hence it slaved to your phone on the same WiFi network. Since the watch has no real input options other than voice and swiping, there's no way to authenticate your watch to your account. I think it's wise that they set it up this way, albeit, a bit confusing how they worded the WiFi capabilities.
Click to expand...
Click to collapse
Ok, putting aside the confusing language in Google's own description (that no one can explain), let me simplify my question: What is Cloud Sync?
Btw, authentication could be taken care of with a token. That would be generated by the Cloud and sent to the phone when the Cloud Sync feature is first enabled, and would be sent to the watch initially via BT and then used to authenticate the watch to the Cloud whenever needed. Token would be invalidated by the Cloud if/when Cloud Sync is disabled on the phone (for example, if the watch is stolen). This is roughly how I expected it to work. If somehow the watch and phone need to be on the same wifi network then this feature is 90% useless IMO, and Google's description is very misleading.
I stand corrected. I think it does work the way you suggest, but not 100%.
I connected my watch to my other phone's hotspot and am able to send/receive texts and emails to my watch. I turned off WiFi on my phone as well as the BT. It takes a while for it to connect and I assume authenticate using a token.
After a while though, like just now, I received a text on my watch but couldn't reply to it, the watching saying "Sorry that didn't work, try again".
mohcho said:
I stand corrected. I think it does work the way you suggest, but not 100%.
I connected my watch to my other phone's hotspot and am able to send/receive texts and emails to my watch. I turned off WiFi on my phone as well as the BT. It takes a while for it to connect and I assume authenticate using a token.
After a while though, like just now, I received a text on my watch but couldn't reply to it, the watching saying "Sorry that didn't work, try again".
Click to expand...
Click to collapse
Cool, thanks for testing this. Now if I can get my own watch to work then I'll be happy
By the way, the diagram at the bottom of this page seems to confirm that the watch should be able to sync notification data with the Cloud without any direct connectivity to the phone:
http://developer.android.com/training/wearables/data-layer/index.html
JeffMD said:
Really? Isn't IPv4 kicking the bucket officially real soon like?
Click to expand...
Click to collapse
The moto 360 doesn't support ipv6 that's for sure. But really that's a non issue, as far as them shutting down ipv4 it won't be for a long time. At least longer than the life cycle of the moto 360 anyways. The Ipv6 adoption is only more prevalent in the U. S. for the most part.
Also as far as a phone using ipv6 only I'm sure Google has some sort of protocol like NAT64 boxes in order for ipv6 to talk to ipv4 so it shouldn't matter if your phone is using ipv6 (but of course I could be wrong about that I'm just making that assumption they do have some sort of protocol to handle that)
jgeorge15 said:
The moto 360 doesn't support ipv6 that's for sure. But really that's a non issue, as far as them shutting down ipv4 it won't be for a long time. At least longer than the life cycle of the moto 360 anyways. The Ipv6 adoption is only more prevalent in the U. S. for the most part.
Also as far as a phone using ipv6 only I'm sure Google has some sort of protocol like NAT64 boxes in order for ipv6 to talk to ipv4 so it shouldn't matter if your phone is using ipv6 (but of course I could be wrong about that I'm just making that assumption they do have some sort of protocol to handle that)
Click to expand...
Click to collapse
I am pretty sure that the phone and watch do not talk to each other directly over wifi so this IPv4-IPV6 mismatch should be a non-issue provided each one of them can reach the internet.
aperry said:
I am pretty sure that the phone and watch do not talk to each other directly over wifi so this IPv4-IPV6 mismatch should be a non-issue provided each one of them can reach the internet.
Click to expand...
Click to collapse
Yes absolutely true. I meant to word the second paragraph in my statement in a way in which I meant suppose ipv4 was shut down in the near future I'm sure Google has someway to communicate with legacy devices so notifications could still be pushed to the watch. Hope that clarifies things.
I've got the 5.1.1 update and it works really well. Better than I expected.
Anyway, I can connect to wifi, even with the phone disconnected from the watch.
See, here is the issue: wifi is connected to the watch, but not working (Yes, I have a working wifi network).
Anyways, has anyone experienced this yet? Plus, does anyone know how to solve it?
Thanks in advance
Bump
I have the same issue / question. I have both watch and phone connected to the same WiFi network. I turn off Bluetooth on my phone and the watch shows the disconnected icon. I send a test email to my phone and the notification pops on my phone but nothing shows on my watch. Once I turn on Bluetooth the notification pops on my watch.
Do I just not understand how this feature should work?
dgoos said:
I have the same issue / question. I have both watch and phone connected to the same WiFi network. I turn off Bluetooth on my phone and the watch shows the disconnected icon. I send a test email to my phone and the notification pops on my phone but nothing shows on my watch. Once I turn on Bluetooth the notification pops on my watch.
Do I just not understand how this feature should work?
Click to expand...
Click to collapse
I believe the disconnected icon (cloud with line through it) means it is not connected to the wifi network. When you turn off bluetooth, you may see that icon temporarily, but after a few moments it should connect to wifi and the icon should go away.
You also need to turn on the setting in the phone so it knows to look through wifi when it can't tag the watch through Bluetooth
Sent from my Nexus 6 using XDA Free mobile app
reinaldistic said:
You also need to turn on the setting in the phone so it knows to look through wifi when it can't tag the watch through Bluetooth
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, the cloud sync setting in the android wear app can be set to off even though the wifi setting is on on the watch...
I am finding many instances where I am getting the cloud icon when I am at home. My watch has both of my access points set up. Sometimes I will get the cloud and I will be 10 feet away from an access point and within line of site while my phone is sitting even less than that from another access point and also in line of sight, and when I check the phone it is connected to wifi.
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
I have also noticed that the watch does not seem to automatically connect to wifi when it loses the BT connection even though I have it set to automatic in the settings.
I am not going to carry my phone all over the house like a goofball so that the watch works. Wifi capability was one of the things I was waiting for for this very reason. It makes the watch WAY more useful...but it actually has to work properly.
brizey said:
I am finding many instances where I am getting the cloud icon when I am at home. My watch has both of my access points set up. Sometimes I will get the cloud and I will be 10 feet away from an access point and within line of site while my phone is sitting even less than that from another access point and also in line of sight, and when I check the phone it is connected to wifi.
Click to expand...
Click to collapse
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
Have experienced the same. However, it may not be the watch problem and may be the Google cloud ☁ service.
vvveith said:
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
Have experienced the same. However, it may not be the watch problem and may be the Google cloud service.
Click to expand...
Click to collapse
Experiencing the same thing more and more often.
My phone (N6) is connected to either wifi or 4G; my watch connects to wif's as well. Nonetheless when disconnected from bluetooth it disconects completely (The Cloud thingy).
Why? I must be doing something wrong, Android Wear is new to me.
Had my galaxy watch about a month now. I have set wifi to auto but I find it resets itself to off. I then set wifi to on and then it still turns off. Any ideas on what is going on? I may have to contact Samsung and I dread doing so.
WiFi shall only be used if the watch loses the connection to your phone. It is only used for the remote connection feature, where the Bluetooth connection between watch and phone is lost afaik
Gesendet von meinem SM-G965F mit Tapatalk
It is set to turn on when I lose BT connection. It can't turn on because the watch has turned wifi completely off
I have my WiFi set to automatic and that works just as expected. Connects to WiFi when Bluetooth connection drops.
Gesendet von meinem SM-G965F mit Tapatalk
I had that problem and I've only gotten my watch for a couple of days. I just turned on wifi to auto when the watch was connected to bluetooth and it just kept going that way for the time being.
Update: I've seen that the WiFi turns itaelf off again after some time. I'm pretty curious to know what causes that.
Have had my watch five days now and have experienced the problem of not being able to reconnect to Wi-Fi..
Define a Wi-Fi connection to be used 'Auto' (when out of reach of BT). But next time the watch is out of BT-reach it is stuck in 'Connecting ...' ( seen in the status of Wi-Fi).
Have reported this as an issue ( I'm in Denmark) and got the answer: Try to 'Reset' - otherwise wait for an update.
My software version is: R815FXXU1BRHB
Maybe it is a router problem. In German forums some dudes have problems with fritz Box router. It does connect only once to the router.
I also noticed that. Probably watch tries to save battery life. It turns on again when you start to do something. Personally I find out as good feature. No drawback.
bagmanone said:
I also noticed that. Probably watch tries to save battery life. It turns on again when you start to do something. Personally I find out as good feature. No drawback.
Click to expand...
Click to collapse
It is not because there are three options Wi-Fi (off), Wi-Fi (on) and Wi-Fi (auto). The later should (re)connect to Wi-Fi when out of reach of BT (the first two are manual). But the reconnect is never completed, stays in "Connecting ...".
What do you mean by "It turns on again when you start to do something."? My watch does not for the above reason (connection is never completed).
Doing manual Wi-Fi connection to same Wi-Fi works fine. When out of reach of BT to mobile it is connected to 4G network.
pkylle said:
It is not because there are three options Wi-Fi (off), Wi-Fi (on) and Wi-Fi (auto). The later should (re)connect to Wi-Fi when out of reach of BT (the first two are manual). But the reconnect is never completed, stays in "Connecting ...".
What do you mean by "It turns on again when you start to do something."? My watch does not for the above reason (connection is never completed).
Doing manual Wi-Fi connection to same Wi-Fi works fine. When out of reach of BT to mobile it is connected to 4G network.
Click to expand...
Click to collapse
I use option Always On. For the option watch turn off Wifi when it is not used at all. Watch turns Wifi on when I start to use watch. It is only my observation. I don't know is that indented behave for GW.
bagmanone said:
I use option Always On. For the option watch turn off Wifi when it is not used at all. Watch turns Wifi on when I start to use watch. It is only my observation. I don't know is that indented behave for GW.
Click to expand...
Click to collapse
Have you tried the Wi-Fi (auto)?
pkylle said:
Have you tried the Wi-Fi (auto)?
Click to expand...
Click to collapse
Not really, I usually need Wifi to connect the internet.
bagmanone said:
Not really, I usually need Wifi to connect the internet.
Click to expand...
Click to collapse
The watch will connect to the internet using BT to the mobile if within range.
pkylle said:
It is not because there are three options Wi-Fi (off), Wi-Fi (on) and Wi-Fi (auto). The later should (re)connect to Wi-Fi when out of reach of BT (the first two are manual). But the reconnect is never completed, stays in "Connecting ...".
What do you mean by "It turns on again when you start to do something."? My watch does not for the above reason (connection is never completed).
Doing manual Wi-Fi connection to same Wi-Fi works fine. When out of reach of BT to mobile it is connected to 4G network.
Click to expand...
Click to collapse
The sync Wi-Fi profiles setting seems to cause the the watch forgets the Wi-Fi password. This shows up as with that "connecting..." state. Try to remove that sync option from the wear app on phone and see if that helps.
I would like to use the Wi-Fi (auto) setting, but for some reason the watch changes that back to Wi-Fi (off) by itself. No idea how to make the watch to remember the setting.
miloytyn said:
The sync Wi-Fi profiles setting seems to cause the the watch forgets the Wi-Fi password. This shows up as with that "connecting..." state. Try to remove that sync option from the wear app on phone and see if that helps.
Click to expand...
Click to collapse
Wow! That did it but this shows there clearly is an error in the sync. option. Did someone report that to Samsung?
Thanks.
miloytyn said:
The sync Wi-Fi profiles setting seems to cause the the watch forgets the Wi-Fi password. This shows up as with that "connecting..." state. No idea how to make the watch to remember the setting.
Click to expand...
Click to collapse
Just bought this watch today. I have the same problem
Disablem "syncing" in connection setting on phone app cures the pproblem
Same issue here.
Just bought the watch and set it on Always on wifi but noticed that it disconnects after some time and then refuses to connect to the same SSID. It either says, authentication error, cannot connect to ...., or doesn't say anything.
Restarting the watch fixes it temporarily.
Keeping it on Auto, does not change from bluetooth to wifi when out of range.
Sync profiles is on. I will try with it off.
Did anyone figure the solution to the issue?
I am facing the same issue
Hello guys how are you?
Recently I bought a Dasaita PX6 Android 10 for my Toyota CHR. Camera working OK, Sound OK... but I have a problem with WIFI connection.
As soon as setup my phone as hotspot, I search that WIFI on DASAITA. I find it and connect to it but as soon as IP address is raised WIFI turns off automatically.
Here I show you a video of the problem:
youtube.com/watch?v=akjF7q0NvJc&feature=youtu.be&spm=a2g0s.imconversation.0.0.560b3e5f2rShbE
Thanks
I had the same issue. I think it has to do with the Zlink app which tries to put the HA in hotspot mode. I managed to switch on wifi after closing the Zlink app manually and disabling the hotspot in the dropdown menu(the icons which appear if you swipe down from the top of the screen). Unfortunately the wifi connection with the hotspot of my iPhone is nog always stable. Sometimes it disconnects after a couple of minutes.
SYoung said:
I had the same issue. I think it has to do with the Zlink app which tries to put the HA in hotspot mode. I managed to switch on wifi after closing the Zlink app manually and disabling the hotspot in the dropdown menu(the icons which appear if you swipe down from the top of the screen). Unfortunately the wifi connection with the hotspot of my iPhone is nog always stable. Sometimes it disconnects after a couple of minutes.
Click to expand...
Click to collapse
Thanks for your reply.
If you saw the video I linked I have closed all apps and the problem is still there. I don't know what happens
CyrusMzRG said:
Thanks for your reply.
If you saw the video I linked I have closed all apps and the problem is still there. I don't know what happens
Click to expand...
Click to collapse
Yes, a saw that, but as far as I can see, you did not disable the hotspot before turning on wifi. I needed to do that as well.
SYoung said:
Yes, a saw that, but as far as I can see, you did not disable the hotspot before turning on wifi. I needed to do that as well.
Click to expand...
Click to collapse
I think as soon as wifi is set to ON, hotspot turns off automatically. It can be shown also on the video.
Actually I use CAR PLAY but I would like to swap between both options with no connection problems :crying:
I thought my suggested method worked, but today it did not work for me either. I agree with you that this is quite annoying. Hopefully someone else can help us out.
i have same issue... looking forward to somebody do a stable update that solve this problem
I have this unit. What works for me is to use usb hookup for CarPlay, then you can use phone hotspot on radios WiFi. You have to turn WiFi on a few times after connecting phone through usb for it to stick. For wireless CarPlay, the radio uses the WiFi resources and turns off selectable WiFi.
Sent from my iPad using Tapatalk
the problem for me is that my iphone is not connect well to the bluetooth of the Dasaita, the issue is that i can't answer or make a call through the Dasaita (android)..... When i'm able to connect to BT and the Zlink start then the BT disconnects, when switch shut down Zlink app BT won't connect anymore
CyrusMzRG said:
I think as soon as wifi is set to ON, hotspot turns off automatically. It can be shown also on the video.
Actually I use CAR PLAY but I would like to swap between both options with no connection problems :crying:
Click to expand...
Click to collapse
I think Syoung (above) is correct.
Obviously you can't run hotspot and wifi at the same time. It's one or the other.
If watch the video closely, the hotspot is off. As soon as wifi is turned on and the phone connects SOMETHING turns the hotspot on (you can see it getting turned on at the 19 second mark in the video), which in turn shuts off the wifi.
Maybe try completely disabling hotspot and see what happens
Well. I tried to connect the iPhone to the car via USB cable to launch CARPLAY. I think my car USB port that actually y also connected to DAISATA doesn’t support CARPLAY. Maybe I need to connect another cable to the back of DASAITA module to make it work.
In addition about the HOTSPOT. The DAISATA HOTSPOT is automatically set to ON to link with iPhone CarPlay.
If I turn it off as soon as my iPhone is near (also set use with CarPlay) hotspot back to ON and CARPLAY IS LINKED AND LAUNCHED.
Do you know if I need to use another cable connected to usb connector located in the back of DAISATA??
Thanks
Hello again. This is what I did and noticed:
- Car usb socket (connected to Daisata) doesn't work with USB CARPLAY.
- I connect the extra usb port to DAISATA.
- CARPLAY via USB working OK on that port.
- If using WIRELESS CARPLAY, Dasaita acts as hotspot creating a WIFI network where iPhone connects automatically.
- Now... I connect the iPhone to the new USB port for CARPLAY ( working ok and connecting faster). I disabled Hotspot from DASAITA. I turned ON WIFI and connect Dasaita to my iPhone hotspot . ALL OK.
So as somebody said is not possible use WIRELESS CAR PLAY and also have WIFI on Dasaita software.
I think connecting the iPhone to the new port we have the 2 connections ( car play and wifi) and on the other hand we can recharge the iPhone.
BUT.... now I need to solve another problem. I don't know why I need to switch off the Hotspot on iPhone each time I want The Daisata connects to the iPhone Hotspot. If I leave the hotspot always ON ( as it MUST BE) the wIFI that iPhone creates doesn't appear on DAISATA. As soon as I switch OFF then ON DAISATA connects in 1 sec to my iPhone
Best regards
CyrusMzRG said:
Hello again. This is what I did and noticed:
- Car usb socket (connected to Daisata) doesn't work with USB CARPLAY.
- I connect the extra usb port to DAISATA.
- CARPLAY via USB working OK on that port.
- If using WIRELESS CARPLAY, Dasaita acts as hotspot creating a WIFI network where iPhone connects automatically.
- Now... I connect the iPhone to the new USB port for CARPLAY ( working ok and connecting faster). I disabled Hotspot from DASAITA. I turned ON WIFI and connect Dasaita to my iPhone hotspot . ALL OK.
So as somebody said is not possible use WIRELESS CAR PLAY and also have WIFI on Dasaita software.
I think connecting the iPhone to the new port we have the 2 connections ( car play and wifi) and on the other hand we can recharge the iPhone.
BUT.... now I need to solve another problem. I don't know why I need to switch off the Hotspot on iPhone each time I want The Daisata connects to the iPhone Hotspot. If I leave the hotspot always ON ( as it MUST BE) the wIFI that iPhone creates doesn't appear on DAISATA. As soon as I switch OFF then ON DAISATA connects in 1 sec to my iPhone
Best regards
Click to expand...
Click to collapse
I went into the zlink app preferences and turned off autoload and control system settings. This seems to stop zlink from turning everything back on when you turn it off. Been working for a few days. I do not however use android auto. You would need to play with the app to see how it functions without those permissions.
Hello,
I couldn't make the switch to wifi on. It kept going off. Tried your help, nothing worked.
What helped me today was a complete "power off". A restart.
It's working now.
Hi, I have a Dasaita PX6 with Max10, I have same issue, i have an iPhone 13 Pro Max, I don't know what to do, I can't solve, could you help me? Thank you in advance
I had a similar issue. I recently purchased a Dasaita HD5367-H10 unit and I've been having some trouble with the WiFi.
When the unit turns on, the WiFi turns on and it connects to my phone's hotspot. Shortly after it connects, the WiFi turns off and I have to manually turn it on again. This only happens once upon boot up and it works fine for the rest of the duration. Once I restart the unit, the issue occurs again.
I think I found a workaround. Disabling ZLink from the Factory Settings menu seems to "fix" the problem, but now the ZLink daemon service is not working.