Steve Herrell

Thanks for this. It looks pretty good. I'll just check it here and see exactly what it does. I'm always wary of changing the Cloudflare stuff because what fixes my...

Thanks for this. I'm just checking now. I can't get the `getFactorId` call to return anything other than `{'meta': {'code': 400, 'error': 9204, 'message': 'Browser is not trusted'}}`; is it...

I merged it. We'll see how it goes... and I feel it's always good to line everything up as close as possible so maybe the extra NOOPs will help.

I think that might be a mistake at my end. I was trying to tidy up the differences between the alarms and got carried away. Does patching it fix it?

Sorry, I remember what I did now, I brought the naming into line with the other devices. (You can use devices ID by setting an `aarlo` line option.) I noticed...

No, we don't scope the names, we've always relied on the users to name their cameras (or any device) uniquely. To prevent clashes outside of _Aarlo_ we prefix everything with...

Sorry for the confusion, and thank for the work getting this going. Still no locations enabled in Canada, I'm relying on a VPN and US account to double check this.

@vinnyspb thanks for looking into this, and thanks for trying to change the `MQTT_HOST`. Maybe I'll have to make that configurable or see if I can pick it up from...

I think it's safe to say they've changed their back end, these are the most obvious changes: - They've changed the header requirement for the CloudFlare login piece. I couldn't...

@dw1562 If it's working you can leave it as-is. But if you find you are missing events you could change the back end to `mqtt`.