Remove remaining mqtt and update AWS ids

[andrewleech]

If I recall correctly all MQTT functions were removed from the mobile app but the unit still seems to use it.
I believe they replaced the same status update request with this web call but not sure if it improves the delay.
See RefreshData function here:
https://github.com/mrhteriyaki/MagIQTouch-Control/blob/master/SeeleyControl/SCData.cs

I'm also not sure if the AWS IDs were a part of it too, I got the feeling there were 2 backend systems and they were migrating systems, mine stopped working weeks after the app was updated. I'm not familiar with AWS to know the significance of the IDs only that they've been changed in the app.

Originally posted by @mrhteriyaki in #1 (comment)

[andrewleech]

@mrhteriyaki I've copied your comment out here to keep note of it as I think it'll be important. Thanks for the link too.

I did think it was likely unnecessary to still have any mqtt messaging left but haven't had time to look into replacement web api's for them

[andrewleech]

I don't think the web API can do anything to improve the delay because certainly nothing has changed in the protocol between AWS, the magiqtouch wifi box and the magiqtouch panel itself. When I was originally sniffing traffic between these to figure this all out I concluded the delays were very much in the magiqtouch hardware and there's not much can be done to fix that.

However, the web API does seem to have one big advantage; making further changes during the delay period from a previous change seem to behave better.

Previously touching anything in the app before the previous setting had gone through completely often ended up reverting the first setting, I don't think that's as bad now.