MQTT question

Built-In Apps and Drivers
1

I'm using the integrated (in beta) MQTT instance to importdevices into hubitat.
This seems to work, but for one device not so much.

This week I got a new powerwaal from Jackery.
Seeing it has an integrated MQTT push functionality (primarely for HA) I wanted to connect it to Hubitat to be able to read the battery state and the current load.

So I entered the Hubitat MQTT adress and credentials in the Jackery, but it shows up strange in Hubitat.

image
image473×759 17.7 KB

The device is under "hb", but only "event" is seen.
Looking at the dev pages, it shoud have more topics (see GitHub - Jackery-Official/jackery · GitHub )

Is this perhaps because in the builtin MQTT server there is no way to authenticate the connection with a generated token?

2

The only usable topic you have, for now, is event. Do you have MQTT Explorer?

3

I agree with @nckepa MQTT Explorer is really the best too to see what is going on with the topics. I use it all the time for my weather observations and I am currently testing the MQTT function to allow Meshtastic LoRa messages to be sent to my Hub.

4

MQTT explorer shows more data, but still not enough.

{

  "type": 23,

"eventId": 0,

"messageId": 0,

"ts": 1788024255,

"deviceType": 3,

"body": {

"deviceSn": "HQ2C09000487HP3",

"devType": 1,

"subType": 0,

"outEgy": 238,

"inEgy": 281

}

}

Looks like it needs the token reported back, else it will not give all data and setpoints.

5

Hopefully we will get more MQTT support in the future. Its hard to assign multiple attributes in an ideal way.

6

There is always seems to be some type of blocking condition, some products want login credentials for MQTT others you have to provide a key. Yes very frustrating. i have been lucky with the topics I am working with both are local, and the ones from the internet I proxy with some code I wrote python and I let the Mosquito MQTT handle the client connection and I republish internally. One shouldn't have to jump though so many hoops.