Jake Burhenn

We are seeing this issue with some of our hubs as well. The strange thing is the same code works with other hubs. It appears to be occurring in the...

Added a change for the queue limit exceeded error. Now it only recreates the sender link instead of doing a full reconnection since that error doesn't require a reconnect.

Do you mean the command is received with a slight delay after the widget value is changed in the UI? If so that might not just be Python, it could...

So Python 3.7 & 3.8 have the problem? I'd try posting this issue on http://community.mydevices.com/ if you haven't already and see if someone there has seen it. You might also...

We aren't able to reproduce the issue here currently, but there are a few options you could try. 1. If you don't need to use the command functionality to send...

You comment out the `while (error != MQTT_SUCCESS)` line and the library works? The ports used by the library are 1883 and 8883. You might try using another MQTT library,...

It hangs when you try to print out `requestedQoSs[i]`? Are you doing that after the `writeChar(&ptr, requestedQoSs[i]);`? Does it also hang there if you try to print it out at...

Strange that setting it to 0 works, but not using the enum 0 value that is cast to an `(int*)`. Maybe there's some issue with that cast on a MKR1000....

Thanks for your submission. Does this completely support Pine A64, including I2C, SPI, etc.? Or is it just the default widgets, like CPU Temperature that it supports currently?

Sounds good. If you get the I/O changes done feel free to add them to this pull request.