Excellent work by @alvarolb and team! The improvements to the Time Series Chart widget were very good.
Approving the opportunity, I would like to suggest some improvements:
Include a two-factor authentication (2FA) option, similar to Google Authenticator. With this, the Administrator will be more secure in relation to the access of the “root” account.
Include the “Decimal Places” field in the Tachometer widget
NOTE: As shown in the image, the Widget Tachometer does not have the “Decimal Places” option, similar to Widget Text. This ends up “confusing” the information. In the image, the Tachometer widget shows “053.00”, but ideally it should show “53”, when setting “Decimal Places” to 0.
Allow to change Widget Tachometer elements that represent the numeral. Ex: Change the color of the label (currently dark) to highlight the text information Ex: 53
Include the field “Text Color” and “Text Size” in the Clock Widget, just as it already exists in the Widget Text. Currently, the Clock Widget takes up a lot of space on the desktop browser dashboard. With this option, the Clock Widget could get smaller and take up less space on the screen.
- Modify Widget Slice to only send data when the user unclick. Currently, if the user clicks and moves the slice strokes, he sends information to the device. The most appropriate behavior would be for Widget Slice to send the data when the user unclick. The current behavior overloads the GSM module, which uses AT commands. I will try to make a GIF with the serial monitor and the Slice widget. It is easier to demonstrate that it sends a lot of data to the device while moving “the ball”. Ideally, it would be for the user to send only when the user unclick “the ball”.
Allow Widget Slice to be set to Read Only. This ensures the use of the Widget Slice (data input on the device) and the visualization of the data, but it avoids accidental changes that the user can make when navigating the dashboard, such as an accidental click.
Check if the divergence in the Google Chrome Desktop and Chrome Mobile timer would be a bug. In Google Chrome Desktop, the timer information (from 5s) is displayed correctly Ex: Now, 1s, 2s, 3s …
In Chrome Mobile, the same information was presenting to me as: Ex: 1m, 55s, 56s, 57s, 58s, 59s, 1m, 55s …
That is, instead of “Now”, “1m” appeared. The count started at 55s on chorme Mobile, instead of “1s”
- Include an alert in the button “Generate Random Credential” warning the user that there is already a registered credential. Something like “There is already a Credential registered. Do you want to change the credential?” “Yes No”. This implementation can prevent the user from changing the currently registered credential by accident.
I have been studying the Thinger.io platform in recent weeks, as I intend to hire the Thinger.io Cloud service for the company I intend to open. If you have more suggestions, send them here.
Thank you very much for the improvements in version 3.1.0 and 3.1.1