fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

#EMQX

0 posts0 participants0 posts today

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 с различных конечных устройств на платформы обработки данных.

habr.com/ru/companies/otus/art

ХабрClickHouse в мире IoTРазработанная Яндексом СУБД ClickHouse — одно из самых распространенных решений для аналитической обработки в режиме онлайн, позволяющее обрабатывать и анализировать большие объемы...

This was gonna be more eloquent before a neighbor/cop in uniform did his cop knock on my front door and hit the doorbell twice. To ask if my car was for sale. Like, essentially asking a favor.. Seriously? WHAM WHAM WHAM. No. It wasn't for sale before and it is even less for sale now. Go away. (He's mad at my custom Harris sign that calls his union's favorite spoiler candidate a jackass.)
Ahem. Anyway. Yesterday I finally got around to yanking
#emqx out and putting #mosquitto back in. Grafana does fine, I don't miss the dashboards much.
Today I made it eavesdrop on my
#Bambulab #P1S so that I could do automating without all the limitations of the onboard #MQTT.
If you're curious, it is pretty simple. Just don't write or subscribe anywhere it doesn't expect or it will kick you out. (Fill in your PIN and serial number, and you can fetch bridge_cafile from the printer with openssl.)

remote_username bblp
remote_password 1234654
bridge_cafile /mosquitto/panda/blcert.pem
bridge_insecure true
notifications_local_only true
try_private false
bridge_protocol_version mqttv311
topic device/01Pdfdfdfdffdfd/report in
topic device/01Pdfdfdfdffdfd/request out

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.

Today's fake #opensource shame goes to #EMQX. The version 5.8.0 release notes start out awesome, lots of good stuff. And a minor release, so how bad could it be? Unfortunately, if you click 'read more' you will find the "breaking changes" section carefully hidden below the fold. It gets very dark very fast.
It turns out this release is mostly about
adding paywalls to a major clustering features, and trashing most of the useful monitoring and ops related dashboard pages. (As a bonus, that PR fixes a private bug in a private Jira.)

I guess it is time to go back to Mosquitto. It may be a pain to monitor, but I don't have to get legal counsel to read the release notes before upgrading.

#snarkhome #mqtt #emqx #mosquitto #homeautomation #paywall #enshittfication

GitHubReleases · emqx/emqxThe most scalable open-source MQTT broker for IoT, IIoT, and connected vehicles - emqx/emqx

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