This was originally built for MQTT + OpenHAB, but now I’d like to migrate over to MQTT + Home Assistant.
It’s based on an Arduino Mega which processes settings and values over various different MQTT topics. It has a kind of “zero config”, where the Arduino sends out its MAC address to a setup topic home/megasetup, and OpenHAB would respond to this by sending 3 messages back on a new topic comprising the MAC address:
home/megasetup/DEEDBAFEFEED -> ZONEVECT Bedroom (name of the controller) home/megasetup/DEEDBAFEFEED -> ZONENAME LG_Bedroom (name of the zone it controls) home/megasetup/DEEDBAFEFEED -> ZONESENS 25 (name of the zone it controls)
Now the Arduino knows what topic to send its commands on, in the above case it would be /home/bedroom/megacmd, and OpenHAB would (in separate rules) respond to commands on this topic by controlling lights / music / boiler / lighting scenes etc.
This seems pretty easy to replicate in Home Assistant, however due to the sheer number of possible messages to configure, my automations.yaml file will get really long.
Can you help me in the following 3 ways?
In an automation, I sometimes need to send a number of payloads sequentially. Right now, I have to invoke the mqttt.publish service each time, rather than invoking it once and sending say 20 payloads. Obviously the below doesn’t work, is there another way? If not, my config files will become very long and unruly… (4 lines for a single MQTT message instead of potentially 1)
Is there a way to do this: “trigger if I receive a payload on this topic, then do an action based on what that payload was”? Initially I thought I could use a condition, nested under an action. But If I understand correctly, conditions can’t be used to interpret the contents of a trigger?
For ease of managing all of my wall controllers, am I best off creating “entities” for each one somehow? Is that possible? Is there some way to make a custom service, that e.g. when you set its state, it will publish MQTT messages on topics?
Hi all - I was randomly Googling just now, and came across this post I made from 18 months ago (!)
Here’s my current state of play:
In the last few months I have adopted Node-RED and set up a touchscreen wall controller based on cheap Amazon Fire 7 (custom built frame, so touchscreen is flush to wall)
I really like the touchscreen… BUT - guess what? I get annoyed by it, exactly like I thought I would before designing my wall controller (shown above) - I miss the instant control of light and audio with physical buttons. Sometimes the Fire 7 is slow to respond (in computing terms, it’s not powerful - ok the Arduino has pretty much no computing power but it’s purpose-built to do one thing, and is more like controlling a lightswitch - instant on / off / dimming. Same with audio volume)
I know this is kind of a backwards way of doing it, but I’m going to try to include HomeAssistant into my Node-RED setup - basically to do the heavy lifting for automation devices (state management, maybe scene management) but keep Node-RED for complex rules and all the “glue” that holds it together
My old panel is still in the wall in the bedroom, but powered off. I miss using it as I can only control lights with Alexa and iPhone right now - urgh - it will be much better when I have a proper light switch working
In summary, my ultimate setup in our new home - when it’s built - will be physical button lightswitches and audio control, with a few touchscreens dotted around for more advanced stuff like reading rainfall graphs and the like…
Either way - there’s no way I’m going to use Home Assistant for rules - just not worth the effort with yaml. Much prefer Node-RED in that respect.
LOL… I forgot about this…
I’ve learned a bunch about the Soundweb device and one of them is kind of ‘show-stopper’… in that it is not capable (As shipped) of live updates - the text that is displayed is updated via loading a ‘config’ file - so my idea of being able to push changes or update it from a central server would only be possible with a full hack of the hardware.
I’m still thinking about this - just buy the device and then rebuild it from the ground up.
Or source the parts and build my own backend.
The idea that there is a LCD with 4 seperate zones of color, and fully RGB colored buttons is really sexy and offers so much in terms of user feedback - with what I like call user targets - that the buttons are a real fixed point to push…
If I could find a co-developer, I’d be willing to put some money into it.
Anyway, I’m new to this whole Home Automation thing and have not moved forward with this at all.
But I need to make decisions so we can figure out how to wire the walls for controls, whatever they maybe.
You mention that you’re using ‘proper light switches’ in the new house…
What switches are you using an how are you integrating that with home automation?
Hey Matt,
We are still in the process of developing the Home automation in our factory conversion to residence project.
My biggest issue is we are basically going to have ONLY dmx controlled linear strips in the entire project so ‘light switches’ are useless.
I’m feeling much the way you are about touch screen devices. And recent expereiences in a house with an Elan System just supports my feeling.
I’m still keen to hack the BSS audioweb device and might try one day. (EC-8BV)
I’ve also recently run across ORVIBO and really love the look, and they have physical buttons! BUT no indicators on the buttons, so not sure it’s worth the cost.
I am actually surprised that there are no good tactile wall switches out there. Perhaps they just aren’t needed anymore.
We also recently got an Alexa for the apartment to be able to check in on mom, but again, it takes too long to get what I want.
Any update on what you ended up with in the new house?
Did you stick with OpenHAB or Move to HA? I think I read the Node-RED works in HA now?
