Feedback

Is it possible to define a subscriber type MQTT client in AppBlocks? For publisher clients there is a block, but for subscriber, no? Can you help me with some advice?

+5V doesn't set the board option for external power. Consequently there is a red triangle warning: Project Errors Board Error: Not enough power for 5V. Add a Tibbit #10 or Tibbit #33

"Try This Project" button that opens every Tutorial in anv edit window like: https://app.appblocks.io/app/project/edit doesn't show on vertical devices like mobiles, tablets...

Automatically generated variables doesn't change "automatically" after you move a tibbit from one socket to another. Now you have to delete the tibbit and place a new one in another place.

The AppBlocks editor is constantly loading/reloading (see image) A few dialogs that try to popup get stuck in a never ending presentation loop

I tried to generate a app for send RS232 commands, but I can't find the way with appblocks

We have/will end up using a variety of Modbus sensors with our devices. I'd love to be able to write a single firmware to handle emission/processing of sensor data. The way I see this working is we can define multiple devices in Modbus configuration (with unique IDs and whatnot) and we have a block that is fired whenever any Modbus data is sent back which has the params of the data and the device ID

For some reason, when storing an MQTT subscription in a setting and then updating it on boot results in the max length being set for the value. I've seen this happen in both of my projects.

Would it be possible to unify my accounts? I have an 'email' account and a Google OAuth-setup account tied to the same email address (however, the Google OAuth authentication is broken for me current)