nebulous

> Data rate limiting until app usage is active. also reads to me as potentially "don't have the stat send anything but an alive message until the new version of...

@mattster98 any news on fallback with 8883 blocked? It's nice to see Carrier joining the 21st century using mqtt to control IoT devices, but it is rather annoying that in...

This _might_ be a timing issue - I changed the default Carrier API refresh timeout to 5 minutes - which is what I have mine set to and don't observe...

Sorry it's not going to work out for you. I'd love to be able to reproduce the problem to see if I can fix it(and always happy to accept patches),...

@GitHubGoody I recommend using a [json formatting plugin](https://chrome.google.com/webstore/detail/json-viewer-pro/eifflpmocdbdmepbjaopkkhbfmdgijcc) to more easily spelunk json output, but to answer your question, each set of values in the `cost` and `usage` structures of...

For reference here's the general sequence of events. Of note, the server/carrier app never pushes data to Infinitude or the thermostat - it is a polling-only operation. Just looking at...

Thanks for continuing the diagram - it is indeed slightly clearer what you're trying to say, but I'd much rather solve the problem directly vs yet another weird bandaid in...

ok I think I'm closer to following then. Returning an invalid config response to the thermostat(after allowing the stat to update with Carrier's supplied config) causes the thermostat to trigger...

The GPT4ALL v3.0.0 client has a "Server Chat" section which correctly shows the response to queries received from VSCode/Continue as they arrive, but I can confirm that when configured as...

It's entirely possible(and I think probable since touch stats can be made aware of SAMs) that settings can be pulled from a touch stat, but at minimum they live at...