Separate PC.
And in answer to your previous question:
Separate PC.
And in answer to your previous question:
Ok. That’s really strange. Try adding ios:
to configuration.yaml
, restart HA and the have one more go at listening for ios.action_fired
give it a few second to get going and then try the actions. Otherwise we might be looking at resetting the app.
Do you see ios.action_fired
listed under Available Events?
Made no difference.
Yes, two listeners.
I really dont think the events are being fired on the phone. As I said before, the haptic feedback is a double buzz like a ‘not allowed’ warning.
iOS 13.2.3, iPhone X.
Double haptic is what I get on a working action. I’m confused as to why you don’t see the events when listening for them. Even on the ones that are working
Ugh. Because event listening does not appear to work in firefox. Chrome reveals:
Event 1 fired 9:02 PM:
{
"event_type": "ios.action_fired",
"data": {
"sourceDeviceName": "iPhoneX",
"sourceDeviceID": "iphonex",
"sourceDevicePermanentID": "240A74A2-D92F-48fudge",
"triggerSource": "widget",
"actionName": "Arm ",
"actionID": "374D6971-2C32-4759-A44blahblah
},
"origin": "REMOTE",
"time_fired": "2019-12-02T10:02:06.415562+00:00",
"context": {
"id": "52866d918c9a405991a89obscured",
"parent_id": null,
"user_id": "f17a5278004e463d9redacted"
}
}
Ok it’s the same issue I had above. That one has a space after ‘Arm’. Check your actions in app either the Event name has a space at the end of it
Even when editing the action it was not apparent that the space was there. I had to delete the entire string and re-type it.
Now working as expected.
Thank you.
Now I suppose I should raise an issue about the firefox event listener.