Has anybody been successful in connecting a LOGO 8.4 to blynk via mqtt.? This version can connect to a MQTT Broker directly. (Previous versions could not)
I have tried, but I am not sure what information from Blynk is applicable to the fields in the authorisation page of the Logo
Blynk issues a authorization token for each device in wich field is this token going?
There are 5 fields under the second step of Mqtt registration on the LOGO
MQTT Broker URL: Here I am using "‘Blynk.cloud’’
Port : 1883
MQTT client id: ??
Username: ?? (Is this your Blynk username?)
Password: ?? (I have tried putting the auth token from blynk here)
It’s usually better to use the region subdomain in the URL such as “lon1.blynk.cloud”
The subdomain relating to your account can be seen in the bottom right of the web console, or in the “about” menu of the mobile app.
Correct.
It’s up you what you use here. This is how your broker refers to the device, so any non-null string of up to 64 characters in UTF-8 format.
No, it is simply “device” (all lower case, exactly as I’ve typed it here).
This is indeed your Blynk Auth Token.
It’s always a good idea to read the documentation, as all of this info is there…
We did read the documentation but the Fields on the Siemens LOGO 8.4 are not very descriptive on what goes where.
We now have the device showing online but, there seems to be a disconnect on how we need to configure the publish and subscribe topics between Blynk and the LOGO8.4 PLC.
I also tried to connect Blynk to the Logo 8.4 PLC and the connection is successful, but the messages sent by the PLC do not correspond to the messages that Blynk expects. It should be possible to modify the messages received on the Blynk side.
We got the Logo 4.8 working, but had to jump through a lot of hoops. We did the following.
Connected LOGO 8.4 to another Mqtt broker (I used HIVEMQ)
Take the output from HIVE and feed it into Node red
Connect to Blynk via node red
After all this. All you have accomplished is to change the datastream from the LOGO from “datastream” to ‘‘ds/datastream’’
The LOGO connects to HIVEMQ without any issues. It connects to Blynk and even shows data transferring in the developer mode but cannot manipulate the widgets due to the /ds not being part of the message.
We are currently looking at installing 100’s maybe 1000’s of these controllers in the water sector and would very much like to use Blynk because of its many features.
We are ready to subscribe to the pro Plan, but not if this problem exists. I am sure this is well within Blynk’s capability’s to offer native support for this controller.
I have sent a e-mail to Blynk and they responded positively by saying they will add it to their future roadmap. My problem is when?
In the meantime we are not able to upgrade as we do not know if they will address this issue even on the higher tiers.
Running a separate broker and node red is not a scalable solution. At scale these separate services gets expensive and drives the cost per unit up to a point where it is not financially viable.