|
|
|
|
|
|
|
|
|
Re: MQTT Implementation in 4diac [message #1806489 is a reply to message #1806483] |
Thu, 09 May 2019 18:52 |
|
0.0.0.0 is not a valid ip address. You need the ip address from which your broker is reachable from your raspberry pi. On windows machines you can find that by typing ipconfig /all in a console and look for the correct interface. Also both have to be in the same network and reachable from each other. But I assume that you have that as you are able to download from your laptop to your raspberry pi.
|
|
|
|
Re: MQTT Implementation in 4diac [message #1806871 is a reply to message #1806831] |
Thu, 16 May 2019 18:34 |
|
Hi Greg,
as we did solve some issues in the MQTT code my default answer would be: try to upgrade 4diac FORTE to 1.10.2. You can even use 4diac IDE 1.8.4 ( but here I would even more recommend an upgrade soon, because here we changed so much under and over the hood. Especially the stability of 4diac IDE >1.9.2 is a reason).
The client ID is just an identifier used by the mqtt library for identifying your FORTE instance to the broker. You can set it to any value as long as it is equal across all FBs in your 4dica FORTE. Maybe we should rework that and handle it under the hood.
Also please note that 4diac FORTE is currently only connectable to one broker.
One thing is that you need to enable normal tcp access enable on your broker or build paho with openssh and adapt your protocol. However I haven't tested that yet.
Alois
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06287 seconds