Thanks. My plan is to try and introduce a profile in the project to allow an easy upgrade of the Tasker project on the mobile device once the project is already installed.... That or looking at some of the App-based options for projects in Tasker. Mostly want to just get it setup first, then expand on some of these ideas.
Actually, that is not a permission issue. The configuration does not appear to have been sync'd to Tasker. Have you created the virtual device on HE yet? In the MC App? If you have, try running the configure command... That should send through the local and cloud API endpoints for the MC App
Yes, I have two devices configured in MC. The complaining notifications seem to have stopped on their own shortly after boot-up, so maybe it was a timing issue. I went ahead and hit Configure just to be sure.
Sounds perfect for my use case. What I want to do is check the HE mode when the Android device is restarted to catch up with any mode changes that occured when it was offline. Currently, I see three variables (%mc_LastBatt, %mediaVolUnmuted, %newVol) but not one for mode.
Hmmm.. I'd expect it to be an issue between loading the Tasker project and doing the setup on HE.... I need to put some smarts into the Tasker project to only send / turn on the reporting profiles once the setup has been done on HE.
This isn't quite how it will work currently. The MC App on HE subscribes (keeps tabs on) changes in mode on the HE hub and when a change is detected sends this to each MC mobile device. I could probably setup a Tasker profile for system boot poll HE for any updates. This could also be used for those who choose to not use cloud comm's, performing the same sync when local comm's are re-established.
My understanding is that "variables" are global, such as the last battery reading and media volume variables... I could be wrong about that...
EDIT - I was wrong. See my correction at the end of this post.
The mode, along with other configuration settings, are Project Variables, specific to the MC Tasker project. You can see these by long-pressing the project name in the bar at the bottom of the Tasker App and selecting Project Properties from the pop-up. The mode variable is mc_mode.
What I was describing earlier was to potentially store this in a regular variable instead, like the battery and volume variables, making the mode available in your own projects / profiles. My initial intention was to keep everything self-contained in the project, but can't remember why I didn't do this with the battery and volume one's.... I need to look at this some more...
Correction Re Variables:
From the Tasker documentation:
Global vs. Local Variables
Variables which have an all-lower-case name (e.g. %fruit_bar) are local, meaning that their value is specific to the task or scene in which they are used.
Variables which have one or more capital letters in their name (e.g. %Car, %WIFI) are global , meaning that wherever they are accessed from the same value is returned.
I am getting somewhat closer to what I will consider a beta release of this App / driver, including the following features I am still working on:
- Reporting current states - Screen brightness, volume settings, do not disturb and more
- Change mode from the mobile device - Including from the home screen and quick settings
- Monitoring of Bluetooth devices connected - Useful for detecting when the device is connected to a car
- Call and Message Monitoring - Missed messages, incoming call and in-call states
- GPS Location Monitoring - Potentially multiple locations
- Turn WireGuard VPN On / Off
- Communicate over VPN when away from home
2 Likes
I'm also playing around with NFC tags, if anyone is interested.
Not sure exactly how I will use them just yet, but have been interested for a while to see what I can do. Have just got triggering of a Tasker profile working with an NFC tag, writing to the tag and launching an app on my phone. With this being the case, and the other features I have working already in Mobile Controller, no reason I can't send a message back to HE when a tag is scanned.
Any ideas or requests are welcome.
"Keep Alive" post....(Wishing this was a beta release....)
Still interested
1 Like
That's good to know. I expect others will be as well.
FYI - The changes will likely require a full replacement of the app / driver / tasker setup.... But it will be worth it 
Hello Simon. I've been away from Hubitat, mostly just letting things run and ignoring the things that break. Are you still maintaining this project?
1 Like
TLDR - yes....
I haven't "released" anything for some time, partly because I indulged myself for some time in new features, including Bluetooth device and VPN tracking, alongside producing a "solid" release for new users. A "solid release" for me includes a seamless, well curated user experience... which takes time to develop. Both in terms of the app in HE as well as how best to construct the Tasker elements.
I have certainly been working away on it in recent weeks... I would really like to release something new, but am struggling to have some new features in a state I am happy with... More a problem for me than anything else. I think I just need to accept where things are at and release something... My main concern is releasing something that I need to write extensive notes on for people to follow or to help them avoid issues I know exists...
To give some overview of what I have been looking at in recent times.... I am at a point where I would be happy to produce an app for an Android device, but need to complete a process for exporting and importing settings should an update be applied. Something I am close to having complete, but need to test more extensively.
I might consider releasing an early version in the coming days.... We will see....Needless to say that your prompt has encouraged me to "just do it"
3 Likes
I'm having a new issue using doNotDisturbOff in a rule. doNotDisturbOn works but doNotDisturbOff in the same rule gives this log:
Funny thing is that doNotDisturbOff works fine when I issue the command from the device. Here is that log:
Is that enough for you to tell me what I'm doing wrong? Thanks for your help!
Looks like you are providing a parameter value in your rule when calling doNotDisturbOff, which it does not need (or expect).
1 Like
That fixed it. Don't know how that happened. Thanks!
1 Like
I'm having the same problem, so first I tried a reboot since it seemed to have worked to fix it for him, but that didn't work for me. I've ran the configure command but I noticed only the cloud api endpoint was set in the Project Properties, not the local api endpoint. I set the local api endpoint manually, but that still didn't fix the problem.
In case it matters.
I have a Pixel 7 Pro.
Tasker version 6.5.5-beta
Hubitat Platform Version 2.4.1.167
Forum won't let me embed pictures, let's see if it will allow me to post a link.
imgur .com /a/lwjrjRh
I figured the picture would explain what problem I was referring to, but since it didn't let me embed them (or post a link without adding spaces into it), I should probably mention which problem, I'm having the same permission issues as he did, but not sure if they are actually permission issues or what.
Welcome to the Community @CoryW , great to see you trying to use this App.
You should join the Hub Owners group here on the Community. To join, click on the "hamburger" icon in the top right of the screen (between the magnifying glass and your avatar), select groups and then click "Join" in the Hub Owners group. This will allow a few other options when posting on the Community, used as a safeguard against bots.
I was able to see the images you posted and they are the same as what @CAL.hub was experiencing.
No, like @CAL.hub it is the URL configuration item not being populated in Tasker, i.e. the local endpoint URL in your case.
Running the configure command seemed to work for @CAL.hub . In the screenshot you provided there was this notification:
I am wondering if you need to update a setting inside Tasker to allow external access, e.g. by my App running on your HE hub?
https://www.reddit.com/r/tasker/comments/d17g5n/external_access_denied_for_tasker/
Take a look at this setting and see if you adjust it and try the Configure command again, whether that resolves the issue.
So, I guess it was sort of a permissions issue after all lol. My previous phone died on me out of no where, and it looks like I forgot to change that setting on my new phone.
That fixed it, but not right away. So I changed that setting, and the errors were still there just counting by the second on there, I don't use tasker notifications for much, but I assume it was because it was messed up from the start, I would need to reboot the phone/tasker to fix it. I rebooted the phone and pushed the config, the errors didn't come back right away, but they did come back. So I figured starting things over with the task might be worth trying, just so see, so I deleted the project, rebooted the phone, imported the task back in, pushed the config button on the phone, and the error notifications have seemed to stop, and I believe it is working now for the most part. It still didn't automatically set the local api endpoint, so I did that myself again.
This is the error that shows up in the Hubitat log whenever I press the config button:
dev:979 2025-05-03 02:09:40.648 AM error sendTaskerCommand: org.apache.http.NoHttpResponseException: 192.168.0.30:1821 failed to respond
dev:979 2025-05-03 02:09:40.637 AM debug sendTaskerCommand: Path = configuration/hedeviceid, Body = mobileDevice-1843151904, IP Address = 192.168.0.30, Port = 1821, MC URL = mc
dev:979 2025-05-03 02:09:40.635 AM debug sendTaskerCommand: Command sent. Response = [status:Access Token Received]
dev:979 2025-05-03 02:09:40.492 AM debug sendTaskerCommand: Path = configuration/heaccesstoken, Body = [ MC TASKER ACCESS TOKEN ], IP Address = 192.168.0.30, Port = 1821, MC URL = mc
dev:979 2025-05-03 02:09:40.489 AM error sendTaskerCommand: org.apache.http.NoHttpResponseException: 192.168.0.30:1821 failed to respond
dev:979 2025-05-03 02:09:40.474 AM debug sendTaskerCommand: Path = configuration/helocalendpoint, Body = http://192.168.0.5/apps/api/259, IP Address = 192.168.0.30, Port = 1821, MC URL = mc
dev:979 2025-05-03 02:09:40.445 AM debug sendTaskerCommand: Command sent. Response = [status:Cloud API Endpoint Received]
dev:979 2025-05-03 02:09:40.209 AM debug sendTaskerCommand: Path = configuration/hecloudendpoint, Body = https://cloud.hubitat.com/api/[ MC CLOUD ENDPOINT ACCESS TOKEN ]/apps/259, IP Address = 192.168.0.30, Port = 1821, MC URL = mc
So it looks like it is sending somethings just fine, but having a problem on others?
I know this project is still in the very early stages, so tell me when I touch on something that isn't exactly broken, rather just not finished.
Through the Hubitat Mobile Controller while connected locally using the Direct Tasker HTTP Request option:
So far I was able to see that the battery status is being updated, and I was able to use the pause/play, volume up/down, screen on/off, and use device notifications (both custom and not),
The things that I have tried that didn't work is the Play Text. However, I don't know if I'm using it correctly, the wording Play Text makes me think it will say the text out loud, but the placement of the option, with it being bunched up with the pause/play and tack options is what makes me the doubt that I have that correct, does it mean for me to enter a file path and filename to play?
Regardless, the error I'm getting is:
[dev:979](http://192.168.0.5/device/list#)2025-05-03 02:02:58.873 AM error org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_simnet_Mobile_Device_1220.playText() is applicable for argument types: (java.lang.String) values: [local test using Direct Tasker HTTP Request]
Through the Hubitat Mobile Controller while connected locally using the AutoRemote Message option:
I have tested the AutoRemote plugin app itself using the link it gives me, and successfully sent myself messages to myself in the browser using, so the plugin app itself seems to be working fine.
When it comes to using it within Mobile Controller, it doesn't seem to be working.
There is only one error sent repeatedly.
dev:979 2025-05-03 01:41:16.867 AM error sendAutoRemoteCommand: org.apache.http.conn.HttpHostConnectException: Connect to 192.168.0.30:1817 [/192.168.0.30] failed: Connection refused (Connection refused)
So I think I'm probably missing something that I need to setup for that to work?
Through the Hubitat Mobile Controller while connected via the cloud using the Direct Tasker HTTP Request option:
I made sure to set the Use Cloud Communications switch on, and pressed the config button again, just in case that is required before disconnecting from my wifi.
It still seems to be trying to connect to my phones local ip, and I didn't see anything get sent from the phone to let the hubitat know it was disconnected, so although I have some error's, I'm guessing this part is still being worked on, so I will hold off with doing any more with that.
Weirdly my battery reporting appeared to stop recently, along with other status updates, even with a more advanced version I am running . I'll need to work through your issues (and mine) as part of getting this finally released. I appreciate your efforts in providing feedback, it really does help.
My bad, I was wrong on it not working with auto remote. It's been a while since I've used it, and that was with my old phone, or possibly the one before that, I didn't realize it had a password set. after clearing it, I used it to pause and unpause but haven't really checked much more then that yet.
1 Like
