Greg C
USA
Asked
— Edited
Resolved by ptp!
i am trying to use the MQTT plugin with no luck. I have a host on 192.168.2.8 and so far am just hitting the connect button but its timing out with
'uPLibrary.Networking.M2Mqtt.Exceptions.MqttCommunicationException' was thrown.
Then high cpu use and a task kill to get back full operation? This is on a Tiny, if I can get this working I plan on getting a /4 also and a SSC32 to help split the power.
I am 3/4 thru an Inmoov build and want/need MQTT for openhab connection.
Thanks all
What plugin are you using? The MQTT Broker or MQTT Client? Did you configure the IP Address in the client? Does the broker require authentication?
Here is the MQTT Client plugin: https://synthiam.com/redirect/legacy?table=plugin&id=170
Here is the MQTT Broker plugin: https://synthiam.com/redirect/legacy?table=plugin&id=169
Which one are you using?
The SSC-32 is a servo controller, and can be controlled using the SSC-32 control. You can find out more about the SSC-32 by pressing the ? (question mark) on the control and viewing the manual page, or view it here: http://www.ez-robot.com/Tutorials/Help.aspx?id=216
The SSC-32 does not directly communicate with MQTT. Can you provide more information about what you're goal is? It'll be easy to setup once we know
However, we'll need more information about your setup. What do you mean by "host"? i.e. what broker is it? What are you subscribing to? Is it a broker?
It is a broker at 192.168.2.8:1883 and has been running for a few years.
What plugin are you using? The MQTT Broker or MQTT Client? Did you configure the IP Address in the client? Does the broker require authentication?
Trying the client and IP is in the config.
No authentication on the broker. And there is a RFM69 arduino radio network sending hundreds of msgs thru it.
The SSC-32 does not directly communicate with MQTT. Can you provide more information about what you're goal is? It'll be easy to setup once we know Grin
Thank you
2 days and this
https://www.youtube.com/watch?v=ObOEqBUFkkY
1) What broker software & version ?
2 )operating system you use on the host ?
mosquitto Version .15
Running on a PI 2 with Raspbian wheezy
Version 0.15 is very old:
although is not a big issue (at least for home users) there are some security issues:
I tried the mqqt client plugin with my mosquito server (1.4.12) and no connection issues.
try to connect and check your server's log:
Code:
next step check ARC windows's firewall and connectivity to the mosquitto port.
last effort: update the mosquitto version.
Looks like the EZ computer can reach the MQTT server
PS C:\Users\greg> Test-NetConnection 192.168.2.8 -port 1883
ComputerName : 192.168.2.8
RemoteAddress : 192.168.2.8
RemotePort : 1883
InterfaceAlias : Wi-Fi
SourceAddress : 192.168.2.54
TcpTestSucceeded : True
And I looked in/var/log/mosquitto/mosquitto.log
but no file there, might be the older version I have. Looking at the log I installed it on 8-15. Looks like I am not one to upgrade when it's working. So I might need to upgrade, but I am getting this so more work to do.
sudo apt-get install mosquitto
Reading package lists... Done
Building dependency tree
Reading state information... Done
mosquitto is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
After some work I get this after a upgrade
pi@raspberrypi ~ $ mosquitto
1497739370: mosquitto version 0.15 (build date 2017-05-29 22:37:10+0000) starting
1497739370: Opening ipv4 listen socket on port 1883.
1497739370: Error: Address already in use
This version does does not match the build date? I might add the latest windows MQTT clients connect with no trouble.
you need to do:
Code:
apt-get update downloads the package lists from the repositories and "updates" them to get information on the newest versions of packages and their dependencies. This command does not install or upgrade any packages.
Code:
installs newer versions of the packages you have. After updating the lists, the package manager knows about available updates for the software you have installed. This is why you first want to do apt-get update.
Thanks