Posts made by Sato
-
Edit the In and Out tokens on the Gui-O app
Hello Kl3m3n,
How is it possible to edit the In and Out tokens that are generated by Gui-O when adding a connection?
Practical issue:
I have a connection unfortunately only on one cell phone, the respective In and Out tokens were programmed on a controller pcb that I no longer have with me. I accidentally deleted this connection in Gui-O. How can I create a new connection with the same tokens?Regards
-
RE: Hello Gui-O - I'm alive
Hello kl3m3n,
Now it's working, I'm not sure why.
I publishing every 30 seconds.
To control failures I send a counter with the message, so far it's 97 and there have been no failures.
I've also tried closing the Gui-O App, forced it to stop and finally disconnected the phone from that uuid, but it's still working.
As I mentioned earlier, I don't know if it's possible to send and receive between esp32Regards
-
RE: Hello Gui-O - I'm alive
Hello,
Now I've experimented with using the app's uuid and it works but not always, most of the time the message doesn't arrive. I'm going to keep testing and I'll give feedback.
Is it possible that it's not through the uuid but through the In and Out tokens of the Esp32 devices?
Regards
-
RE: Hello Gui-O - I'm alive
Hello @kl3m3n and community,
This is how i try use the Alive function I wanted to implement, but can it make it work.
What i need ist that one Device Esp32 publish a message and a second Device Esp32 receive it.
I know it don't be so, but I'm trying with both tokens to see it anything arrive. I'm a bit confused with this subject.
I have an Esp32 Device named "Test1" registed in the Gui-O App
with these tokens to which I just added /alive
static const char *In2 = "15cab81e-e558-4498-8994-0733c30662f4/alive";
static const char *Out2 = "da853476-386a-8b48-9778-047bd6acf266/alive";This Device named "Test1" publish each minute with these tokens!
aliveNotification = "Hello";
mqttClient.publish(&In2[0], (const char*) aliveNotification.c_str());
mqttClient.publish(&Out2[0], (const char*) aliveNotification.c_str());The other Device Esp32 named "It is Alive" registed in the Gui-O App
which is only used to receive the message published from the Esp32 Device named "Test1"
static const char *In2 = "15cab81e-e558-4498-8994-0733c30662f4/alive"; // Want to subscribe Device "Test1"
static const char *Out2 = "da853476-386a-8b48-9778-047bd6acf266/alive"; //Want to subscribe Device "Test1"mqttClient.subscribe(&In2[0]); //subscribe topic alive - from Device name "Test1"
mqttClient.subscribe(&Out2[0]); //subscribe topic alive - from Device name "Test1"The question is where in the code of the Device name "It is Alive" do I get the message "Hello"?
In the void parseGuioMsg(const String &msg) ???""You have a ESP32 device publishing to uuid/alive""
Must it be used uuid of the App?
I need to use Esp32 to Esp32Can someone help and clarify what I'm doing wrong and indicate how I should do it?
Thanks
Regards -
Selectable language
Hello Kl3m3n,
With the intention of being used in several countries, my project currently supports 3 languages that can be selected in the app.
Perhaps it wouldn't be a bad idea for Gui-O to also have identical functionality for its menu texts and so on. There are many users who don't understand English.
Just a suggestion
Regards
-
RE: Hello Gui-O - I'm alive
Hello @kl3m3n,
I haven't done any tests yet because I'm waiting for the ESP32 to be delivered.
But could you please take a look to see if the way I describe it below is the right way?
Esp_a
In, uuid_a, alive //publish periodically that it is alive (for Esp redundant)Esp_b
In, uuid_b, alive //publish periodically that it is alive (for Esp redundant)Esp_c
In, uuid_c, alive /publish periodically that it is alive for (Esp redundant)Redundant ESP (must subscribe to all ESPs that are connected, which can be many, right?
mqttClient.subscribe(&Out_a[0]); // subscribe to esp_a alive
mqttClient.subscribe(&Out_b[0]); // subscribe to esp_b alive
mqttClient.subscribe(&Out_c[0]); // subscribe to esp_c alive
"" "" "" "" ""
"" "" "" "" ""
// redundant ESP sends push message to 2 cell phones
// don´t worry, changed some Chars
static const char Push1 = "d4f1c682-16b8-3958-5734-51dc22471e0c/alive"; // publish push to mobile1
mqttClient.publish(&Push1[0], (const char) pushNotification.c_str());static const char Push2 = "e4f1c792-26d8-4958-5764-16dc22471f0c/alive"; // publish push to mobile2
mqttClient.publish(&Push2[0], (const char) pushNotification.c_str());Thank you
Best regards -
RE: Hello Gui-O - I'm alive
Hello @kl3m3n,
I also think that the solution is a redundant ESP32 that will only serve to receive and process the periodic Alive signals, and if one fails, it will send an IoT notification with the ID of the failed device.
As such, it seems possible. What I still don't know how to do is create this subscription token of Alive channel to the redundant ESP32. Could you help with a example?Thank you
Best regards
-
RE: Hello Gui-O - I'm alive
Hello kl3m3n and community,
I've been thinking about the question I asked about Alive and I've designed something for you to see if it might work. I think kl3m3n will be the one who can best answer this and maybe even help.
Regards
-
Hello Gui-O - I'm alive
Hello Kl3m3n and community,
Hello Gui-O - I'm alive
I can't remember if I've already asked this question on the forum.
For certain emergency devices and others that monitor specific crucial functions in equipments, it is necessary for these devices to send information that identifies them to the platform they are running on, at set intervals, such as every 48 or 72 hours, as a sign that they are "alive".
This information can be their In or Out Token or another unique identifier for each device that adapts to this functionality.The platform continuously checks these "I'm alive" signals from the devices and, if it detects any failure in the delivery of the signal as it has exceeded the established period, it notifies the application which device has failed to deliver.
This function is valuable for identifying IoT devices that have been installed but are not working, whether due to malfunctions or other factors, allowing for on-site analysis.
There's no point in having equipment monitoring failures if there's a problem with the equipment itself and it goes unnoticed in terms of operation.
I'd like to bring up this topic to see if anyone has any ideas about whether it's possible and the best way to implement it.
Regards
-
RE: critical risk in relying on closed-source platforms for commercial solutions
Hello @kl3m3n,
I raised this question to understand how many hobbyists and professionals are in the Gui-O platform community.
In my case, I have been developing a product for commercial purposes for which I am still seeking investors. The market for the product is global.
I am of the opinion that in the case of commercializing products developed and produced using the Gui-O platform, you should also benefit from a percentage of the profit from the solution (product + Gui-O).
I believe this is well-deserved, and there is no reason to think otherwise.In commercial terms, the most important aspect is not only the value you can derive from the Pro version registration, perhaps with hobbyists, but if you consider the example I provided, that client has approximately 55 employees, which would represent the same number of Pro version registrations. By entering into a partnership as you mentioned,
"This means you get an apk that you can distribute to your users on your own terms,"
you would end up with much more financial return. For example: 7000 x €4 = €28,000
This is an example, and the value depends on the type of final product, but at a minimum, this would be the amount, and reimbursement in most cases would not be immediate but rather phased over time. Clients buy it according to their needs and financial capacity.By maintaining the commitment in all future projects, you would be optimizing the monetization of your work. The apk issue would provide the necessary security for all of us to make commitments with end customers, making it possible to commercialize the solution of product (pcb) + Gui-O in a win-win manner.
Give it some thought. In my case, I will continue to try to find clients for the solution, but I am already more reassured knowing there is openness to leverage this good solution for both sides.
I hope that other professional users can join this partnership model and share their opinions.
Regards
-
RE: critical risk in relying on closed-source platforms for commercial solutions
Hello @kl3m3n and community,
I apologize for the confusion. The article I shared is not a cause for concern; it was presented merely as an example.
Specifically, I wasn't referring to the MQTT broker for which the generous kl3m3n provides a tutorial for those wishing
to port it to their own server. The support he provides is, and always has been, exemplary.The main concern is related to the use of Gui-O as a platform for commercial products. I've had the opportunity to discuss
this issue before. When using Gui-O in commercial projects, one of the first questions from clients is usually about the
platform on which the product is run and whether it is provided by the same supplier as the final hardware product.To illustrate, consider a potential client with over 7000 devices, each of which could be equipped with a PCB. Here, the concern is evident: we cannot guarantee the client the continuity and maintenance of the Gui-O platform, as we have no influence over its maintenance, or worse, its continuity.
During commercial negotiations, the decision to purchase a product can represent a significant investment for the end customer.
Thus, the choice also takes into account some guarantees related to what was mentioned earlier.I want to clarify that, personally, I love using Gui-O from the very beginning. However, I bring up this issue because I believe some clarification is helpfull, especially when it comes to products with commercial purposes.
Regards
-
A small percentage of the profit of any sell pcb
Hello,
I've never mentioned it until now, but something I've already thought about and will certainly do whenever I manage to sell boards from my project, is to give kl3m3n a small percentage of the profit from the sale of each board.
I think this is well-deserved, given the enormous amount of work he has done and continues to do, without which the majority of the Gui-O community would not have been able to develop projects with the resources that Gui-O offers us.What do the members of this community think about this?
Regards
-
critical risk in relying on closed-source platforms for commercial solutions
Hello,
It's not that I've already managed to commercialize the project I've been working on for 3 years, and in the beginning I even addressed this type of situation with kl3m3n and naturally it's a concern and something for anyone who wants to acquire solutions that use closed source platforms.
How can we answer questions about this to a potential client?
Microsoft's withdrawal from Azure IoT Central highlights a critical risk in relying on closed-source platforms for commercial solutions. This move reminds us that by choosing proprietary solutions, we are at the mercy of suppliers' business decisions. This can lead to the need for costly restructuring or even the total loss of the investment if the service is discontinued. It's a wake-up call to invest wisely and consider the long-term sustainability and adaptability of the technologies chosen. More details at [The Register]
https://www.theregister.com/2024/02/15/microsoft_retires_azure_iot_central/Regards