Home Assistant

18 Topics 145 Posts
  • 1 Votes
    20 Posts
    258 Views

    Thanks to everyone for your input! It'll be a couple of days before I can get deep into this because I have very limited time these days to dabble.

  • 0 Votes
    1 Posts
    223 Views
    No one has replied
  • 0 Votes
    4 Posts
    244 Views

    thanks for the advice, the issue was simply solved by forgetting and repairing the device, I'm not sure, but there was an interference from my bluetooth headphones that I tried switching off, anyway the article below helped a lot with tackling the issue, I put it here so others can use it if ever encountering this issue:

    Erfan Askari  /  Jan 29  /  Voice Assistants How To Connect Alexa To Vizio Soundbar: Ultimate Guide | Smart Home Scope How To Connect Alexa To Vizio Soundbar: Ultimate Guide | Smart Home Scope

    Trying to connect Alexa to Vizio soundbar? Here’s a guide that’ll help you do it by Bluetooth and AUX, the choice is yours!

  • New HA instance

    6
    5 Votes
    6 Posts
    269 Views

    Just run everything under docker, including ha, and a single nuc is more than enough. USB are easily mapped via docker.

  • Using HA Harmony Hub to control volume

    4
    0 Votes
    4 Posts
    156 Views

    Well that was far too easy. Thanks for the pointer at /config makes it really simple!

    C

  • 1 Votes
    20 Posts
    818 Views

    HA is a very big piece of software. The current stable branch docker image is 1.6GB. I chose to run it on dedicated hardware; that just seems too large to saddle the NAS with. This makes the USB issue almost moot. I run ZWaveJS UI in a separate docker container, and use the recommended serial port aliasing (through /dev/serial/by-id/...). Both run under docker-compose. It's sane. No issues.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    8 Views
    No one has replied
  • Lovelace initial setup

    14
    0 Votes
    14 Posts
    506 Views

    Yes, the regular sidebar with dashboards is scrollable, i ment the custom sidebar i tried for a in-dashboard sidebar..

  • HA-Vera Energy Usage Deprecated since 2022.4.0

    4
    0 Votes
    4 Posts
    235 Views

    @toggledbits Yes, I am aware of that and this is how I use it with the rules in MSR but for redundancy (and dashboards) I also use the Vera integration in Home Assistant. I have not yet dived into the world of MQTT. 😁

  • Hosting web interface inside HA?

    2
    0 Votes
    2 Posts
    145 Views

    Images and cams are proxied by HA. You’ll definitely need something specific. I’m using synology’s ability to relay an internal address with a private dns to avoid using a vpn while at the office (or anywhere, when using my laptop). I’ve exposed Vera, reactor and ha this way and the normal tweaking is easy.

    The complex route will be to add ngnix, an authentication layer and route everything.

  • HA Bridge oddity

    2
    0 Votes
    2 Posts
    131 Views

    Well not really solved but....

    Copied the device in HA-Bridge. Discovered it in Alexa and it works. Deleted the old one and re-named it.

    Still works

    Go figure.

    C

  • Odd behavior in HA

    4
    0 Votes
    4 Posts
    216 Views

    There's an updated blueprint posted in the HA forum, but not easy to find. It's midway through a large thread.
    I don't have this device, so can't say if it's 100% working now.
    You can try contacting The Smartest House through their website. If they don't have something posted, they may point you in the right direction.

  • TTS gone in HA/MSR?

    9
    0 Votes
    9 Posts
    308 Views

    Any time you upgrade to a version that isn't supported, you run the risk that a change to the Home Assistant APIs won't be handled properly by the HassController class in MSR. In the last six months, there have been two changes that have changed their API significantly enough to cause issue, and in one of those two cases, it was total shutdown.

  • https not allowed in reactor?

    9
    0 Votes
    9 Posts
    354 Views

    OK. Of course, I was assuming, because of your example in reply to me, that you were making an HTTP request (via the HTTP Request action in reactions) to HA, not trying to use the secure websocket at the Controller interface level. This is why details in reports are important. More better than less. Also, if you have posted information from log files, it also would have been obvious that I was thinking about the wrong connection.

  • Home Assistant Fork

    1
    0 Votes
    1 Posts
    256 Views
    No one has replied
  • 0 Votes
    42 Posts
    2k Views

    @toggledbits No, I totally grokked what you were explaining, it's just that there's a (relatively new) well-documented problem of Amazon Alexa now only looking at port 80 during Discovery. Hence, whatever solution one rigs to intercept its inquiries, it must originate on some device's HTTP port 80. And that simply cannot happen (without major surgery and risk) on the Synology NAS, even if you try to instruct a Docker container to open it (yields red box and stern warning). Just no can do.

    therealdb is recommending a work-around using Vera, and I'm inclined to try that once I pin down where his info applies.

  • EspHome acquired by Nabu Casa

    1
    1 Votes
    1 Posts
    182 Views
    No one has replied
  • Latest HA release

    1
    0 Votes
    1 Posts
    178 Views
    No one has replied

Recent Topics