Following old set up guide


#1

Ran into some issues. Can’t be sure if it’s because the video I followed was over two years old or not. It appears the script is up-to-date and functioning. After installing python on my windows 10 box I’ve dedicated for this activity. I see the same firewall pop-up as in the video. I accept. And I originally got a bunch of errors about missing modules. But then ran the command again with CMD in admin mode and things progressed further. Eventually i see [homeassistant.core] Starting Home Assistant - Timer starting… however NO UI ever pops up, rather an auto-discovery process begins. It fumbles a bit with my ps3’s DLNA server… then gets hung up on my Samsung Set Top Box. (second cable box)

2019-02-10 10:25:28 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 3.07s
2019-02-10 10:25:28 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2019-02-10 10:25:28 INFO (MainThread) [homeassistant.core] Timer:starting
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.components.discovery] Unknown service discovered: dlna_dmr {'host': '192.168.1.166', 'port': 7676, 'ssdp_description': 'http://192.168.1.166:7676/smp_12_', 'name': '[STB]GX-SM530CF', 'model_name': 'SM530CF', 'model_number': 'AllShare1.0', , 'manufacturer': 'Samsung Electronics', 'udn': 'uuid:127a3980-0036-1000-a373-1077b1abe5dd', 'upnp_device_type': 'urn:schemas-upnp-org:device:MediaRenderer:1'}
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.loader] Loaded cast from homeassistant.components.cast
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.loader] Loaded upnp from homeassistant.components.upnp
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.components.discovery] Found new service: samsung_tv {'host': '192.168.1.166', 'port': 7676, 'ssdp_description': 'http://192.168.1.166:7676/smp_3_', 'name': '[STB]GX-SM530CF', 'model_name': 'GX-SM530CF', 'model_number': '1.0', 'serial': '20090804RCR', 'manufacturer': 'Samsung Electronics', 'udn': 'uuid:127a3981-0036-1000-b709-1077b1abe5dd', 'upnp_device_type': 'urn:samsung.com:device:RemoteControlReceiver:1'}
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.components.discovery] Unknown service discovered: spotify_connect {'host': '192.168.1.108', 'port': 52155, 'hostname': '25d2051019ca6596-0.local.', 'properties': {'CPath': '/zc/0', 'VERSION': '1.0', 'Stack': 'SP'}}
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.setup] Setting up media_player
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.setup] Setup of domain media_player took 0.0 seconds.
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.loader] Loaded media_player.samsungtv from homeassistant.components.media_player.samsungtv
2019-02-10 10:25:41 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.samsungtv
2019-02-10 10:25:41 INFO (SyncWorker_3) [homeassistant.components.media_player.samsungtv] Samsung TV 192.168.1.166:55000 added as '[STB]GX-SM530CF (GX-SM530CF)'
2019-02-10 10:25:52 INFO (SyncWorker_5) [root] Sending handshake.
2019-02-10 10:25:52 WARNING (SyncWorker_5) [root] Authorization cancelled.
2019-02-10 10:26:03 INFO (SyncWorker_13) [root] Sending handshake.
2019-02-10 10:26:03 WARNING (SyncWorker_13) [root] Authorization cancelled.
2019-02-10 10:26:14 INFO (SyncWorker_4) [root] Sending handshake.
2019-02-10 10:26:14 WARNING (SyncWorker_4) [root] Authorization cancelled.
2019-02-10 10:26:25 INFO (SyncWorker_14) [root] Sending handshake.
2019-02-10 10:26:25 WARNING (SyncWorker_14) [root] Authorization cancelled.
2019-02-10 10:26:35 INFO (SyncWorker_15) [root] Sending handshake.
2019-02-10 10:26:35 WARNING (SyncWorker_15) [root] Authorization cancelled.
2019-02-10 10:26:46 INFO (SyncWorker_2) [root] Sending handshake.
2019-02-10 10:26:46 WARNING (SyncWorker_2) [root] Authorization cancelled.
2019-02-10 10:26:57 INFO (SyncWorker_16) [root] Sending handshake.
2019-02-10 10:26:57 WARNING (SyncWorker_16) [root] Authorization cancelled.

then it gets stuck in this loop of trying the handshake and never stops. I let it run for over a half hour. I even attempted blocking the device by Mac address in my router… rebooted the router … no DHCP lease to that IP anymore… and re-ran the script… and i’ll be damned if it didn’t find it again… and start this loop again… even without it connected to my network WTF!

Did it save this info into configuration the first time it ran? Can I remove it? What is happening here exactly? why is it trying to get root on my samsung cable box? i’m so confused. two commands in the video set up… but zero troubleshooting …


#2

It is highly recommended to use something other than Windows for home assistant


#3

I saw quite a few similar responses when creating this topic. Why do the creators suggest it works on windows 10 if it doesn’t? Who DOES have it working on Win10? and what did they do? I have linux boxes available, but none I want to solely devote to this. Like my Odroid-C2 and Rpi are both dedicted to other things i’m not trying buy another SBC just for this. Nor am I trying to have my main win10 box on all the time. So a low power, fanless win10 box I had sitting around seemed to be the PERFECT solution for me.

Obviously the server started… Why can’t I view the UI? Why is it looping on the Samsung box?


#4

They do?

Notice the recommended and alternative installation sections? See Windows anywhere?

Following the link to the user guides section for installing on Windows yields this.

The Microsoft Windows platform is not a primary target to install Home Assistant. Also, not all tools and third-party modules will work.

Not many people. People that got it working found it is severely limited by Windows and moved on to better setups.

So use docker? You don’t have to dedicate the device to this only.

Install virtual box and run hassio then?

It’s hanging on the discovery part. It’s trying to add your TV but it’s failing.


#5

If you want to run Home Assistant on Windows, you have the option to run it on a virtual Linux machine that runs within Windows…

The basic procedure is this:

  1. Install Oracle’s(free) “VirtualBox” software.
  2. Use the VirtualBox GUI to define/create a virtual machine that will run within your Windows system … it’s easy.
  3. Install whatever Linux version you like on the virtual machine.
  4. Boot up and configure your new Linux virtual machine … then load Home Assistant.

VirtualBox is one of many “Hypervisors” that can be used to create, run, and manage virtual machines. I’ve used most of them at one time or another, and I’d recommend VirtualBox for this type of project. It has everything you need, and it is easy to use.


#6

Note that no UI will ever “pop up” - you need to use a web browser to access HA. Try opening a browser and going to ip-address:8123 (if you’re doing it from the same box running HA, try 127.0.0.1:8123 or localhost:8123).


#7

So, upgrade it to linux!