The Lounge
Home Assistant
Our great sponsors
The Lounge | Home Assistant | |
---|---|---|
61 | 1,410 | |
5,391 | 68,378 | |
0.9% | 1.3% | |
8.3 | 10.0 | |
about 12 hours ago | 4 days ago | |
TypeScript | Python | |
MIT License | 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.
The Lounge
-
Simplicity of IRC
IRC as a protocol is indeed incredibly simple and easy to get started with. Years ago did discover this when I was able to make [this atrocity](https://github.com/creesch/discordIRCd) bridging IRC and discord where for IRC I effectively did a simple server implementation.
There is a caveat, though. Like many older protocols (ftp) there is a lot that was not initially written down or left up to clients and server implementations. This, does lead to a lot of edge cases you need to be aware of once you want to actually support a wider user group.
Also, as this is apparently is still a discussion. IRC is not simple from a modern user UX perception. Registration can be complex and confusing, though hidden a bit through clients. Managing channels with various flags is a whole other thing. Then there is also the fact that these days people are no longer used to the fact that they can't see messages from periods where they were not connected. Of course, the latter can be easily handled by a BNC or fancy clients like https://thelounge.chat . But, that is only easy for technically inclined folks.
-
Posthog is closing their Slack community in favor of forum
> It’s 2024, people aren’t going to go out of their way to setup “bouncers” to keep up with conversation that happens when they’re not online or leave their computer running 24/7.
You can just set up something like The Lounge [0].
-
Show HN: GodotOS: A Fake Operating System Interface Made in the Godot Engine
Excellent idea! You'll have a mature, open standard protocol under the hood, with no vendor lock-in, excellent extensibility, and great modern frontends like The Lounge (https://thelounge.chat/) or Convos (https://convos.chat/) to choose from (and you can choose).
-
IRC Is the Only Viable Chat Protocol
> But all of the modern services like Teams, Slack and Discord, have seamlessness between client devices as their first priority.
Can't speak for the others, but Teams is really hit-or-miss. Missed notifications, missed messages, out of order messages. Then it appears to be fixed for three months only to happen again. It mostly seems to happen on Android.
In general, you're right, multi-device appeared to have been solved for IM - at least MSN messenger and Skype had it - right around the time when the smart phone came around, but then we had the same problem again in the mobile world, because somehow those messengers couldn't successfully move to phones: WhatsApp and the likes was bound to one device again. They added web access later, but that was more of a hack than true multi-device support.
The big problem the phone messaging apps solved was that their protocols didn't require a persistent connection. Theoretically, all the other protocols, MSN, ICQ, Skype, IRC could have been extended to support this too, but it's always faster to just build something new and be first to market.
If you want to use IRC today and have that modern multi-device experience, IMO the most decent solution is Quassel[1] (and Quasseldroid for Android). It's like a bouncer, but uses a custom protocol between the bouncer (quassel-core) and the GUI (quassel-client), so that it can perfectly sync state across all devices, and with flaky connections on mobile. It obviously required you to run the core on some server so it's accessible from everywhere, so nothing for "normies" as TFA calls them, but to me it's what makes IRC usable in the modern world. I wouldn't want to use irssi in a screen via ssh in termux on my phone.
The next best thing, if you're a Web 2.0 aficionado is probably The Lounge[2].
- Show HN: Halloy – A GUI Application in Rust for IRC
-
Matrix 2.0: How we’re making Matrix go voom
For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.
Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.
[1] - https://github.com/thelounge
[2] - https://thelounge.chat/
[3] - https://github.com/convos-chat/convos/
[4] - https://convos.chat/
[5] - https://www.mumble.info/
-
Most used selfhosted services in 2022?
TheLounge (https://github.com/thelounge/thelounge) - web IRC client that I set to listen on my vpn/mesh. Works great on desktop and mobile, and supports push notifications.
- TheLounge: Modern, responsive, cross-platform, self-hosted web IRC client
-
IRCv3 2022 Spec round-up
FWIW TheLounge [1] and Convos [2] can front-end an IRC server giving it much of the look of a modern client and also chat persistence when using TheLounge in private mode. The trade-off in my opinion is scalability. With a bog standard IRCD I can handle tens of thousands of clients per node. Adding web persistent chat adds memory usage.
[1] - https://github.com/thelounge https://thelounge.chat/
[2] - https://github.com/convos-chat/convos/ https://convos.chat/
Home Assistant
-
Changes we're making to Google Assistant
Home Assistant can cast dashboard/media/etc to your display and has shopping lists. https://www.home-assistant.io/
-
Valetudo – Cloud replacement for vacuum robots enabling local-only operation
If you provided MQTT support like plenty of IoT companies do, then any open source home automation tool can integrate! Home Assistant (https://www.home-assistant.io/) have a grading system, so a local-first implementation would give you their highest score since they also really care about privacy. https://www.home-assistant.io/blog/2016/02/12/classifying-th...
- Ă„lytaloista kokemuksia?
- Is there a way to see actual print time after a print is done?
- It's no handy app but...
-
List of your reverse proxied services
Home Assistant
-
How I use "AI" to entertain my cat
Next, I needed to wire this up to my home speakers and play a sound familiar to Max. In the before times of not watching live animals outside, Max liked it when I'd play some bird videos on YouTube for him and they would all start with the same "chirp" sound. He knew this sound meant bird watching time. So I downloaded the video, extracted the audio, then split the chirp out into a custom 4 second .mp3 and stored it on my local Home Assistant instance which was already integrated with my Google Nest speakers. Luckily, Home Assistant's API is pretty friendly, but the docs definitely suck. Once I added the .mp3 file onto my Raspberry Pi where Home Assistant is hosted, I was able to trigger the sound to play on my speakers with this simple request to its REST API:
-
Mazda files false DMCA takedown notice to intimidate open source programmer
https://github.com/github/dmca/blob/master/2023/10/2023-10-10-mazda.md
https://www.thedrive.com/news/mazda-slaps-developer-with-cease-and-desist-for-diy-smart-home-integration
https://web.archive.org/web/20231014070536/https://old.reddit.com/r/homeassistant/comments/1771ywu/removal_of_mazda_connected_services_integration/
https://community.home-assistant.io/t/mazda-connected-service/354221
https://community.home-assistant.io/t/removal-of-mazda-connected-services-integration/625885/36
https://www.home-assistant.io/
https://youtu.be/l2qKEkG29gI
https://youtu.be/NfiIXooD77s
https://youtu.be/PrtbYu1OYhY
https://youtu.be/nigJMu0lUbM
https://youtu.be/qLlxOD5IHYc
-
DMCA takedown for pymazda and node-mymazda
Relevant discussion in Home Assistant's PR removing the integration as well: https://github.com/home-assistant/core/pull/101849
-
Philips Hue will soon force users to create an account
Home Assistant https://www.home-assistant.io/
It's a quite powerful tool to integrate a variety of different smart home devices into one location and share them between ecosystems.
I have a wifi thermostat that requires a dedicated app and does not allow for Apple Home integration. With Home Assistant I installed an integration for that thermostat, then shared it with the Apple Home bridge (also an integration) and quickly was able to allow my iphone/automations etc, to modify the thermostat. And that's only scratching the surface and something that took a few minutes.
What are some alternatives?
Node RED - Low-code programming for event-driven applications
Domoticz - Open source Home Automation System
homebridge - HomeKit support for the impatient.
CasaOS - CasaOS - A simple, easy-to-use, elegant open-source Personal Cloud system.
FHEM - Branch 'master' is an unofficial read-only-mirror of https://svn.fhem.de/fhem/trunk which is updated once a day. (branch sf_old a mirror of the old repo: svn://svn.code.sf.net/p/fhem/code/trunk)
Mycodo - An environmental monitoring and regulation system
openHAB - Add-ons for openHAB 1.x
CompreFace - Leading free and open-source face recognition system
ZNC - Official repository for the ZNC IRC bouncer
Jeedom core - Software for home automation
Huginn - Create agents that monitor and act on your behalf. Your agents are standing by!
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.