zigbee2mqtt
NATS
Our great sponsors
zigbee2mqtt | NATS | |
---|---|---|
125 | 106 | |
11,087 | 14,766 | |
- | 2.4% | |
9.8 | 9.8 | |
4 days ago | about 16 hours ago | |
JavaScript | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zigbee2mqtt
-
A Custom Zigbee Doorbell
Have you considered Zigbee2mqtt[0]? You'd be running an extra program, but the docs are really good, it's pretty lightweight, and MQTT is incredibly easy to talk to from python or basically anything else.
[0] - https://www.zigbee2mqtt.io/
-
Thoughts, learnings and regrets after three years on Home Assistant
For Zigbee, I can recommend using the Zigbee2MQTT (https://www.zigbee2mqtt.io/) integration instead of HomeAssistant's built-in ZHA system. It might be a bit more complex to set up, but it's very powerful and works fantastically. (User "simon42" on YouTube has some good videos about the topic, but they're in German.)
-
Bad business broke the smart home
This is definitely better than many of the alternatives but still not perfect. With Zigbee etc you end up locked into one or more of the ecosystems, not to mention some manufacturers implementing it in a way that has weird quirks (see [1]). With esphome you have a limited choice of devices (would love to see more), but you also usually end up locked into keeping a 2.4GHz WPA2 AP for your devices (and you miss out on mesh, but also the problems when it doesn't work...)
1: https://github.com/Koenkk/zigbee2mqtt/issues/16717
- The Philips Hue ecosystem is collapsing into stupidity
-
Philips Hue will soon force users to create an account
I can recommend this: https://www.zigbee2mqtt.io/
You can keep your Hue bulbs and devices but threw away the app, hub, and need to work with hue as an institution at all.
I got a $30 USB zigbee stick to replace the hub. works great!
-
Any one know how to connect sonoff s31 to a mqtt server on 8883 (tls)
It looks like it uses zigbee? If you have a server you could run zigbee2mqtt. You'd also need a zigbee dongle / adapter.
- How I wrote my own Smart Home software
-
Troubleshooting a troublesome trinket that's terribly torpid!
\also posted on the z2m* github device discussion board
-
Raspberry pi & a Sonoff USB dongle
If you want to use HA on your phone, you would need to install it on the pi, along with either ZHA or Zigbee2MQTT for the Zigbee network interface. Debian alone won't be able to interface with most of your smart devices.
-
New installation: setup everything in the lab or after the installation?
I still haven't understood if the devices will change the path using the better route or not (since I've just tested a bTicino switch K4003C and it keeps using the worst path with 1 or 0 signal quality over a near Ikea repeater with a signal quality of 50).
NATS
-
Implementing OTel Trace Context Propagation Through Message Brokers with Go
Several message brokers, such as NATS and database queues, are not supported by OpenTelemetry (OTel) SDKs. This article will guide you on how to use context propagation explicitly with these message queues.
-
NATS: First Impressions
https://nats.io/ (Tracker removed)
> Connective Technology for Adaptive Edge & Distributed Systems
> An Introduction to NATS - The first screencast
I guess I don't need to know what it is
-
Interview with Sebastian Holstein, Founder of Qaze
During our interview, we referred to NATS quite a few times! If you want to learn more about it, Sebastian suggests this tutorial series.
-
Sequential and parallel execution of long-running shell commands
Pueue dumps the state of the queue to the disk as JSON every time the state changes, so when you have a lot of queued jobs this results in considerable disk io. I actually changed it to compress the state file via zstd which helped quite a bit but then eventually just moved on to running NATS [1] locally.
[1] https://nats.io/
-
Revolutionizing Real-Time Alerts with AI, NATs and Streamlit
Imagine you have an AI-powered personal alerting chat assistant that interacts using up-to-date data. Whether it's a big move in the stock market that affects your investments, any significant change on your shared SharePoint documents, or discounts on Amazon you were waiting for, the application is designed to keep you informed and alert you about any significant changes based on the criteria you set in advance using your natural language. In this post, we will learn how to build a full-stack event-driven weather alert chat application in Python using pretty cool tools: Streamlit, NATS, and OpenAI. The app can collect real-time weather information, understand your criteria for alerts using AI, and deliver these alerts to the user interface.
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
Why wasn't NATS[1] used ?
Written in Go, single-binary deployment... there's a lot to love about NATS !
[1]https://nats.io/
-
Scripting with NATS.io support
require nats.io
-
Introducing “Database Performance at Scale”: A Free, Open Source Book
About cost, see [1]. Also, S3 prices have been increasing and there's been a bunch of alternative offers for object store from other companies. I think people in here (HN) comment often about increasing costs of AWS offerings.
Distributed systems and consensus are inherently hard problem, but there are a lot of implementations that you can study (like Etcd that you mention, or NATS [2], which I've been playing with and looks super cool so far :-p) if you want to understand the internals, on top of many books and papers released.
Again, I never said it was "easy" to build distributed systems, I just don't think there's any esoteric knowledge to what S3 provides.
--
1: https://en.wikipedia.org/wiki/Economies_of_scale
2: https://nats.io/
- NATS: Connective Technology for Adaptive Edge and Distributed Systems
-
Is it an antipattern to use the response channel as identifier
I am in a project were nats.io is used. Someone thought, it would be a great idea to link data in an event with data in a response using the response channel name.
What are some alternatives?
Tasmota - Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
mosquitto - Eclipse Mosquitto - An open source MQTT broker
celery - Distributed Task Queue (development branch)
Z-Stack-firmware - Compilation instructions and hex files for Z-Stack firmwares
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
Node RED - Low-code programming for event-driven applications
Apache ActiveMQ - Mirror of Apache ActiveMQ
homebridge - HomeKit support for the impatient.
nsq - A realtime distributed messaging platform