Tasker not talking to Autovera but Autovera talks to Tasker

Plugins & Plugin Development Unmaintained
1

Ive posted this in the Autovera Forum but Im crossposting this here in case anyone can help.

Up until last week Ive had no issues with Tasker and AV - however last week my profiles and tasks got wiped out from another tasker plugin and I had no backup so I was forced to recreate (also forced some housekeeping in tasker).

When I recreated a few of my tasks Ive found that Tasker wont talk to Autovera for even the simplest of tasks like turn on a light - however I can go to that device directly in AV and toggle that device successfully.

Weird thing is that autovera WILL update tasker any status changes (profile)

The task:
Tasks - Plugin - autovera - devices - Light -
Action:State
State:Turn On
Service:power Switch

When I run the “turn on light” task, tasker sits there for about 30s and then returns:

10.46.24/ActionArgBundle key: DeviceName: replace String value with null
10.46.24/ActionArgBundle key: DeviceId: replace String value with null
10.46.24/ActionArgBundle AutoVera Devices: DeviceName: ignored replacement specified for null value
10.46.24/ActionArgBundle AutoVera Devices: DeviceId: ignored replacement specified for null value
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:newLoadlevelTarget
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:newArmedValue
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewMode
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewModeTarget
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:EnergyModeTarget
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewFanSpeedTarget
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewDirectionTarget
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewApplication
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewCurrentSetpoint__heat
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewCurrentSetpoint__cool
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewAutomaticWhiteBalance
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewFixedWhiteBalance
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewRotation
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewBrightness
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:NewColorSaturation
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:presetNumber
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:Id
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:Name
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:newText1Value
10.46.24/ActionArgBundle AutoVera Devices: extra key not found in bundle:newText2Value
10.46.24/E FIRE PLUGIN: AutoVera Devices / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 12 bundle keys
10.46.24/E AutoVera Devices: plugin comp: com.joaomgcd.autovera/com.joaomgcd.autovera.broadcastreceiver.BroadcastReceiverFire
10.46.24/E add wait type Plugin1 time 30
10.46.24/E add wait type Plugin1 done
10.46.24/E add wait task
10.46.54/E Error: null

Any help would be appreciated.

2

I see that you are using State. Have you tried event?

3

I’m having this problem… exactly. Was there ever a solution?

4

Well I figured it out, with a new update to Android with power save mode on somehow disables tasker. Least this worked for me.

5

I’ve been getting this a lot recently.

A reliable solution is to remove AV and reinstall it.

Also sorts out authentication issues.

6

After the most recent Samsung update, again Tasker wasn’t working. What I did was refresh my devices and auto Vera and it also refreshes the scenes at the same time. That works for me this time.