Earlier quoted context omitted.
For me it started with a single wifi lightbulb. My wife often gets into bed with the baby. If the baby falls asleep before the light is off, she doesn't want to get up to have to turn the light off since it will wake the baby. Now she can just turn it off from her phone. Kinda just expanded from there. Now a good chunk of the regularly used bulbs in the house are "smart". Basically what it means is that if you turn a…
> The lights in my office come on when I walk in if it's dark, and when I unlock my computer it shoots a message out over a MQTT broker which my automation takes as "someone is occupying this space now" and leaves them on. When I lock my computer, two minutes later if no motion is sensed it'll turn them off. What did you do to send the message when the computer locks/unlocks? This is an exact use case I could make us…
Working out from there:
* I use Windows as the host OS for my desktop. You can use Task Scheduler to set a task to run on lock/unlock. I have jobs set that mute/unmute my audio and call a MQTT client to publish the messages to the broker.
* Those messages are picked up by Node-RED. It's a ladder-logic-ish environment for automation. It has flows that control all the bits of logic based off of all the various data sources including MQTT.
* Node-RED calls Home Assistant, which handles providing a UI as well as actual integration with all the various bits of hardware (light bulbs, z-wave controller, etc)
I quite enjoy this stuff (which is probably half of how I got here), so feel free to ask if you've got follow-up questions.