#Similar problem with watch actions and

1 messages · Page 1 of 1 (latest)

tacit schooner
#
event_type: ios.action_fired
data:
  actionID: lock_door
  actionName: lock_door
  sourceDeviceID: iphone
  sourceDeviceName: Michael’s iPhone
  sourceDevicePermanentID: F9567FD2-<snip>
  triggerSource: watch
origin: REMOTE
time_fired: "2022-09-12T21:15:28.940615+00:00"
context:
  id: <snip>
  parent_id: null
  user_id: <snip>```
#

Deleting the integration and re-launching the App to re-create the integration still doesn't solve the sourceDeviceID problem but it did cause the integration and my previous thread's issue about the notify service call to function correctly

#

I could change my automation to use the Permenant ID or the sourceDeviceName instead, but just wanted to flag it as a problem I've run into.

#

Source id used to be michaels_iphone

tacit schooner
#

@quaint cipher without having ever looked at the code or setup the build chain on my mac, how complicated would it be for me to set sourceDeviceID to pull from the same location as the notify service name stuff?

quaint cipher
#

not hard at all. it should do that.

tacit schooner
#

Cool.

I'll see if I can find a cycle to do that.

quaint cipher
#

lmk if you need help. i may be a bit incommunicado this week - but i'll be around next.

tacit schooner
#

yeah no worries. Just an annoyance with apple changing things in the update.

Figured i'd try and fix it

#

Just a free time question

quaint cipher
#

oh, i already made 'sourceDeviceName' use the override name

#

what are you seeing?

#

you'll need to make the 'deviceID' var turn into a func, pass in server, and use the override the same way as the first thing i linked there which asks the server for it

tacit schooner
#

👍

I'll see if I can find a cycle do get that in

#

Never looked at swift language before so will have to grok that all.

quaint cipher
#

it's pretty similar if you squint your eyes to something like javascript