social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
RE: https://mastodon.uno/@giuseppegv/115730518668624174
I like the idea of this post. Here is mine with some additions of my own:
OS
- Desktop and laptop
- #Debian 13 with #Cinnamon
#homelab server
- #Proxmox 9 with #Debian and #HomeAssistant OS VM's
Email
Service providers
- @disroot and @Tutanota
Client
- #Betterbird
Notes
- @logseq
Browser
Desktop
- @mozilla #Firefox , @librewolf , and @torproject
Mobile
- #IronFox
VPN
- @mullvadnet
Password and TOTP Manager
- @keepassxc with #Syncthing
Search
- #DuckDuckGo , @ecosia , and @marginalia
Social
- @Mastodon and @pixelfed
#FOSS #Debian #GNULinux #GNU #Linux #Proxmox #homelab #homeassistant #disroot #tuta #tutanota #betterbird #logseq #Mozilla #Firefox #Librewolf #Tor #Torproject #IronFox #Mullvad #MullvadVPN #VPN #TOTP #KeePassXC #Syncthing #DuckDuckGo #Marginalia #Mastodon #Pixelfed
I'm running my VM in proxmox, but I assume that VirtualBox would be just as good.
I didn't mean to sound like I was criticizing your choice to run in docker - I did that for literally years before deciding that not using HAOS was adding more aggravation than it's worth. Some integrations just run better on HAOS or (at least for some 3rd party ones) aren't even tested on anything else.
That said, there are a lot of third party things you can run outside HAOS - I run Node Red, Frigate, zigbee2mqtt, zwaveJS and mosquitto in independent docker containers on other hosts and have HAOS connect to them.
It sounds like you have a lot of interesting hardware in your existing automation system that may or may not have integrations already.
One way to work around that would be to run an MQTT server like mosquitto in a docker container, then update your existing bash scripts write data to MQTT entities so HA can read the entities.
If you format the MQTT entities right, HA will automatically discover them as devices or sensors without you having to create custom MQTT sensors. That auto-discoverability format is a little finicky, but if you're comfortable with python I wrote (with a lot of recent improvement by Steffan Pankratz) a library that makes writing automatically discoverable entities easier.
Diese Woche geht's bei @ajfriesen und mir um Monitoring im Smart Home und dem Homelab. Welche Arten von Monitoring gibt es? Wieso ist das wichtig? Welcher Ansatz eignet sich fürs Smart Home? Darüber hinaus berichtet Andrej über seine Migration von Fritz zu UniFi für WLAN, LAN und Router.
Im Podcatcher eurer Wahl oder hier: https://podcast.smarthuette.de/episodes/grune-balken-machen-glucklich-monitoring-im-smart-home
Viel Spaß beim Hören!
#homeassistant #homelab #unifi #monitoring #uptime_kuma #zabbix #prometheus #nagios #icinga #grafana #linux #docker #traefik
My lights didn't turn on to wake me up! And home assistant's last trace is sometime in November so I have no idea why! (By the way, if any other home assistant users are reading this and know why I don't have traces that are, like, in this month, let me know!) But I guess I needed the sleep and the only repercussion is that I missed the gym this morning. At least I feel rested!
Anyway, uh.... Good morning!
#gym #goodmorning #homeassistant
Ernst gemeinte Frage an alle #RaspberryPi Fanhumans: Wie lange halten eure #SD Karten?
Ich habe für mich privat das Nutzen von Pis längst aufgegeben, weil mir nach 2 bis 3 Jahren die Systeme zuverlässig die Hufe hoch gemacht haben, weil die SD Karten tot waren.
Jetzt ist auch das letzte System ausgefallen.
Lief 3,5 Jahre mit #HomeAssistant. Und jetzt isser einfach tot. Bootet nicht mehr.
Von meinen x86 ThinClients mit normalen Samsung SSDs ist mir noch nie eine ausgefallen...
If your rPi can't boot from an SSD, next time you upgrade, look at setting up an SD card that boots the rPi and then mounts an external SSD as the / partition.
It'd be a hack, but then all your configuration will be on the SSD, and you can keep a spare boot SD card. I would be surprised if the boot-only SD card needs more than 8GB.
HAOS is the best supported way to run Home Assistant - consider running it in a VM instead of HA in docker containers.
I ran HA in docker for years but eventually got tired of not being on the golden path where everything gets tested more thoroughly.
After 15+ years of #Domiticz home automation software I figured it’s time to try Home Assistant, not really because I need it, more because I can.
My environment is quite large and complex so it’s going to be a long transition, bare with me
I’m using MQTT, a lot of Node-red logic, IKEA with gateway, a huge 1-wire network, several bash scripts, several Blocky scripts, Rfxcom with a lot of devices. Many scenarios and time events, ambient controls, and much more.
For now I have a Docker running HA and a ESPHome connected to the IKEA Gateway and realized that it can’t see the events from IR sensors and that I probably need a Zigbee gateway. Happy to get a nodeMCU showing the temp values from a DS18B20 Dallas on the GPIO pins but sadly realized that to configure each device it needs to be available as a pre built device. Hmmm and a lot of my devices are not yet integrated, this means I will need a 1-wire master for the HA, because I like to leave the Raspberry 1-wire setup as today. Why? Because I have to put too much work into it at every upgrade and the Rpi stability considering SD-cards are not the best. (Even though my last installation has run 4+ years on the same card)
Well, the slow journey has at least started towards a new environment, let’s see how it progresses
Quick calc from #HomeAssistant energy readings + the odometers from the familly ebike (tern HSD riden with passenger at the back or heavy shopping loads)
750km in one year with 6.2kw
120km / kWh
Very happy with my Home Assistant battery monitoring dashboard. It will automatically add new gauges when I add new devices to the house.
Better go change the battery in my garden lights button.
It took me almost a month to actually get these #Aqara THA sensors delivered. Had 2 orders cancelled because the item was unavailable…
Also, I remember buying this kind of sensor for 5$ back in the day…
Theoretically I should have all parts to make my humidifier a smart humidifier over the holiday break.
Maybe a good excuse to try Rust on an ESP32.
Suggestions which #HomeAssistant enabled humidifier to order once I’m done with mine welcome.
Hello la communauté #homeassistant !
Je cherche des interrupteurs sans fil pour piloter des actions/appareils via home assistant.
Je suis curieux de savoir ce que vous utilisez.
Quelles marques, quel protocole, quelle portée...
Pour l'instant je n'ai pas ajouté d'antenne zigbee ou thread sur mon instance, j'utilise surtout matter avec les quelques appareils compatibles.
Merci d'avance pour vos retours.
Our small domotics setup has been updated to the latest version of Home Assistant. I'm still using Home Assistant Core so I'm on my own, that way of running Home Assistant is not supported anymore.
So made a backup, installed Python 3.13, recreated the Home Assistant virtual environment, installed Home Assistant, copied over the Home Assistant configuration directory and started Home Assistant.
Few minutes later everything was up to date again.
1/2
Rendre les thermostats pilotables obligatoire dans tous les foyers ? Apparemment la loi est déjà passée, mais le gouvernement repousse la date d'application.
Pourquoi pas, mais alors obligeons les fabricants à ouvrir les protocoles de pilotage de leurs machines. Je veux pouvoir me fabriquer moi-même le thermostat.
Pffffff... #HomeAssistant me dit ça :
The legacy platform: template syntax for sensor is being removed. Please migrate netatmo_hvac_modes to the modern template syntax.
Remove existing template definition.
Add new template definition:
template:
- sensor:
- default_entity_id: sensor.netatmo_hvac_modes
name: Hvac modes Général
state: '{{ state_attr(''climate.salon'', ''hvac_modes'') }}'
Restart Home Assistant or reload template entities.
Mais je fais ça où et comment ?
Une idée ?
Was dieser Wohnung lange Zeit gefehlt hat war ein Außenthermometer.
Jetzt hab ich eins! Es wiegt drei Tonnen und misst nicht besonders hochauflösend, aber naja.
(Habe gestern noch etwas mehr Protokoll-Reverse-Engineering bei der Aufbauelektronik im Wohnmobil gemacht und dabei das am Unterboden montierte Außenthermometer auf dem RS485-Bus gefunden.)
Diese Woche geht es bei @ajfriesen und mir um neumodische Rezeptverwaltung bis hin zur Eskalation. Darüber hinaus reden wir über Home Assistant Installationen und Proxmox Evangelismus.
Beim Podcatcher eurer wahl oder hier: https://podcast.smarthuette.de/episodes/eisstabchen-skalieren-nicht-rezepte-verwalten-und-home-assistant-installieren
Viel Spaß beim Hören!
#homeassistant #mealie #grocy #kitchenowl #valetudo #roomba #proxmox #linux #pve #utm #openprinter #joplin
I've also got a couple of BLE temperature/humidity sensors in several places in the van.
They have a 0.1°C accuracy, but because they're reporting every few seconds, Home Assistant can calculate a very smooth temperature curve by simply averaging the values.
The blue background behind the curve represents the span of the values measured during that time period, and the blue line is the average.
1. reverse engineer the RS485 bus for the battery management and water level sensors in your van
2. write a daemon that polls these values and pushes them into MQTT
3. set up Home Assistant in the van
4. profit
Playing around with this ⬆️ feature some more, and I just love it.
The file in the screenshot was all I needed to deploy Home Assistant.
One single file, followed by `systemctl daemon-reload && systemctl start homeassistant`.
It will automatically create /var/lib/homeassistant and expose it to the container, as well as run nightly updates using `podman auto-update`.
#Zigbee #HomeAutomation without
#HomeAssistant, instead all defined in
#nix / #NixOS, this is neat! 😲
Three of my radiator valves are saying that they want to update their software. What a bonkers world we now live in.
And today I discovered that after updating their software they only retained *most* of their settings, leaving me wondering why I was getting cold.
@ShadowJonathan brb gonna go fork and create FreedomAssistant where only imperial units are used and metric is deprecated.
#homeassistant #homeautomation
I have successfully set up a Zigbee controller on our #HomeAssistant pi and converted _most_ of our HUE lights over to use it instead of sending data to Hue's cloud.
4 of them aren't convertable, but I have replacements in my cart. Cheaper because no longer need Hue brand.
Also have little things to insert into wall behind switches to make other things "smart"
Quelqu'un a déjà installé un capteur #SDS011 sur un serveur #HomeAssistant ? Je n'arrive pas à faire communiquer HA avec le capteur. J'ai cette erreur :
"Platform error 'sensor' from integration 'sds011' - Integration 'sds011' not found."
avec mon sensor.yaml comme suit :
"- platform: sds011
serial_device: /dev/ttyUSB0
name: sds011
measure_interval: 30
"
et manifest.json :
"{
"domain": "sds011",
"name": "SDS11 Air Quality monitor",
"version": "0.1",
"documentation": "https://github.com/mrk-its/homeassistant-sds011",
"requirements": ["py-sds011==0.9"],
"dependencies": [],
"codeowners": ["@mrk-its"],
"homeassistant": "2025.10.3",
"iot_class": "local_polling"
}"
une idée ?
today I added two Tapo C200 and a 3D buddy to homeassistant.
why did it took so long?
a few years for the TP-Link cameras.
This morning, 30 minutes focused et voilà!
New Home Assistant card I made last night. As a salaried employee, display the dollar amount I’m effectively donating back to my company in free labor when I’m at my desk over 8 hours. Resets daily.
This may come off as if I’m disgruntled, but it was about seeing the real data of a thought experiment I had! And that having a real-time ticker might inspire me to call it a night sooner on long days.
@homeassistant #homeassistant #homeautomation #quantifiedself
Okay, so let me tell you about my doorbell, from a #networking perspective.
When you push the button by the door, it sends a message over the #zigbee wireless mesh network in my house. It probably goes through a few hops, getting relayed along the way by the various Zigbee light switches and "smart outlets" I have.
Once it makes it to my utility closet, it's received by a Zigbee-to-USB dongle, through a USB hub (a simple tree network) plugged into an SFF PC. From there, it gets fed into zigbee2mqtt, which, as the name implies, publishes it to my local #mqtt broker.
The mqtt broker is in the small #kubernetes cluster of #raspberrypi nodes I run in my utility closet. To get in (via a couple of #ethernet switch hops), it goes through #metallb, which is basically a proxy-ARP type service that advertises the IP address for the mqtt endpoint to the rest of my network, then passes the traffic to the appropriate container via a #linux veth device.
I have #HomeAssistant, running in the same Kubernetes cluster, subscribed to these events. Within Kubernetes, the message goes through the CNI plugin that I use, #flannel. If the message has to pass between hosts, Flannel encapsulates it in VXLAN, so that it can be directed to the correct veth on the destination host.
Because I like #NodeRed for automation tasks more than HomeAssistant, your press of the doorbell takes another hop within the Kubernetes cluster (via a REST call) so that NodeRed can decide whether it's within the time of day I want the doorbell to ring, etc. If we're all good, NodeRed publishes an mqtt message (more VXLANs, veths, etc.)
(Oh and it also sends a notification to my phone, which means another trip through the HomeAssistant container, and leaving my home network involves another soup of acronyms including VLANs, PoE, QoS, PPPoE, NAT or IPv6, DoH, and GPON. And maybe it goes over 5G depending on where my phone is.)
Of course something's got to actually make the "ding dong" sound, and that's another Raspberry Pi that sits on top of my grandmother clock. So to get *there* the message hops through a couple Ethernet switches and my home WiFi, where it gets received by a little custom daemon I wrote that plays the sound via an attached #HiFiBerry board. Oh but wait! We're not quite done with networking, because the sound gets played through PulseAudio, which is done through a UNIX domain socket.
SO ANYWAY, that's why my doorbell rarely works and why you've been standing outside in the snow for five minutes.
Je commence un peu à faire ce que je veux, à adapter pas trop difficilement les exemples à mon cas de figure.
Prochaine étape : rendre ça un peu plus stylé et passer en mode sombre...
#homeassistant #esphome #energyMonitoring #CYD #cheapYellowDisplay
I want to use presence detection in Home Assistant automations. I'm using the companion app on Android. My Home Assistant installation is accessible from both external and internal URL.
I would have thought that configuring either external and internal URLs, or home network SSID, should be enough to allow Home Assistant to tell if my phone is home or not, but the app seems to want full location access to work properly.
I don't care if Home Assistant keeps a record of where I am (or rather, I would prefer if it didn't), I just want it to know if I'm home or not.
Any ideas?
I'm on the hunt for peertube channels about the following:
I only speak English and a bit of Dutch, so unfortunately I'm having a bit of trouble finding peertube channels for my interests. Any help would be appreciated!
@ffeth une mission pour #HomeAssistant ? Il me semble avoir vu passer des capteurs de niveau d’eau (mais je ne sais pas s’ils pourraient s’adapter sur des bocaux). Une électrovanne connectée, une prise connectée, et une automatisation type SI niveau atteint ALORS couper la prise ET l’électrovanne
Migrated my Home-Assistant from the Raspberry PI 4 to a bhyve VM on my FreeBSD home-server ✅
Did configure acme.sh to get a Let's Encrypt certificate by using my public powerdns nameserver and the DNS-01 challenge ✅
Successfull implemented Passthru of my USB-controller to the Home-Assistant bhyve VM for ZigBee dongle ✅
Shut down and removed the old Raspberry PI ✅
I like it, when plans work out 🙂
I have just backup/restore/migrated my #HomeAssistant instance from a KVM virtual machine to the Raspberry Pi 4B (2GB) that was sleeping in my messbox.
That's cool because it means I do not require USB device pass-through anymore on the hypervisor. Hello #bhyve, I'm looking back at you.
Many #HomeAssistant Zigbee switch automations have now started also toggling other switches than the designated, bringing excitement about what else will turn OFF when I turn this light ON into an otherwise dull existence. 🤪
This product, honestly... 💩
#introduction Hello! I'm Hamzah. I'm a #linux/#devops engineer in my day job. I live in #london.
I consider myself a hardcore geek, but these days most of my time is taken up by my three kids and wife.
I'm very interested in automation, and have a small addiction to #ansible, #kubernetes and #HomeAssistant.
@rodolphe
Bonne question.
Ce qui me permet de voir que les fichiers date du 08 juin. Et que donc, ce n'est pas renouvelé comme prévu, ce qui est finalement normal puisque j'accède à mon serveur #HomeAssistant via un port spécifique qui est redirigé par mon routeur vers ce serveur. Car les ports 80 et 443 vont vers un autre serveur sur lequel j'ai un site web. Et donc, le certificat ne peut pas se renouveler puisque le port 80 ne renvoie pas vers mon HomeAssistant.
Par contre, quand je redirige 80 et 443 vers mon serveur HA, ça ne renouvèle pas non plus via le BluePrint, bizarre.
Problème avec #HomeAssistant. Avec #Brave, ça boucle sur le message "Unable to connect to Home Assistant. Retrying in xxx seconds"
Sur mon téléphone, avec le #HomeAssistantCompanion, j'ai le message "La date du certificat de Home Assistant n'est pas valide". Effectivement, dans Brave, ça me dit que le certificat a expiré hier à 9h00.
En revenant sur Brave, en mode "navigation privée", j'ai pu finalement me connecter en outrepassant le fait que le certificat SSL ne serait plus valable. Pourtant, le certificat est à renouveler le 07 novembre.
J'ai forcé le renouvellement, la date ne change pas, et toujours impossible de me connecter en SSL.
Une idée ?
Hey #HomeAssistant people I need a little help. I have an issue with a phone that from time to time gets banned. Whatever the limit I set, it just spams the /api/websocket with bad authentication. HA is only accessible over VPN, and it seems to be linked with times when the VPN is not up while moving out of the house (not 100% sure of that). Do you have an idea of what is happening and how to avoid that ? Disabling the ip_bans ? The device is a recent Android.
I've set the limit to 150 to test, and it happend to reach it in less than a second.
Sur mon #HomeAssistant je soupçonne que let's encrypt stocke les certifs quelque part et que nginx les cherche ailleurs. nginx me propose de chercher dans un sous répertoire de "ssl", mais tout ça c'est des chemins relatifs.
Comment est-ce qu'on a accès aux chemins absolus ?
@rodolphe merci pour les informations, j'ai déjà l'intégration Sonos dans #HomeAssistant, et le lien entre mon enceinte et HA fonctionne bien. Et globalement, mon enceinte, une Symfonisk de chez IKEA, fonctionne très bien, en #Aiplay avec mon ordinateur, mais, et c'est le truc qui m'agace parce que je dois du coup installer l'application #Sonos sur mon téléphone et donc créer un compte : mon enceinte ne diffuse du son que... si j'ai un autre appareil Airplay connecté et diffusant de la musique ! Si je coupe mon ampli #Yamaha, plus de son. Et je ne trouve pas comment faire, sauf... à paramétrer l'enceinte via l'appli Sonos. Bref, c'est n'importe quoi !
Logitech Harmony, c’est fini. J’ai tout juste pu mettre ce qu’il faut dans la mienne pour la Nintendo Switch 2 et je pense que ça ne durera malheureusement plus très longtemps.
En plus, faut avoir un Windows et du Silverlight et toussa pour la màj maintenant, alors bite ! Home Assistant !