After successfully migrating over from Wink, my Home Assistant is down. Not sure how to connect to my pi either.
I actually recently posted the following in the Reddit sub:
Successfully moved my whole smart home from Wink to Home Assistant (cloud with Alexa) without nabu casa. On my wink I had myQ and Alexa linked, and loved the remote feature. Home Assistant wasn’t easy but it also wasn’t impossible. I’m also fairly new to r/HomeAutomation so I hope this post is in the right place to help a now formal Wink user who didn’t want to pay the $5 a month.
My Journey started the day Wink announced they would start a subscription start. I bought a Raspberry Pi 4 and Nortek stick for zwave and zigbee.
CanaKit Raspberry Pi 4 4GB Starter Kit - 4GB RAM
GoControl CECOMINOD016164 HUSBZB-1 USB Hub
Coming from a super noob, I had no idea what to do and I plug my monitor, keyboard, and mouse into my pi to download hass.io. This didn’t work and then I tried the imaging with etcher. For a few days I was stuck here because I didn’t know that using a mac you need to format the SD Card and clean the disk to FAT32. My next issue was I was still using the pi on the wifi (still an issue). I monitor the hass.io installation from my monitor connected to my pi and never finished. For days it was stick starting and stoping something because of “wlan0: link is not ready”. I ended up pluging an ethernet directly in my pi just guessing that it worked and decided to see if homeassistant.local:8123 would load. And it did! For my initial setup I followed this youtube video: Beginner’s guide to Home Assistant
This video also has a previous version to that could be helpful as well. I think a confusing thing I ran into was how normal he makes the whole process sound. I ended trying to use the unified addon which is wrong. His process is good (not) for setting the remote access without nabu casa. I used the DuckDns addon and ran into trouble with this as well. I had my cloud working but not SSL cert, ended up being a config issue with the “-”.
Adding all my devices were easy except for my locks. The documentation on Home Assistant is what I found to be most helpful this. I still am not quite sure what some of the statuses mean on my locks however.
Kwikset 98880-004 SmartCode 888 Smart Lock
These are good locks for the price but just are to add to any smart system, I had trouble with Wink and just about the same amount with HA so keep that expectation. However, I was nice that I was able to configure user codes within HA (can’t this on Wink). Another stab at Wink was after the connection to Alexa on HA I was able to lock/unlock and do garage functions as well.
Connecting HA to Alexa with HA cloud is super hard but Home Assistant Documentation makes it actually really easy. Except theres one flaw, account linking requires you use port 443. Port forwarding on remote access makes it so you port forward 443 to 8123, which means you cannot link HA with Alexa. My work around for this was simply changing the default port in the config.yaml.
Boom! I did it! I moved over the Sengled Smart LEDs , my locks, (Dome) Water Shut-Off Valve, leakSMART Water Sensor, and reintegrated Alexa and myQ plus Ring. Yes it was a bit of work but now I will never have to worry about paying $5 a month. Also it was a little fun and now I have more control. I used Yonomi to control my locks and garage with Wink before this.
After I posted this I forgot about my GE zwave switch that was still connected to Wink. I couldn’t get it to connect my Home Assistant so I decided to turn my Wink back on and remove it from their app. A bunch of my devices reconnected to my Wink, so I removed those again in addition to the switch. I unplugged my Wink then restarted my Home Assistant but it never booted back up. So I turned off power to my pi, waited a bit, then tried again without any success. My pi is on but I still cannot reach it on my duckdns domain and I was never able to connect to from my mac, so I don’t know how to diagnose the problem. Has anyone else had a similar issue? Not sure what to do