#emqx — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #emqx, aggregated by home.social.
-
hmm, does mosquitto not support bridge mode with MQTTv5?
Trying to bridge from EMQX to mosquitto 2.1.2 with MQTTv5 and bridge mode enabled and it fails with "protocol error"
Turn the protocol down to v3.1.1 and it woks
-
hmm, does mosquitto not support bridge mode with MQTTv5?
Trying to bridge from EMQX to mosquitto 2.1.2 with MQTTv5 and bridge mode enabled and it fails with "protocol error"
Turn the protocol down to v3.1.1 and it woks
-
Der neue MQTT-Broker hat schon interessante Statistiken.
Ich hatte vorher schon bemerkt, dass der Luftsensor von Tuya viel zu oft reported und damit das WLAN vollstopft. Deshalb habe ich den per Steckdose erst Abends vorm Schlafengehen eingeschaltet (steht im Schlafzimmer) und nach zwei Stunden wieder ausgeschaltet.
Jetzt kann ichs auch im Log sehen
-
Der neue MQTT-Broker hat schon interessante Statistiken.
Ich hatte vorher schon bemerkt, dass der Luftsensor von Tuya viel zu oft reported und damit das WLAN vollstopft. Deshalb habe ich den per Steckdose erst Abends vorm Schlafengehen eingeschaltet (steht im Schlafzimmer) und nach zwei Stunden wieder ausgeschaltet.
Jetzt kann ichs auch im Log sehen
-
ClickHouse в мире IoT
В этой статье мы рассмотрим использование ClickHouse для хранения данных, поступающих по протоколу MQTT. Данный протокол был специально разработан для приложений IoT и предназначен для обеспечения эффективной и надежной связи между устройствами. В MQTT используется облегченная модель публикации‑подписки, обеспечивающая бесперебойную передачу данных даже в условиях ограниченных ресурсов. Низкие накладные расходы и поддержка потоковой передачи данных в реальном времени делают протокол MQTT идеальным выбором для сбора и передачи данных IoT с различных конечных устройств на платформы обработки данных.
-
Bizarre, I'm running into issues where Frigate fails to connect to EMQX's MQTT and EMQX logs user_not_found, even though the user clearly exists in the #EMQX web interface. Whyy. I've already tried accounting for case by creating a lowercase version, but alas still doesn't work.
-
Bizarre, I'm running into issues where Frigate fails to connect to EMQX's MQTT and EMQX logs user_not_found, even though the user clearly exists in the #EMQX web interface. Whyy. I've already tried accounting for case by creating a lowercase version, but alas still doesn't work.
-
Gestern mal #EMQX angeschaut. Ist letztendlich ein MQTT Broker mit einer grafischen Oberfläche.
Wer Docker auf einem Linux-Server betreibt hat es in wenigen Sekunden installiert.
Gefällt mir bisher ganz gut.
https://www.emqx.com/en -
I'm trying to setup #Zigbee2MQTT with #EMQX on HomeAssistant, whew this thing is tricky to get working.
Auth User is setup in EMQX, but Z2M still says ECONNREFUSED.
-
I'm trying to setup #Zigbee2MQTT with #EMQX on HomeAssistant, whew this thing is tricky to get working.
Auth User is setup in EMQX, but Z2M still says ECONNREFUSED.
-
Today's #homeautomation adventure is moving from "it should just work" #mosquitto to "whoa slick dashboards" #emqx. (Mosquitto just works....kinda. Mostly. Damned hard to debug.)
Unfortunately EMQX is #optout #telemetry. So here is the cheat code:
In the container environment block, or under 'emqxConfig:' in the helm values, just set: `EMQX_TELEMETRY__ENABLE: "false"`
The false needs quotes to keep it text, not boolean. (And it may be = instead of : depending on how you are running EMQX.) The double-underscore is intentional. -
Today's #homeautomation adventure is moving from "it should just work" #mosquitto to "whoa slick dashboards" #emqx. (Mosquitto just works....kinda. Mostly. Damned hard to debug.)
Unfortunately EMQX is #optout #telemetry. So here is the cheat code:
In the container environment block, or under 'emqxConfig:' in the helm values, just set: `EMQX_TELEMETRY__ENABLE: "false"`
The false needs quotes to keep it text, not boolean. (And it may be = instead of : depending on how you are running EMQX.) The double-underscore is intentional. -
Took another try at #EMQX to handle my mqtt traffic. 5.x looks a lot more polished than 4.x did, and works amazingly well in #Kubernetes. I know #HomeAssistant now has it as an add-on which is nice as well.
It handles certs SO much better than 4.x did (I had to hack it a bit before within the pv where the database lived).
Now if I could figure out how to integrate the users from #Authentik, I'd be a happy girl. 4.x supported LDAP, but was a bit painful