Hi Guys,
Just bought that wifi robot Skypee. Excellent piece of kit. But was just wondering if anyone has heard of or can develop software so I can control it through my Diamond (or any windows mobilke based phone).
Just posting it in Diamond section as I own one but I am sure that Spykee users will have other mobile devices whether it be windows platform or not.
Any coments suggestions welcome.
Had a quick search on google but could not find anything (yet).
anybody?
BUMP!
Just bumping this thread to get noticed.
So, I am assuming nobody has found a way to do this.
Never mind. I am sure many of you may get a spykee this xmas and maybe then the devlopments will start (hopefully)!
I didn't thinkt you could buy Spykee yet. Where have you bought it???
cool gadget!
Agent 720 said:
I didn't thinkt you could buy Spykee yet. Where have you bought it???
Click to expand...
Click to collapse
alrite mate,
i bought mine few weeks back from costco in birmingham. it cost me £115 inc vat! but i heard they were going for £99 on amazon inc delivery! dont know if they still available though.
only thing that is a ***** about spykee is building it. it comes with about 1000 pieces. it took me about 6 hours in total to build it!!!
but its worth it! its really a great "spy" robot and the voip funtionaility is overrated as skype is not supported (yet anyway). but good thing about it is that firmware can be upgraded and additional programs for robot can be written in future!
just waiting for a windows mobile based gui application to control it! then it will be awesome
I just got a Spykee for Xmas, My girlfriend paid 175 quid and that was the cheapest price a few months back as they were all 199.
Im gutted to see it for 99 quid now but thats just the way things go!!
I would love to control it from my xperia.
There is an SDK for the Spykee and I might even try and develop some software myself depending on what language its for.
Shame about the price, I could have had 2 and used one to build an Ed209 from robocop or a Johnny 5 from short circuit.
It took me about 2 hours to build, if that! How the hell did it take you 6 hours?
I did have trouble with the stupid fiber optics though as they kept falling out but it was easier to just put them in last!!
lol
CrazyDiamond said:
I just got a Spykee for Xmas, My girlfriend paid 175 quid and that was the cheapest price a few months back as they were all 199.
Im gutted to see it for 99 quid now but thats just the way things go!!
I would love to control it from my xperia.
There is an SDK for the Spykee and I might even try and develop some software myself depending on what language its for.
Shame about the price, I could have had 2 and used one to build an Ed209 from robocop or a Johnny 5 from short circuit.
It took me about 2 hours to build, if that! How the hell did it take you 6 hours?
I did have trouble with the stupid fiber optics though as they kept falling out but it was easier to just put them in last!!
Click to expand...
Click to collapse
lol, 2 hours not bad! it took me that long to build the backbone lol! well6 hours was an average time over 3 days. did not have time to spend whole day on it but i suppose if u got experience with meccano or are good with building things like this then it would be good. i just wish the robot could build itself out the box lol!
I cant wait for applications\firmware for this to come out! will be excellent! my nephews love connecting to it from the other side of the world and playing\chasing\talking to my son via spykee! Great!
crazydiamond, you talk of an sdk being released? is it out yet? i last checked the website few days back and it was not out. will have a quick search again after i posted and if i cant find it will try and ask the question here again.
but i am glad to hear that i am not the only one wanting an application to control spykee from a WM based handset! will be very interesting to see one!
Have fun merry xmas and happy new year to all!
Apparently there is an SDK coming out soon, as spykee was advetised as having one I thought there was already one to download!
Another shameless marketing trick!
There is a guy called Jimfx on www.spykee.org who has deleloped his own GUI in Delphi and it works really well.
You can even change the speed to make Spykee a lot slower.
Give it time and someone will release some source code for us to play with.
I am quite dissapointed with spykee if I am honest.
I have had nothing but trouble with remote connection setup and have had to change my router settings because Spykee would not see my router unless it was broadcasting the SSID!
I still cannot get my friends to connect! Have forwarded every port and updated firmware on the router.
It needs an update and a web interface and some better documentation.
I expected so much more, and the intruder detection is not as advertised either.
I will keep you posted mate on any, if any, code appears for Spykee Devs
All the best and Merry Crimbo
Crazy Diamond
spykee
CrazyDiamond said:
Apparently there is an SDK coming out soon, as spykee was advetised as having one I thought there was already one to download!
Another shameless marketing trick!
There is a guy called Jimfx on www.spykee.org who has deleloped his own GUI in Delphi and it works really well.
You can even change the speed to make Spykee a lot slower.
Give it time and someone will release some source code for us to play with.
I am quite dissapointed with spykee if I am honest.
I have had nothing but trouble with remote connection setup and have had to change my router settings because Spykee would not see my router unless it was broadcasting the SSID!
I still cannot get my friends to connect! Have forwarded every port and updated firmware on the router.
It needs an update and a web interface and some better documentation.
I expected so much more, and the intruder detection is not as advertised either.
I will keep you posted mate on any, if any, code appears for Spykee Devs
All the best and Merry Crimbo
Crazy Diamond
Click to expand...
Click to collapse
yeah i had trouble setting up remote connection. but make sure you have changed the default admin password for spykee from password (default) to whatever you want. also, it is better to have a static ip address assigned to spykee so that it functions correctly.
its true about the false marketing about spykee but hey, i know this can be more of a robot than meccano have advertised it as because once custom apps for the robot can be made...well lets just say we will 'flash' spykee just as we 'flash' our mobile devices....to get more functionailty out of them than the manufacturers initially permitted!
Thanks for your reply and Help.
I have already assigned a static ip to spykee and tried Mac filtering on/off, broadcast ssid on/off, WEP on/off etc etc and still no luck.
Its starting to piss me off, The robot is not responding to anything.
The battery lasts a few minutes before it says it needs to re dock! Even on a full charge it says it needs to re dock.
So annoying. It looses connection in Local mode or Ad-hoc and none of the features work that are supposed too either.
I have already emailed play for a refund but it was bought before their 28 day stupid returns policy. Even though I only opened it on Xmas Morning.
Looks like I will be taking them to court.
Hi CrazyDiamond,
In order to be able to connect to Spykee from the internet, you have to follows
these steps ( and it works really good)-- I will use example data to make thing easy.
- Create a user other than admin on the console application
( MyUser / MyPassword)
- Register your Spykee on http://www.spykeeworld.com/spykee/US/index.html and select register. ( Give a name to your robot and a password -- carefull, this is case sensitive)
( MyRobot / MyRobotPassword)
- Still in the console, in My Spykee tab, put EXACTLY the name ( case sensitive) and the password you registered in spykeeworld. Note the ip adress you have here.
( MyRobot / MyRobotPassword). The ip shown: 192.168.1.1)
- Go to the remote connection tab and check 'Authorize remote access' then put a port number.
( 12345)
- On your router you need to do port forwarding to Spykee ip address and use as SOURCE and DESTINATION the port number you did put on the console application.
( source port: 12345 destination port: 12345 destination ip: 192.168.1.1 )
That's all.
Now to connect to your Spykee, click on the connection icon. Select Remote robot and put the exact name you used to register spykee ( case sensitive).
( MyRobot)
Then when the password is requested, use the account you create on the console (not the admin one).
(MyUser/MyPassword)
Then it should work.
Regarding the battery which the console says it is empty. This is a bug on the console application. Just don't take in account this message and you will see that you can use your Spykee for hours.
Regarding the documentation, it sucks!
Regarding the SDK, this is not yet available and I hope it will be soon...
Yes the last note, your Spykee should bip 3 times when you turn it on, which means it did
connect to your wifi access point.
I hope it helped.
Drack
CrazyDiamond said:
Thanks for your reply and Help.
I have already assigned a static ip to spykee and tried Mac filtering on/off, broadcast ssid on/off, WEP on/off etc etc and still no luck.
Its starting to piss me off, The robot is not responding to anything.
The battery lasts a few minutes before it says it needs to re dock! Even on a full charge it says it needs to re dock.
So annoying. It looses connection in Local mode or Ad-hoc and none of the features work that are supposed too either.
I have already emailed play for a refund but it was bought before their 28 day stupid returns policy. Even though I only opened it on Xmas Morning.
Looks like I will be taking them to court.
Click to expand...
Click to collapse
Great!
drack said:
Hi CrazyDiamond,
In order to be able to connect to Spykee from the internet, you have to follows
these steps ( and it works really good)-- I will use example data to make thing easy.
- Create a user other than admin on the console application
( MyUser / MyPassword)
- Register your Spykee on http://www.spykeeworld.com/spykee/US/index.html and select register. ( Give a name to your robot and a password -- carefull, this is case sensitive)
( MyRobot / MyRobotPassword)
- Still in the console, in My Spykee tab, put EXACTLY the name ( case sensitive) and the password you registered in spykeeworld. Note the ip adress you have here.
( MyRobot / MyRobotPassword). The ip shown: 192.168.1.1)
- Go to the remote connection tab and check 'Authorize remote access' then put a port number.
( 12345)
- On your router you need to do port forwarding to Spykee ip address and use as SOURCE and DESTINATION the port number you did put on the console application.
( source port: 12345 destination port: 12345 destination ip: 192.168.1.1 )
That's all.
Now to connect to your Spykee, click on the connection icon. Select Remote robot and put the exact name you used to register spykee ( case sensitive).
( MyRobot)
Then when the password is requested, use the account you create on the console (not the admin one).
(MyUser/MyPassword)
Then it should work.
Regarding the battery which the console says it is empty. This is a bug on the console application. Just don't take in account this message and you will see that you can use your Spykee for hours.
Regarding the documentation, it sucks!
Regarding the SDK, this is not yet available and I hope it will be soon...
Yes the last note, your Spykee should bip 3 times when you turn it on, which means it did
connect to your wifi access point.
I hope it helped.
Drack
Click to expand...
Click to collapse
Drack thats great man! Its a better guide than I could even think of. I wish I had a straight forward step by step guide when I was trying to configure mine out!!!!
i am sure this will help newbies of spykee!
CrazyDiamond, have you ironed out the issues with ur spykee? personally i think there is something wrong with its wifi broadcasting capabilities but hey im no expert. let us know how you get\got on
Hi, sorry for late reply, I was without Spykee as I sent him back for refund.
My spykees power issues were not software bug related, he eventually would not even activate when clicking "click to activate" Thing was driving me crazy so I sent him back and got my 184 quid back.
Bought another one for 94 quid from Gizoo and just build him and finished setting him up.
Drack, Nice guide, I appreciate your help although there was nothing there that I didn't already do correctly in the first place.
I still cannot connect remotely, I think it is down to my Router but I really do not know for sure.
I am a bit of a Computer Wizard and have been for the past 15 years, Solved 100's of PC hardware related and software related problems but cannot get a stupid robot that has age 8 written on it!! lol gotta laugh really.
Im sure my router is forwarding the ports correctly as I even checked the ports were open, completely removed all my security, firewalls and made sure He has his own IP assigned and still no luck.
Think I will convert him into an Ed209 or Johnny5 and wait for a firmware update if a new router does not work.
Cheers guys and Happy new year.
WooHoo, He is alive, Johnny 5 is alive!!! Well spykee is but you know they look the same.
I didn't test the new robot from a remote computer as it didn't work with the first one I had on the same settings.
I tested it with a local computer using remote connection as it specified in the manual.
This did connect for about 2 seconds and then just disconnected. Same thing as with first robot.
Wasn't even gonna bother testing from a remote Computer but decided as my friend had the software and was online at the time I would ask.
To my supprise, He connected! Still cant connect remotely from a local pc but thats only to test it anyway.
So happy He works. If anyone else has the same problem as I have had then make sure you try it from a remote PC, even if it doesn't connect as instructed in the manual.
It is so much fun to have someone drive him round
Strange!
Hi CrazyDiamond,
Your problem is really strange...especially the fact that you can't connect remotely from your local pc while a friend of you can connect remotely from his computer...
this could be that you have a kind of network problem. Check if you dhcp server is
correctly configured (if you can force an ip address for a specific mac address then do it for your robot, so it ensure that you will get anytime the same ip address...)...because if you don't then your port forwarding will not work correctly...this is stupid they didn't allow a fix ip address for the robot
Drack
drack said:
Hi CrazyDiamond,
Your problem is really strange...especially the fact that you can't connect remotely from your local pc while a friend of you can connect remotely from his computer...
this could be that you have a kind of network problem. Check if you dhcp server is
correctly configured (if you can force an ip address for a specific mac address then do it for your robot, so it ensure that you will get anytime the same ip address...)...because if you don't then your port forwarding will not work correctly...this is stupid they didn't allow a fix ip address for the robot
Drack
Click to expand...
Click to collapse
Hi Drack, I already have the router Mac filtered and also already assigned a specific IP to Spykee by adding his Mac into the routers config.
Its all working fine apart from connection to a remote robot from local pc. This is not a problem as when I am home I connect too him locally and when I am at work I connect remotely.
It cant be the PC I am using as I have tried 2, One connected with wifi running xp pro sp3 and the other is connected via patch cable directly too the router, thats running Vista Ultimate 64.
The software is buggy using Vista64 and does tell me the battery needs charging etc.
Thanks for your advise, If I was unable to fix the problems myself then your advise would have been a blessing and I would have solved it.
Hope this thread helps others with problems.
By the way, Spykee is the nuts and I have had so much fun. Cant wait to Mod him and get the SDK.
Sdk is coming...
Hi CrazyDiamond,
Your problem is really strange but as soon as you can connect remotely from outside, and locally, this is no more a real problem.
For the battery I have exactly the same problem under XP, it tells the battery is empty after 5mn of run. It seems to be a bug in the software...
For the SDK, I emailed the support and they told me that they apologize to be late, but that the SDK should be available very soon ( this month).
I hope now that they will be hardware addon for Spykee...maybe Mecanno/Erector will provide new add on devices in the future...or why would they have use an usb connector??
cheers,
Drack
CrazyDiamond said:
Hi Drack, I already have the router Mac filtered and also already assigned a specific IP to Spykee by adding his Mac into the routers config.
Its all working fine apart from connection to a remote robot from local pc. This is not a problem as when I am home I connect too him locally and when I am at work I connect remotely.
It cant be the PC I am using as I have tried 2, One connected with wifi running xp pro sp3 and the other is connected via patch cable directly too the router, thats running Vista Ultimate 64.
The software is buggy using Vista64 and does tell me the battery needs charging etc.
Thanks for your advise, If I was unable to fix the problems myself then your advise would have been a blessing and I would have solved it.
Hope this thread helps others with problems.
By the way, Spykee is the nuts and I have had so much fun. Cant wait to Mod him and get the SDK.
Click to expand...
Click to collapse
There is a working mOd for the camera tilt already
Even without the SDK CdRsKuLL over at spykeemods has managed to do it.
Head over too http://www.spykeemods.co.uk/
Working on a brighter LED at the moment for better night vision.
I recently bought a Verizon Note 9 (first Samsung phone) so I'm not well versed on things. I have noticed from time to time when I am not receiving carrier signal (still connected to wifi) my texts will start failing with the error "Invalid teleservice id".
After some digging I noticed that my phone number in "About Phone" was incorrectly set to an invalid number 1-265-000-000.
I have cleared all caches and reset all settings I can think of. This problems occurs on all SMS applications. So far I have tried: Google Messages; Samsung Messages; Verizon Messages+.
Where does the "About Phone" page get populated from?
My hunch is the internal number of the phone is getting set by some screwy logic and that is throwing off everything that relies on it.
Invalid teleservide id soulution found
I need people to test this solution to make sure it works across all devices as the error seems to affect all android devices under certain conditions. If you would like to read how I came to this solution to help me check my work or you are just interested please keep reading, If you just want the solution feel free to skip to the bottom paragraph beginning with SOLUTION. If you try this solution, which I actually believe to be a solution and not a hotfix, please respond with 3 pieces of information: 1) Did it work. 2) What Android device you use and the version of Android you are using and 3) Your ISP (Internet Service Provider).
This data is very important.
STORY:
So, last month I switched to Android for a couple of reasons after having used iPhones since the iPhone 5. The two most important things to me were being able to stream music using the LDAC Bluetooth codec and having a crack at Samsung Dex to see if I could avoid buying a laptop next year. I was immediately happy with these features that had been the impetus for switching, but then something unexpected happened: the thing that I have always taken for granted, i.e. my phone sending/receiving calls and texts, was incredibly unreliable on this phone (Galaxy S20 Ultra). After doing some googling and finding the official forums (there seem to be 2 devoted to this issue and I will post this both places) I found the incredibly disheartening ‘hotfix’ of disabling WiFi calling to be completely unnaceptable. Not only because I don’t actually get cell service in my apartment but because a $1400 flagship smartphone should certianly not have less functionality in any area that an iPod Touch circa a decade ago.
Normally I would just take my faulty device down to a Verizon store because although I am in IT I specialize in computers more than phones, however since we have been in isolation this began an approximately 20 hour saga via the phone over the span of May 25th to June 19th. After trying everything I could glean might work from google, and following every step that Verizon tech support asked me to try and actually convincing them to update the carrier settings on my account I was finally given the OK to get a replacement device. It is important to note at this point that I had only been searching this error for my model phone and mistakenly had the idea that it was an incredibly rare issue that was a problem with a select few devices.
So, you can imagine my complete and udder shock after getting the replacement phone, setting it up, and getting the Invalid Teleservice ID Error 4 on the second text message I tried to send on the device. It took me about an hour to really get my wits together because at this point I was trying to come to terms with the very possible reality that I was not going to be able to use my phone at home reliably because I don’t have good reception over WiFi. When my faculties returned, I resolved to read every post I could find on this issue.
What I found is that this problem has been around since certain people started installing Android 8 on their phones and that they have been trying to get Verizon to offer an actual solution since 2017. So here we are 3.5 years later and almost 4 generations of Android later and “the best network” has so far failed to offer any sort of real solution to this problem. However, from getting the error on my new phone and seeing that the error was effecting essentially every model device Verizon sells (that runs Android) gave me a key piece of data: the problem has nothing to do with the device.
After getting deeper and deeper into some forums I noticed that one person reported that this problem only occurs for them when they use an Xfinity WiFi hotspot. That was my lightbulb moment. I am also an Xfinity customer. I then started searching the problem from that perspective and found that most of the people reporting the error and mentioning their ISP were either Xfinity or Spectrum customers, and now I was starting to feel like I might be onto something.
In terms of IT, networking is my weakest area. Nevertheless I dove into some forums that have tried to approach this problem from a networking perspective and although a lot of it was over my head I started to suspect there was something about the firewall on Xfinity and Spectrum routers that is causing the problem. After 72 hours of exhaustive testing ( not only is 24 hours approximately my previous record for not having the error, but I used that time to send out as much information via text messaging as possible to try to cause the error) I am ready to posit a hypothesis as to what is actually causing the problem and post the solution that is currently working for me.
As I have noticed that the problem is most likely to crop up for me when I am using Dex and a physical keyboard and have tried to send many texts in quick succession, the idea came to me that somehow trying to send a large volume of data exacerbates a problem that Xfinity and Spectrum routers have reliably delivering packets in the right order and format over the internet to the Verizon network. So, this is what I decided to try, and it has now worked for approximately 84 hours straight and has performed flawlessly under stress testing (Spamming 500 word texts and hi res photos to multiple people in quick succession using copy/paste).
SOLUTION:
I’m sure many of you who play video games have used a function on your routers to get around NAT issues called the DMZ. The DMZ allows you to put a device using a specific IP address on your personal network outside of the firewall and connect it directly to the internet. For a device that exists on this network wirelessly there is a simple step you must take first. You must assign your device a static IP. If you go into your router settings you will likely find that all devices on your network are assigned IP addresses via a system called DHCP. This essentially means your device will probably have a new IP every time you leave the house and return, so we need to make it the same every time so that the DMZ will function the way we want it to. Every router is going to have a slightly different settings menu, but you should be able to find a tab that lists the CONNECTED DEVICES on your network. What you need to do is change your phone from being a DHCP connected device and assign it a STATIC IP address. Finding the option to do this may be harder than actually doing it, all you need to do when you find the option is change the connection type from DHCP to Static and pick and IP address that will work for you. My network uses 10.0.0.XX for the devices on my home network so I assigned my phone to 10.0.0.99. Then I placed the 10.0.0.99 in the DMZ. In my router menu, the DMZ is under ADVANCED SETTINGS and when you select the DMZ tab, simply enter the IP address you chose for your phone.
To recap:
1) Set your phone to a static IP
2) Put that IP in the DMZ
That’s it. A valid criticism of this solution is that your phone is less secure, however I would respond that the likelihood of your phone being hacked is much smaller that that of a PC and if this slightly loosened security really bothers you, just use a VPN. A VPN will keep you safe in a Starbucks on their free public WiFi and it can protect you here (I actually had a VPN when I got my device and originally I thought it was the cause of the Invalid Teleservice error). CAUTION: There has been a crop of predatory VPN services lately that provide working VPNs, but will charge you a ridiculous amount. I use NordVPN (I found a code on YouTube that gave me 70% off six devices on a 3 year plan, that ended up costing about $100) but there are plenty of good services that will allow you to connect to the internet via a VPN on one device for approximately $2-3 a month.
So please, try this and report back. This error has been the bane of my existence since switching to Android and it is completely unacceptable that Verizon has had literally years to do figure out a solution to this problem and yet they have not. My end goal is not to receive credit but to make sure that in the future Verizon Tech Support actually knows how to help people solve this problem, and their techs don’t take your calls and then look the problem up on google, proceeding to be completely transparent in terms of having no actual knowledge of this issue and literally reading the same forums I have already been over and suggesting the non-solutions posted there in order, i.e. turn off WiFi calling and if that doesn’t work turn off ‘Advanced Calling’.
REMEMBER: If this solution does not work for you, please double check that your changes the router you use have stuck. I have previously had routers that will for reasons I don’t understand change the DMZ domain or switch a device back to DHCP from static or simply fail to save your changes properly.
I await responses eagerly.
You need to take your device to your local high street retail branch of your cell provider and ask them to check your SMS/MMS settings
I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.
K_A_Beausoleil said:
I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.
Click to expand...
Click to collapse
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
---------- Post added at 04:37 PM ---------- Previous post was at 04:05 PM ----------
hkjxda said:
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
Click to expand...
Click to collapse
Scratch this... Wifi calling uses it's own IPsec VPN tunnel, VPN clients only encrypt internet traffic, not cell service. Back to square one...
I have a problem with my recently purchased Tasker app. I tried posting on the official Tasker forum (https://tasker.helprace.com/s1-general/problems/top) but after I would click submit, nothing would come up. If anyone knows how to get in contact with the developers other than leaving a negative review on the Play Store that would be much appreciated.
I have a Samsung Galaxy S9 (not rooted) running whatever the latest version OS (Pie I want to say?).
I have a simple Profile setup to Connect to VPN when Wifi is connected, and Disconnect from VPN when Wifi is disconnected (as an Exit task) using the OpenVPN Tasker Plugin.
On rare occasion, everything works as expected.
Unfortunately, the majority of the time, it will indeed recognize the correct state (Wifi Connected), however, it will not connect to the VPN. When I go into Tasker, I see the Profile is green text, and if I go to More>Run Log I can see that it says something to the extent of:
"Active 2 Wifi Connected" then "Start TaskService" then "Running 3 VPN Connect" then "OK 3.1 VPN Connect.com.ffrog8.openVpnTaskerPlugin\n***\n*!" then "ExitOK 3 VPN Connect" then "Stop TaskService" (this is all in reverse order, since I think the run log puts the newest events at the top, but this is how I read them from bottom up).
Tasker even says 1 Task running on the notification bar on my lock screen. However the VPN is not connected. If I go into Tasker, turn off that profile, then turn it on again (via the toggle switch on the right hand side), the VPN will connect as expected and the run log will say the same exact thing.
Likewise for the Exit Task - when I disconnect from the network Tasker seems to recognize the state just fine (evident in Run Log and notification icon in lock screen), however my VPN remains connected (well my guess is it must disconnect for a short period as I transition from Wifi to 4g).
I have tried waiting a while to see if it's just a time issue, but I could wait hours and it will never trigger one way or the other (VPN Connect or VPN Disconnect). I have tried different Wifi networks. The Wifi State Active = "Any". In Android Settings>Apps>Tasker>Battery the toggle for "Allow background activity" is set to on, Optimize Battery Usage is set to off. Likewise for OpenVpn Tasker Plugin.
*Joao or anyone have any ideas?
Many thanks.
Troubleshooting = Because a Piece of Code went
Sorry to say that it looks like I am the 1st reply, as I have no real training in coding or programming myself.
I too recently began to play with such though with the intent to install it on some family member's devices ? However, like you I have not been able to get my desired automation regular enough to share it. When I 1st downloaded Tasker (I think) it had something about a "community" to share & get help with as well as more.
Trying to be helpful I ran a quick search for the specific site & as usual, Google had to go overboard with the results. Still hoping this will help you sooner as they all focus on that particular program:
https://community.home-assistant.io/t/tutorial-using-the-new-auth-system-with-tasker/82423
Just wondering if all the changes to Android OS as a whole may also have an affect on something minor such as whatever we choose to do with "automation" programming? Have seen throughout various post's & news that sort of thing....
for any other poor soul with the same problem, I read a couple of obscure comments on the interweb that the OpenVPN plugin for Tasker is no longer functioning, and all must be run through the Open VPN Connect app (NOT Open VPN for Android app) using intents. I found a guide once, and am testing it now and will report back if it works more reliably. Thank you Lone wolf for your reply.
just to update the poor souls, using intents like I said seems to work more reliably in terms of connecting to VPN. The only problem is if you go out of wifi range, it disconnects, but then are back within wifi range quickly (like somewhere with bad wifi signal), it will not connect again for some reason.