I’m using mosquitto broker (6.4) and added two bridge connections to my .conf file
when using mqtt explorer every topic is exposed, from ha, my solar assistant and my extra addition homey pro.
when configuring Mqtt client in ha, i get a message saying one device is found!?
and i should choose an area. This device is a solar growatt sph device, but this is the only device discovered
When listening to a topic from the client, i can receive correct values from all topics, from all 3 brokers.
first message is from the ONLY device found by the client, the next is a samlpe from my broker
This have been working before, but when installing new Homey Pro and solar assistant, i must have messed up somehow. Client only list a single device , but can find ALL topics when listening, reinstalled and restarted many times now, is there a way to make sure the client stats from scratch after a reinstall, because to me it looks like this sigle device has been hardcoded into the client ;-(
Message 1 received on homeassistant/sensor/inverter_1_grid_frequency/config at 2:01 PM:
{“device”:{“ids”:[“solar_ha”],“mdl”:“Growatt SPH”,“mf”:“Growatt”,“name”:“Growatt SPH”},“name”:“Grid frequency”,“state_class”:“measurement”,“state_topic”:“solar_assistant/inverter_1/grid_frequency/state”,“uniq_id”:“solar_ha_inverter_1_grid_frequency”,“unit_of_measurement”:“Hz”}
QoS: 0 - Retain: true
Message 0 received on homey2023/go-e-knappen/$type at 1:59 PM:
socket
QoS: 0 - Retain: true
Also ALL topics from all brokers can be browsed from MQTT explorer, while only connecting to Mosquitto broker on my HA
OK so the first question is, why do you need bridges?
The normal way to use MQTT is to have a single server and point anything that needs to use MQTT to the same single server.
because Solar assistant can only use itself as a broker, at first i started with this is as my only Broker (like you suggest), at some point i couldn’t get my ha client to update/show new topics, and from there on the trouble started, when using Solar assistant as broker for all 3, i still only get the same single device in my ha mqtt client, sorry i should have mentioned this also.
I haven’t tried using Homey Pro as my Broker yet, but expect to get the same result, also Homey Pro cannot be configured to bridge
OK we need to see some other topics that are published then, not from solar assistant because that is clearly working, we need to see topics of the devices that SHOULD be appearing in Home Assistant, but are not.
this is from my Homey Pro broker hub:
Message 0 received on homey2023/go-e-knappen/$type at 1:59 PM:
socket
QoS: 0 - Retain: true
This also from Homey Pro:
homey2023/alarm-tilstand/alarm-heimdall/$name
QoS
0
Message 0 received on homey2023/alarm-tilstand/alarm-heimdall/$name at 3:14 PM:
Alarm tilstand - Alarmtilstand
QoS: 0 - Retain: true
Yeah I saw that one, but any topics that have a $ in the topic, are internally used for MQTT - they don’t have any use in Home Assistant or any MQTT Client, they are typically for server itself.
The suggestion is that Homey needs both a server app, which presumably is what you have installed on it. But also a client app - which you connect to Home Assistant’s MQTT rather than Homeys ?
I have tried both options now (own broker and therefore bridge configured) and also Homey client conneting to Mosquitto broker on HA, no matter what, i can only see one device in MQTT client on HA, and from the same HA client i can listen to all topics publblished. That’s why i suspect the client is “broken” and cant list all devices somehow
Latest from Homey to MQTT client via Mosquitto broker on HA:
Message 12 received on homey2023/zigbee-nous-router-bryggers/meter-power at 3:26 PM:
0
QoS: 0 - Retain: true
since my last reconfig (Broker only running on Solar) devices from Homey Pro are slowly popping up inMQTT client in HA, now 12 devices in 30 minutes, still lacking devices from Solar assistant, i will wait to see if they will appear
