Domoticz (used for zigbee integration) have been bothering me so much that i've been looking at HomeAssistant to replace it. Now that Z-way is moving in with an integration, its even more tempting..
But i don't like the idea of having it as an OS that I can't use for other things, and running the HASS Core in a docker seems to be somewhat reduced in terms of addons?
I realize that HASSOS is using docker for integrations or addons, but can I still use docker compose to set up my own dockers (i.e z-way, influx, grafana) there as well?
I guess i'm getting old, change is difficult! 😉
I've just started to look at HASS UI, and have seen enough to see that it has an infinite number of ways to show enitites and devices in all forms and shapes.. But for starters i'd like to have something familiar, so how do i go about getting a sidebar for rooms like in openluup?
I know i can put them in the actual left sidebar, but i'd prefer to keep that for configuration pages..
on each room page i'd like to sort the lights, the heaters, the sensors together, and i saw somewhere that HASS will do that for you if you play your cards (pun) right.. can't find it again now..
Any pointers to a beginner?
Relates to Vera integration in Home Assistant
Just for you to be aware.
If you are using plugs (or whatever) in Vera to measure energy for your appliances this is deprecated in 2022.4.0 since the HA integration to Vera is not updated and maintained anymore.
Skärmavbild 2022-04-14 kl. 19.54.47.png
Skärmavbild 2022-04-14 kl. 20.48.06.png
Time to move away from Vera for z-wave ...
Link to HA thread:Apr 8, 2022 Update 2022.4.0/ Remove energy usage/ VERA Update 2022.4.0/ Remove energy usage/ VERA
Yes, it can truly be a hard time to keep up with all the changes and sadly that no one maintains Vera no more. The REST sensor can make it live a bit longer at least for now… sensor: - platform: rest name: "ender_kwh" resource: http://IP_OF_VERA:3480...
I've integrated Reactor and Z-Way Expert panel in my HA UI, but as it is iFrame, it will not work if I log in from the outside.
It would be great to access these in case my wife finds an automation flaw while I'm elsewhere, which seems to be the rule of thumb..
If I understand this right, all the dockers(reactor, z-way) host their own web server on the port, so it should be possible to get this throuh the HA "tunnel"(VPN or whatever its called)?
I noticed that my Octoprint camera is integrated differently, and can be seen on external connection as well even if i only give it a local address in setup?
(Not sure it's the right HA bridge but....)
I have a selection of HA bridge devices to enable Alexa integration. They all work perfectly except one that has just (48 hours) started saying that it's un responsive with Alexa. If I go to the HA bridge and test on / test off it works absolutely perfectly.
I've deleted and renamed from the Alexa App but no change. Simply says 'Device Un-responsive'
I am currently running Home Assistant and Vera at the same time. I have installed a couple of ZEN32 5 button controllers but having issues getting the additional buttons to control my Vera devices. Am using the ZEN32 (Z-wave JS) blueprint which works well for devices on HASS. In developer tools I can use the Light:Toggle service and toggle my kitchen light through Vera. If I create the same action through the ZEN blueprint it doesn't work.
Anyone have any thoughts?
Since a couple of days, I'm not able to use the TTS in MSR (HA). I haven't done anything else but updated HA. Don't know if that's the source of the problem. Have this happened to anyone else, or is it just me?
When I searched in the HA community, there seems to be a croud of people having this issue - but they often refers to Alexa, so they may not have my problems.
I took a snapshot of a MSR instance, where it shows that the TTS is missing. I use to have 4 different TTS engines to choose from - now I have none. Am I alone in this?
I have had big troubles connecting HA to MSR. Finally I found out that MSR will work as long as my HA-installation is http, and not https.
Is it possible to bypass that limitation even with https?
Opening a thread to discuss updates to my home assistant fork.GitHub - rafale77/core: Open source home automation that puts local control and privacy first GitHub - rafale77/core: Open source home automation that puts local control and privacy first
:house_with_garden: Open source home automation that puts local control and privacy first - GitHub - rafale77/core: Open source home automation that puts local control and privacy first
I am trying to keep it on par with the official one but have made quite a few tweaks focused on video handling and processing. Home Assistant being developed on python is a great base for integration of machine learning and deep learning models into smarthomes because it is one of the most common languages used in the field.
As of today, I updated the readme file and the version to match the latest official release.
Most of my spoken commands to Alexa go something like this:"Alexa, time for bed"
at which point she executes a pre-planned Routine (triggered by that spoken phrase). The routine may turn On a virtual switch (named, say, "VS: Time for Bed" on my Vera Plus, but known to the Alexa Smart Home skill as "Time for Bed" just to keep my sanity).
The VS is a child device of Switchboard plug-in (by @toggledbits ) and acts as a binary (On/Off) light switch. Typically, I'll instruct Reactor to turn the switch back off -- or, more commonly, have it set to turn itself back off after NN seconds in the Switchboard UI. In other words, it's just a brief Trigger for a Reactor routine or Vera scene.
Now, here's my question: In order to avoid creating dozens of virtual switches -- one for each Routine / Scene -- has anyone tried using a DIMMER instead?
Seems to me that a dimming device, since it can be set to 100 different "brightness levels", could trigger 100 different responses in Reactor. But I'm hesitant to try this arrangement until I know others have had success, and that the faux "dimming" process won't inadvertently trigger intermediate values (e.g. "ramping") along the way.
Eager to hear if this alternative workflow makes sense and is practical, insofar as "Binary" and "Dimmer" seem to be the only switch types that Vera allows Alexa to "see" on Discovery.
Thanks! - Libra
Paulus Schoutsen / Mar 17, 2021 Nabu Casa has acquired ESPHome Nabu Casa has acquired ESPHome
Nabu Casa has acquired ESPHome to ensure that the project can continue to flourish as a free and open source project.
They are moving fast...Franck Nijhof / Mar 2, 2021 2021.3: My Oh My 2021.3: My Oh My
Introducing My Home Assistant, a new UI for service calls, 100% Fans, Z-Wave JS updates and Supervisor updates.
EspHome acquired by Nabu Casa
therealdb last edited by