MQTT with Retained Flag no Data update

tom_l · April 11, 2024, 11:33am

Many people use HiveMQ and other brokers without issue. It is more likely an issue with CCU Jack.I see you have opened an issue:

github.com/mdzio/ccu-jack

Homeassistant Topics werden nicht aktualisiert

opened 10:13AM - 11 Apr 24 UTC

slg60

Versuche den CCU Jack auf meiner Raspimatic auch für Homeassistant zu nutzen. M…it der in HA bereitgestellten MQTT Integration funktioniert das auch soweit. Die Daten werden von einer AHOY DTU zur Verfügung gestellt. Es gibt Daten die werden in HA aktualisiert, es gibt aber welche, wie z.B Yield/Total werte, die werden nur nach einem Neustart ein mal in HA aktualisiert oder wenn man das Topic manuell über die Integration abonniert. Auch hier werden die Daten nur ein einziges mal zur Verfügung gestellt. Andere Broker scheinen in HA da keine Probleme zu haben. Kann sich das jemand erklären? Das Problem scheint es wohl öfter schon gegeben haben. Die Betroffenen sind dann meist auf einen anderen Broker gewechselt und die Probleme waren weg. Ich würde den Jack aber gerne als einzigen Broker behalten. Jemand eine Idee?

slg60 · April 11, 2024, 11:40am

Maybe, but what is against this assumption is the fact that wit MQTT Explorer everything works, so when the MQTT Integration would work like MQTT Explorer, I would have no issue…

Tryed to use the workaround with the Mosquitto Bridge… When I’ve prepared everything properly then there really seems to be something wrong with the protocol…

mosquitto version 2.0.18 running
2024-04-11 15:54:33: Connection Refused: unacceptable protocol version
2024-04-11 15:54:33: Client local.core-mosquitto.bridge-01 closed its connection.
2024-04-11 15:54:33: New connection from 127.0.0.1:48084 on port 1883.
2024-04-11 15:54:33: Client <unknown> disconnected due to protocol error.

tom_l · April 11, 2024, 11:44am

It’s either HA not subscribing the CCU Jack topics correctly (unlikely as it works for other brokers), or CCU Jack not publishing to the subscribed HA client correctly when a subscribed topic receives a new message. Unlikely to be an authentication issue as it is publishing retained messages to HA when it connects.

Anything in the HA or CCU Jack logs that can shed light on this?

code-in-progress · April 11, 2024, 11:52am

I use EMQx and have no issues with retained flags in HA. My guess is that since CCU Jack uses Go as it’s language, it’s doing something that may not be part of the standard 3.1.1 spec when it comes to the retain flag. I couldn’t find anything in the source code that highlighted the broker it uses (but it looks like it’s a Go version of MQTT).

That’s like comparing apples to oranges. MQTT Explorer and HA use completely different libraries to access MQTT brokers and may have differences in how they both handle the retain flag. I know that HA made changes last year(?) to how it handles the retain flag that I think might have been different than the 3.1.1 spec allows for (for 5.x broker support).

slg60 · April 12, 2024, 6:20am

I have a Solution now. I’m using the Mosquitto Broker in HA and the CCU Jack is working as a Bridge. I can live with that, but really curious why the Jack Broker is not working in HA. Placed an issue on CCU-Jack Project.