-
Aktuell bin ich immer noch auf der Version 0.8.79 weil in den Versionen 0.8.8x mir bei der Überprüfung mit dem MQTT Explorer Topics fehlen. So. z.B. im ch0 ALARM_MES_ID:
![grafik](https://github.com/…
-
I can connect to my MQTT brocker, but the list of topics remain empty.
I tried all protocol settings and with or without a Topic filter.
I tried with my own data / clients and with the provided …
-
Thank you for creating and maintaining zwave-js-ui. I am currently migration my zwave network and I am using MQTT.
For topic type I use `ValueID topics`, Payload type is `Just value` and I disabled `…
-
### Observed behavior
We've observed frequent RAFT leadership transfers of the $MQTT_PUBREL consumers and health check failures, even in a steady state. Occasionally, these issues escalate, causi…
-
### Is your feature request related to a problem? Please describe
I have set up a zigbee2mqtt node and would like to be able to configure topics that end with a device id. This is impossible, as zi…
-
i want to have 2 source connectors reading from the same mqtt topic and writing to 2 different kafka topics. why i need this? because i am using a different partitioning key
is it possible to a add…
-
Hi,
thanks for your firmware.
After some problems with connecting to my door sensor (your connection plus connection EN to VCC, internal memory 2MB and not 1MB) I could flash your firmware and rea…
-
Found that MQTT sends the information about FW* HW* in ch0 only once after reboot the device.
This can be checked very easy.
Start MQTT Explorer. Wait a few minutes. ch0 will show 12 to 13 topics.…
-
**Overview:**
This pull request introduces a new feature to the Publisher class, allowing it to publish individual key-value pairs from a JSON object to separate MQTT topics. The original functionali…
-
After migrating my mqtt broker to docker, the nuki hub is recognized by hass but not the opener. The nuki topic contains all the information though, but I only see items for the hub in the homeassista…