I am sure that the issue is Android's new restrictions on implicit intents. With very few exceptions, later Android versions require that the target package be specified when sending broadcast events. I have confirmed this using Tasker's send intent to try and trigger a response. If I fail to include your app's package (outlined in red in the attached screenshot) within the send intent specification, nothing happens. When I do, I see the server showing my message in a toast.
So for this to work on later android, you need to include the tasker package in your broadcast event's parameters. I think you want to use the Intent's setPackage() method and pass in the package name for Tasker (net.dinglisch.android.taskerm).
This is what I had to do with my app SystemSettingsForTasker - which also communicates events to Tasker via intents.
I am sure that the issue is Android's new restrictions on implicit intents. With very few exceptions, later Android versions require that the target package be specified when sending broadcast events. I have confirmed this using Tasker's send intent to try and trigger a response. If I fail to include your app's package (outlined in red in the attached screenshot) within the send intent specification, nothing happens. When I do, I see the server showing my message in a toast.
So for this to work on later android, you need to include the tasker package in your broadcast event's parameters. I think you want to use the Intent's setPackage() method and pass in the package name for Tasker (net.dinglisch.android.taskerm).
This is what I had to do with my app SystemSettingsForTasker - which also communicates events to Tasker via intents.