#Where do i find my mqtt host ip.

1 messages · Page 1 of 1 (latest)

next lion
#

My system crashed. I had no backup and have to start over. Trying to get my cameras back into HAOS. The mqtt host was previously 10.0.0.20. But now I only see 127.0.0.1. Where do I find my host ip. Tried using the HA ip but that doesn't work.
I have 2 wyze cams that are connected through wyze docker bridge. Then 1 eufy cam with eufy security addon and integration. No ip's I try work.
I had a copy of my frigate config. All i did was copy and paste it into the config. But I can't figure out the ip addresses.
I have
mqtt:
host: 127.0.0.1 (from webrtc integration)
user: mqtt
password: xxxxxxxx

I've tried the ip's from the wyze bridge addon, local ip, eufy security. Actual device ip's from router. Nothing works.

serene star
#

now I only see 127.0.0.1.
Where?
What broker do you use? Is it even running?

next lion
#

Mosquitto broker.

#

I see the 127.0.0.1 is in the eufy security integration

#

How do I see if it's running?

#

The addon says it's running but 0% cpu usage and 0.5% ram usage.

serene star
#

Which addon?

#

Ah. It should tell you a hostname on the addon page. Try to use that.

#

And check the addon logs.

next lion
#

Host name says core-mosquitto

#

The addon was rhe mosquitto broker addon

serene star
#

Then use that. The HA ip should also work if the addon is properly configured and running. Like I said, check its logs.
Also try to manually set a port in the config.

next lion
#

I can't tell anything from the logs.
There is 1 ip it is connecting from and that starts with 172.30.xx.x

serene star
#

Then share them.

next lion
#

Here is a snippet.

2024-10-27 10:56:57: New connection from 172.30.33.3:44081 on port 1883.
2024-10-27 10:56:57: New client connected from 172.30.33.3:44081 as auto-472FD216-EB97-6207-5A25-F9241B74AC2E (p2, c1, k60, u'addons').
2024-10-27 10:56:57: Client auto-472FD216-EB97-6207-5A25-F9241B74AC2E disconnected.
2024-10-27 10:56:58: New connection from 172.30.33.3:40729 on port 1883.
2024-10-27 10:56:58: New client connected from 172.30.33.3:40729 as auto-E5AF83E4-14FE-9A27-2319-C6D1209F0429 (p2, c1, k60, u'addons').
2024-10-27 10:56:58: Client auto-E5AF83E4-14FE-9A27-2319-C6D1209F0429 disconnected.
2024-10-27 10:57:07: New connection from 172.30.33.3:57095 on port 1883.
2024-10-27 10:57:07: New client connected from 172.30.33.3:57095 as auto-AAEB28C5-7D2E-918B-3E3D-13BCCCF87ACA (p2, c1, k60, u'addons').
2024-10-27 10:57:07: Client auto-AAEB28C5-7D2E-918B-3E3D-13BCCCF87ACA disconnected.
2024-10-27 10:57:07: New connection from 172.30.33.3:39415 on port 1883. 
#

From the mosquitto broker logs.

serene star
#

That's fine.

#

Can you try if you can connect via MQTT Explorer through the HA ip?

next lion
#

What is mqtt explorer

serene star
#

Mark the text, right click and search with google :>

lyric sapphire
#

ping your home assistant and you have the internal ip, plus the port 1883

#

ping homeassistant.local -4 is the command

#

ping will give you an answer which includes the ip

verbal heartBOT
#

Open your Home Assistant instance and manage your systems network configuration

serene star
#

Or check here.

next lion
#

Mqtt is running. I see a bunch of reports in the explorer.

#

So the ip from the ping is the host ip then?

lyric sapphire
#

yes

next lion
#

Why is the local ip from the integration different from what i get from the ping?

serene star
#

Which local ip? 127.0.0.1?

next lion
#

The 127.0.0.1 is from the eufy security addon.
The ip for home assistant on my router and the local ip integration are the same. 192.168.xx.xx
But the ping is the 172.30.xx.x

serene star
#

Both 127.0.0.1 and 172.x are only valid on the system itself. 192.168.x is the "real" ip accessible on your LAN.
127.0.0.1 is the true localhost and you almost never want to use it: https://en.wikipedia.org/wiki/Localhost
172.x is the docker ip. All addons and HA itself are containers which have such an ip. core-mosquitto should resolve to that for example.
You see it's a bit complicated and what to use depends what needs to access what and what it listens to.

next lion
#

The eufy integration says 127.0.0.1 is the host ip for go2rtc addon. Are you saying don't use that one

serene star
#

Likely not.

next lion
#

Still can't get my cameras working again. When setting up the eufy integration I'm asked for the host ip and port for eufy security web socket instance. Where do I find that.

serene star
#

Not familiar with that software. Likely the ip/hostname of the addon it uses.

next lion
#

Ugh. This is getting aggravating. Nothing i try works.

next lion
#

I got my eufy camera working in Frigate. Still can't get my wyze cameras, using docker wyze bridge.
I think it is the ip for the mqtt host. My last setup had 10.0.0.9 as the mqtt ip and I used it with cameras name in the config and it worked. Now it wont work. My local ip is 172.30.xx.1, but when I ping the home assistant in terminal it shows 172.30.xx.2. Where can I find what goes under host?

mqtt:
  host: ???.???.??.??
  user: xxxx
  password:  xxxxxxxxx
#

It shows the camera (front-porch) in the mqtt explorer