@SteveV Hi.
First, try to reboot the RPi and retry.
If this does not work, try running the commands with sudo, e.g.:
sudo apt install python3-paho-mqtt
Regards,
Kl3m3n
@SteveV Hi.
First, try to reboot the RPi and retry.
If this does not work, try running the commands with sudo, e.g.:
sudo apt install python3-paho-mqtt
Regards,
Kl3m3n
Instructions can be found here:
https://www.gui-o.com/how-to-guides/how-to-translate-gui-o
Hello GUI-O community!
There are roughly 700 texts that can be displayed to the user within the GUI-O application.
Some of them are shown often, while others will probably never be shown at all (maybe in some very specific cases). Nevertheless, all texts deserve equal right to be translated
I am looking for translators for various languages. If anyone is interested to help, please send me a private message via Chat. Please specify which language you are interested in to translate. The source language is English.
The translations that are already finished are (I will update the list as soon as new translation in added):
Thank you.
Best regards,
Kl3m3n
@Sato Hi
It is possible to share the device via the email for example (settings -> quick pair -> IoT devices -> tap on "share" icon for the device). There is a QR code attached that can be scanned with GUI-O app to re-create the associated device.
If you deleted the device before sharing this QR code, there is no option to manually enter the In and Out tokens.
Best regards,
Klemen
@Sato Using MQTT, it is possible to send messages from any device to any device that is connected to the same broker.
Best regards,
Klemen
@tgpa123 I understand.
In my opinion, this is not a very transparent user feature - updating field from another source, while user is typing in the same field.
I will put this on hold for now. If there should be a need for this feature in the future, I will consider it again.
Best regards,
Klemen
@Hub said in Selectable language:
Hello @kl3m3n,
I can help with translation into Polish.
Regards,
Hubert
Thanks!
First, I need to prepare some stuff for this feature. I will let you know.
@Sato said in Selectable language:
Hello @kl3m3n,
Sure, for german too
Regards
Thank you. I will let you know when I have everything ready.
@Hub Hi!
What about using |TI (text input) widget? I can probably add some validators to ensure the entered text is HEX.
Regards,
Klemen
@tgpa123 Hi.
I tested this on my device with ESP32 and can send longer data than 20 bytes. It seems that the server and client negotiate a larger MTU value in my case.
Nevertheless, I can chunk the data so that there is never more than 20 bytes by default. So, for messages greater than 20 bytes, multiple packets will be sent. Of course, the last packet will still be terminated with CRLF.
Regards,
Klemen
@Sato This is possible, yes. Will put in on TODO list. Will probably need some help for translations... Are you willing to help for Portuguese?
Regards,
Klemen
@tgpa123 I will need to check this. If I understand correctly you would like a number field to be both indicator and control?
I think this could potentially lead to usability issues due to not conveying clear meaning to the user... Is it a control or an indicator?
Best regards,
Klemen
@tgpa123 This is doable... I can probably roll out this feature with the next release.
Regards,
Klemen
When pushing to the phone using MQTT channel...
@Sato said in Hello Gui-O - I'm alive:
"d4f1c682-16b8-3958-5734-51dc22471e0c/alive"
This should not be "/alive" but "/notifications". I think other stuff looks ok!
Regards,
Klemen
@tgpa123 Just one more question.
When using the BLE Terminal app, you are connecting to the same device with the same configuration (as in GUI-O case)?
Regards,
Klemen
@tgpa123 Hi.
I think know what is going on. It is probably related to Android default MTU size for characteristic (23 bytes, 3 bytes are used, so only 20 bytes available)...
I will fix this by setting larger MTU size or chunking the data. Will have to analyze to implement best option.
Thanks for the information.
Regards,
Klemen
@tgpa123 Hi.
Can you give me the total length of the payload? What is the text input UID?
Thanks,
Klemen
@Sato Hi.
For starters, you could simply use the same topic with /alive appended.
You have a ESP32 device publishing to uuid/alive at some interval. The redundant ESP32 is subscribing to this topic and handling the alive packets. If the packet is not received within the desired time interval, it can react accordingly (send push notification).
Regards,
Klemen
@Sato Hi!
I think the best way to achieve this is to use a redundant ESP32 just for "alive" functionality. Push notifications can than be used to deliver the failure messages to the Android device even if GUI-O app is not running (as they run on top of Google messaging service).
But, GUI-O app cannot monitor this, because:
It can only connect to a single device at a time. It does not make sense that multiple devices control a single GUI. Major changes to logic and app functionality would be needed.
It cannot run reliably in the background due to Android process handling. App can be killed anytime if the Android OS deems it necessary.
Best regards,
Klemen
@Sato Hi!
I greatly appreciate your suggestion and dedicated support to GUI-O!
But I think that each of us should benefit from our own work. The PCB (and FW running on it) is your product. GUI-O is my product and if you buy GUI-O license(s) for your clients, I will benefit from this.
It is of course possible to make some more detailed arrangements (some sort of cooperation, etc.).
Does this sound reasonable?
Regards,
Klemen