Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

MaxTheDog73

Member
  • Content Count

    21
  • Joined

  • Last visited

Reputation Activity

  1. Like
    MaxTheDog73 reacted to jakkuh_t in HomeAssistant Google Assistant & MyQ Integration Tutorial   
    This tutorial is meant to show you how to setup a self-hosted HomeAssistant instance with Google Assistant integration. For this specific tutorial, we will be using UnRAID to manage our docker containers for all the apps we are using, but you could also manually install all of this directly onto your own Linux system without docker or into your own docker setup on a VPS in a datacenter in if you have the know how.
     
    As we mentioned in the accompanying video, there may be some potential security concerns with this setup - primarily that your HomeAssistant instance must be publicly accessible on the internet for Google Assistant to work with it. You can remedy this a bit by using Cloudflare as your DNS provider, which can hide your external IP address, and block automated bots from accessing your HomeAssistant page.
     
    If you want to use Google Assistant with your HomeAssistant instance, you're going to need the following:
    1. a HomeAssistant instance - we will be using the "Home-Assistant-Core" docker app from the UnRAID Community Apps plugin.
    2. a domain name - we will be using "autopilottonowhere.com" with DNS hosted by CloudFlare for the purposes of this tutorial
    3. an SSL certificate for the above domain name - we will have this automatically issued from LetsEncrypt by our reverse proxy ("NGINX Proxy Manager" from the UnRAID Community Apps plugin).
    4. remote access to your HomeAssistant instance by way of port forwarding
     
     Tutorial:
    Start by acquiring a domain name. You can use whatever registrar you'd like, but once it is purchased we'd recommend setting up the domain with CloudFlare. CloudFlare has some solid documentation on doing so here: https://www.cloudflare.com/en-ca/welcome-center/activation/ For the purposes of this tutorial we will be using "autopilottonowhere.com" Note: If you already have a domain you'd like to use you can skip this step, lol. Next, if you haven't already, install the "Home Assistant Core" UnRAID Community app onto your UnRAID server. There isn't any configuration needed for this, but it will ask you to create an account. Make sure you use very strong login credentials as the instance will be exposed to the open internet.  Set it to autostart. If you're hosting HomeAssistant at your house, you'll likely have a dynamic IP address (meaning it has the potential to change unexpectedly) and will need to do some additional steps, otherwise skip to #4: To make sure your domain automatically updates when your dynamic IP changes, we'll need to setup some sort of Dynamic DNS service. This will regularly check your external/WAN IP address, and update the DNS record if it changes. Assuming you're using CloudFlare, the UnRAID community app "CloudFlareDDNS" works perfectly for this.  Create a DNS A record that you want to be dynamically updated, but with a random IP address just so the record exists and can be updated. I'm not actually sure this is strictly necessary, but I did it anyways to prevent any potential issues 😛. We're going to use "homeassistant.autopilottonowhere.com". Make sure the little cloud is orange, as this indicates that CloudFlare is protecting your domain.    
    Before you can install the DDNS app, you'll need to create a Custom Token for the zone/domain you wish to use for HomeAssistant. Copy the API token into a text editor temporarily so you don't loose it. Otherwise, it will need to be regenerated. Click Install on the CloudFlareDDNS app from the UnRAID Community Apps page, enter the requisite info and hit apply. Check your CloudFlare "DNS" tab for your domain to make sure it is updating the record properly. 🙂  Set the DDNS app to autostart so that it comes back online, in the event that your UnRAID machine is rebooted.  If you have a static IP at home or wherever you are hosting it, create a DNS A record to point to your IP. We're going to use "homeassistant.autopilottonowhere.com". Make sure the little cloud is orange, as this indicates that CloudFlare is protecting your domain.   
    Install the "NGINX Proxy Manager" UnRAID Community App, during the install, you can leave the ports as default as we can forward them to the proper HTTP and HTTP(s) with our port forwarding rules.  Set it to autostart. Open the WebUI, login with the default credentials, then update them to be appropriately strong.  Email: admin@example.com Password: changeme Assuming your HomeAssistant instance is running on a NAT'd subnet, we'll need to forward the necessary ports to make it publicly accessible. Since we will be proxying it with NGINX Proxy Manager, setup your two port forwarding rules (one for HTTP (tcp port 80) and one for HTTPs (tcp port 443)) to forward to it (80 -> 1880 and 443 -> 18443) instead of HomeAssistant, as pictured. You'll need to use your GoogleFu to figure out how to do this on your specific router, but we're assuming you at least know how to port forward if you're willing to attempt this tutorial.  Note: if you haven't already done so, you should set your UnRAID server to have an static INTERNAL IP, otherwise it may change like a dynamic external/WAN IP would, and break our port forwarding rules. In our case, this is 10.20.0.29. Go back to NGINX Proxy Manager and apply for an SSL certificate for your chosen HomeAssistant domain. If this doesn't work, there is likely an issue with your port fowarding rules, so review those.   
    Still in NGINX Proxy Manager, create a Proxy Host.  Before saving, add the SSL certificate you created in the previous step to the Proxy Host.   
    Your HomeAssistant instance should now be accessible remotely through your domain of choice! 😄 To setup Google Assistant to work with your HomeAssistant instance, it's a bit of a long winded process if you're self hosting, but JuanMTech created an awesome tutorial for it. As long as you follow it and take your time, it will work without issue. https://www.juanmtech.com/integrate-google-assistant-with-home-assistant-without-a-subscription/  Important note: near the end of the tutorial you will be instructed to set the exposed domains. The MyQ openner is categorized under the "cover" domain, so make sure you included "- cover" under exposed_domains  If you want to link your MyQ door opener, go to Configuration>Integrations>Add Integration in HomeAssistant, type in "MyQ" and link your credentials. Then, in the Google Home app on your phone, ask google to "Sync my devices" and your garage doors, along with any other exposed domains should appear! Woo! Last step, the most difficult.... say "Hey Google, open <device name>", crack open your beverage of choice, and bask in the glory that is HomeAssistant. 
  2. Like
    MaxTheDog73 reacted to iKingRPG in HomeAssistant Google Assistant & MyQ Integration Tutorial   
    Dear linus/jakkah/LMG,
     
    I'm glad you finally tried Home Assistant. In the end of the video I noticed linus mentioned that he wanted to keep using the original relay to avoid the 5 second closing delay. It is possible to control the Sonoff relay in Home Assistant, you could use a custom integration that lets you do so, or a much better solution that would also avoid their cloud entirely, is to flash the Sonoff with custom firmware that allows it to be controlled 100% locally, and gives you pure control over the device.
     
    Another thing is if you won't want your relays on the wall next to your buttons, you could also put them on the ceiling. Open the cover off your garage door opener, and if you see a button that opens/closes the garage door opener, that means you can run leads from there to the relay, which should allow you to control it again from the relay with no problems.
     
    Another reason why you might want to do this, is you know how you said Chamberlain is a bad company? Well, even though now you are controlling the garage door opener locally, Chamberlain will still screw you over. You see, there is no official MyQ API, this means that the way the Home Assistant integration for MyQ has to work, is by emulating the mobile app. So when you close your garage from home assistant, they think you are closing it from the app. This is bad, because this means that every time MyQ makes a change to their app or API, the integration breaks, no longer allowing you to control the opener. Normally the Home Assistant developers patch it after 1-2 days, but it's still really annoying. It breaks every few weeks randomly.
     
    Back to flashing the Sonoff. Personally the firmware I use is called ESPHome, which is open source firmware designed to run on any device using an ESP8266 microcontroller (like Sonoff wifi devices), and they connect directly to the Home Assistant local API. There is also an alternative firmware called Tasmota, but I'll explain how to use ESPHome, because it is simpler.
     
    First, you will need to buy some things if you don't already have them.
     
    USB to TTL/Serial converter: (this is the one I use)
    https://amazon.com/dp/B075N82CDL/
     
    Jumper wires: https://amazon.com/dp/B07GD2BWPY/
     
    Next, you will need to install the ESPHome Home Assistant Add-on from the Add-on Store.
     
    Open the ESPHome interface and add a node, fill out the wifi info, device name, etc. There are video tutorials that explain this.
     
    After you do that, click "edit". This is the configuration code for the firmware that you are about to flash to your Sonoff. You're going to need to add some code. The code that's there will work, but the device will just connect to your wifi network and not do anything. You need to tell the firmware that you want to control relays.
     
    From the video, the relays you use look like a Sonoff 4CH Pro. I have that too, and this is the code I use. Just copy and paste this after the line with your OTA password, the change the names of your relays to whatever you want, something like "Garage door 1".
     
    # paste into ESPhome node config after "OTA" binary_sensor: - platform: gpio on_press: then: - switch.toggle: button_1 pin: number: GPIO0 mode: INPUT_PULLUP inverted: True name: "Sonoff 4CH Button 1" - platform: gpio on_press: then: - switch.toggle: button_2 pin: number: GPIO9 mode: INPUT_PULLUP inverted: True name: "Sonoff 4CH Button 2" - platform: gpio on_press: then: - switch.toggle: button_3 pin: number: GPIO10 mode: INPUT_PULLUP inverted: True name: "Sonoff 4CH Button 3" - platform: gpio on_press: then: - switch.toggle: button_4 pin: number: GPIO14 mode: INPUT_PULLUP inverted: True name: "Sonoff 4CH Button 4" - platform: status name: "Sonoff 4CH Status" # Change the names of your switch: - platform: gpio id: button_1 name: "Sonoff 4CH Relay 1" pin: GPIO12 - platform: gpio id: button_2 name: "Sonoff 4CH Relay 2" pin: GPIO5 - platform: gpio id: button_3 name: "Sonoff 4CH Relay 3" pin: GPIO4 - platform: gpio id: button_4 name: "Sonoff 4CH Relay 4" pin: GPIO15 output: - platform: esp8266_pwm id: blue_led pin: GPIO13 inverted: True light: - platform: monochromatic id: status_led name: "Sonoff 4CH Blue LED" output: blue_led After you finish with the code, click "validate". If all goes well, click "compile". It should download a .bin file when complete (that's the firmware).
     
    We are almost done. Next, you need to install the ESPHome flasher tool on to your computer. Once that's done, open up your Sonoff. You should see pins labeled 3v3, GND, RX, and TX. You need to get your jumper wires and usb to TTL converter. Make sure the usb converter is set to 3.3v, because 5v will fry your Sonoff. You need to solder a wire from GPIO 0 to GND (ground), this will short out GPIO 0 and out the device in flashing mode. Then, connect the jumper wires from your USB to TTL converter to the correct pins on the Sonoff board. Plug the USB adapter into your computer, and open the ESPHome flasher tool. Choose the .bin file you downloaded and click flash. It will tell you when the Sonoff is done flashing. Once completed, disconnect the wires from the board and remove the wire you soldered from GPIO 0 to ground so it doesn't start in flashing mode next time. Then put it all back together.
     
    Now, power up the Sonoff. After a few seconds, it should connect to WiFi. 
     
    The last thing to do is to go in your home Assistant configuration page, and it should have discovered your Sonoff automatically. Type your password and you are good to go! Your relay is in home assistant. 
     
    And you can still connect contact sensors. 
     
    Ugh I'm out of time I'll add to this later
  3. Informative
    MaxTheDog73 reacted to Gorgon in Getting annoyingly large WUs   
    Not much you can do these days. There are problems with a couple of servers at Temple University that were hanging systems so I believe those have been taken off-line so the selection of projects has become much more limited.
     
    I feel your pain. I have a RTX 2080 that should be getting 2+ million points per day chugging along at 1.6MPPD.
     
    It does, however, all tend to average out in the long run and over the rest of the competition they should get the bugs worked out and hopefully things will return to normal.
  4. Like
    MaxTheDog73 reacted to jakkuh_t in DIY WiFi Cam Tutorial   
    2+ Camera Setup
  5. Like
    MaxTheDog73 reacted to jakkuh_t in DIY WiFi Cam Tutorial   
    Single Camera Setup 
  6. Like
    MaxTheDog73 got a reaction from leadeater in World Community Grid - can't access stats   
    Yeah I just got an email saying that I had completed my first task, thanks for the help :)
  7. Like
    MaxTheDog73 reacted to jakkuh_t in BOINC Pentathlon 2019   
    Seems like the easiest way for most people to help out is in the Marathon.
     
    This involves downloading BOINC, selecting the "World Community Grid" project, and then selecting the sub-project "OpenZIKA".
     
    1. Download + Install BOINC (https://boinc.berkeley.edu/download.php) 
    2. Open BOINC and click "Add Project"
    3. Select the "World Community Grid" project, and then click on their website url. (https://www.worldcommunitygrid.org/discover.action)
    4. On their Website, click "Join Now" at the top left or right depending. Enter your information and Register.
    5. Once presented with the Sub project selection, choose "OpenZIKA" and click next. It will download a program, but you don't need it.
     
    6. Go back to the BOINC app and click "Next >". Login with the World Community Grid account that you just signed up for.
     
    Your BOINC app will now benchmark your system, and then start running. 
     
    BUT, you still need to set your team to the LTT forum one.
     
    7. Navigate to the team selection page, and login if you aren't already (https://www.worldcommunitygrid.org/ms/team/viewMyTeam.do)
    8. Type in "LinusTechTips" in the "Contains:" field.
    9. Click on the "LinusTechTips_Team" result that shows up. Once the page loads click "Join Team".
     
    You will now be BOINCing for the LTT team
     
    This is the easiest way to help out the cause, but there are more beneficial / advanced ways to do so if you're interested. Refer to the OP for more information.
     
    Message @Ben Quigley if you need assistance.
  8. Informative
    MaxTheDog73 reacted to porina in World Community Grid - can't access stats   
    I see same. Maybe servers are overloaded with the pentathlon going on.
  9. Informative
    MaxTheDog73 reacted to Gorgon in I'm new to fah are these results decent for the hardware?   
    You also have to remember that others who may be reporting results may not be using the same number of threads. I'm assuming that it is not using all the threads as you are also GPU folding with a 1060 3GB which, under windows, will require a thread to keep it fed.
  10. Informative
    MaxTheDog73 reacted to Gorgon in I'm new to fah are these results decent for the hardware?   
    Depends on the CPU. I'm currently running:
    14137 on 6/8 threads on a Xeon e31231v3 11:37
    14055 on a 4 threads on a M-5Y10c 24:33
    9037 on 4 threads of a i3-6100U 3:11
    14113 on 4 threads of a i5-3337U 19:53
    14132 on 2 threads of a i7-7567U 13:23
    9020 on a Chromebook - no TPF listed in the NaCl client but It tells me I'm getting 1800PPD 8-)
  11. Like
    MaxTheDog73 got a reaction from Gorgon in I'm new to fah are these results decent for the hardware?   
    I have pushed it to 2000MHz on the core since and its still at 70°C. (370kPPD)
    Fan profile v
     
  12. Informative
    MaxTheDog73 reacted to Gorgon in I'm new to fah are these results decent for the hardware?   
    Id give it a graphics clock offset first. Start with about +50, wait 10 minutes or so to check thermals then try another +10 or so. I can run my 1060s at 2050 and 2012 without crashing so you have some clock headroom left but it depends on the lottery. +75 should be safe but anything above that your risking crashes
  13. Agree
    MaxTheDog73 reacted to TVwazhere in I'm new to fah are these results decent for the hardware?   
    50% fan speed is fine, there's diminishing returns once you start getting super fast fan speeds so it'as not likely you'd see significant temp differences (my definition of significant being about 15ºC)
  14. Funny
    MaxTheDog73 got a reaction from Gorgon in I'm new to fah are these results decent for the hardware?   
    I do have it in my bedroom but only around 50% fans and 70°C. I do often put music on and use headphones quite often when gaming so I never hear more than a hum. I understand its an endurance thing but I think I'm only going to fold during winter because its really nice having some extra heat in a victorian house with single glazed windows and only around 15°C during winter. 
  15. Agree
    MaxTheDog73 reacted to Gorgon in I'm new to fah are these results decent for the hardware?   
    Much better. That’s a really good PPD on the GPU. How are the temperatures?
  16. Agree
    MaxTheDog73 reacted to Opencircuit74 in Can't get folding@home idle mode to work   
    Good that it got sorted out.
  17. Like
    MaxTheDog73 reacted to Opencircuit74 in Can't get folding@home idle mode to work   
    Try to look at the usage using MSI afterburner. Task manager works most of the time, but is pretty garbage if it doesn't know what specific process is running.
×