Forum Replies Created
-
AuthorPosts
-
Mr_FlibbleParticipantOk, I found the problem. Obvious really, but so is any problem like this until you know the answer.
I installed Mosquito MQTT on Home Assistant through the GUI add-on tool, set it up, and set up most of my MQTT devices, and they all worked just fine.
When I tried to connect the Open Garage Units (I have 3 of them) they all started having the issues described above.
The MQTT log showed multiple entries of:
New connection from 192.168.1.161 on port 1883.
Socket error on client <unknown>, disconnecting.
New connection from 192.168.1.161 on port 1883.
Socket error on client <unknown>, disconnecting.
New connection from 192.168.1.161 on port 1883.
Socket error on client <unknown>, disconnecting.Not really obvious what was going wrong.
I thought first it was the way Home Assistant handled the looping from some github posts. But wasn’t it at all.
How I solved it:
I intentionally gave one of my Open Garage devices the wrong IP address for MQTT. It continued to operate normally, and Home Assistant could see it. There was no slowdown in the web interface.
Looking more closely at the MQTT side of the house I found the problem:
}
],
“anonymous”: false,
“customize”: {
“active”: false,
“folder”: “mosquitto”
},As soon as I realized that the default behaviour of Mosquito is “anonymous”: false I realized my mistake.
Setting “anonymous”: true, fixed the issue immediately.
Obvious in hindsight, but I am posting all the gory details here in case someone else with Open Garage and Home Assistant runs into the same problem, then they can google for my idiocy and fix their issue.
Mr_FlibbleParticipantGot onto the Dev branch, and got v. 1.1.1; but it has exactly the same issues as the other versions.
As soon as I define an MQTT Server IP, the system implodes.
If the screenshots I took upload properly, you can see where I am preparing to save the MQTT server target (am I missing the port? Is that required? I need better docs on this)
The next two screenshots show how the interface begins to freeze as the system goes off the rails (I am going to have to go back out to the garage now and hard-reset it).
Attachments:
You must be logged in to view attached files.
Mr_FlibbleParticipantI just tested 1.1.0
It suffers the same issues as 1.0.9
When I define an MQTT server, the polling stops functioning correctly. However, this time the interface was stable enough for me to reset the IP of the MQTT server to the following:
-.-.-.-
Doing this, the system recovers and works in Home Assistant with Polling again.I don’t know where I can locate higher firmware versions than 1.1.0
Mr_FlibbleParticipantI am having some unusual behavior with MQTT and OpenGarage. I am using home assistant, and it works fine. Currently, I am using the OpenGarage component where it polls every 10 seconds, which is less than ideal.
When I add the IP for my MQTT server, OpenGarage goes “crazy”.
What I mean by crazy, is that the web polling portion ceases to function, and my ability to control it through home assistant vanishes, and it appears offline. Furthermore it forgets all of its settings, and comes back “blank”. It then functions intermittently until I hard reset it and go through the adoption process again.
I would assume this is a one off, but I have 3 of these devices, and I have a large number of devices using MQTT today without issue.
Currently, this is on firmware 1.0.9, so my next step is upgrading.
Has anyone got MQTT working with these and the Home Assistant control portion? (Works just fine as long as I don’t try to enable MQTT)
-
AuthorPosts