• Content count

  • Joined

  • Last visited

  • Days Won


Vettester last won the day on June 17

Vettester had the most liked content!

About Vettester

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

5,830 profile views
  1. Vettester

    Do You Miss Iris ?

    Not missing Iris at all. Hubitat has a lot more functionality and local processing, Combined with Homekit I have everything I need within a single UI.
  2. Vettester

    Marvin Ellison

    I haven't shopped at Lowe's since they announced the shut down of Iris. It appears they are going down the same path as Sears and Kmart.
  3. Vettester

    Marvin Ellison

    The saga continues...
  4. Vettester

    Six weeks with Hubitat

    You can also quickly access your first 9 favorites and scenes through Apple's Control Center and Homekit adds additional automation functionality. Win win for WAF!
  5. Vettester

    Six weeks with Hubitat

    You're welcome, I'm glad you got it working. I think you're going to like it. In my opinion it's a much better interface than the Hubitat dashboard app.
  6. Vettester

    Six weeks with Hubitat

    Excluding the temperature for your contact sensors should be fairly simple. First within the home app open the device you want to exclude and go into settings. Scroll down to the bottom of the settings and you'll see a device serial number. Add this device number to the "excluded_attributes" section of your config.json file of the homebridge instance that contains the device along with the attribute you want to exclude. From the example above your config.json file should look something like this: { "bridge": { "name": "Homebridge@2", "username": "AB:22:3D:E2:CE:32", "port": 51827, "pin": "033-44-255" }, "accessories": [], "platforms": [ { "name": "Config", "port": 8081, "auth": "form", "theme": "teal", "temp": "/sys/class/thermal/thermal_zone0/temp", "tempUnits": "f", "sudo": true, "standalone": true, "restart": "sudo -n systemctl restart homebridge@2", "log": { "method": "systemd", "service": "homebridge@2" }, "platform": "config" }, { "platform": "Hubitat-MakerAPI", "name": "HomeBridge2", "app_url": "", "access_token": "9c2198be-89e6-48b2-ab21-7cfd725e7dde", "polling_seconds": 300, "temperature_unit": "F", "mode_switches": false, "hsm": false, "excluded_capabilities": {}, "excluded_attributes": { "456": [ "temperature" ] } } ] } Save the file then restart the homebridge instance and the temperature button for that device should be removed.
  7. Vettester

    Six weeks with Hubitat

    You can disable the HSM and Modes in your second instance by modifying the config.json file. Under the Hubitat-MakerAPI Platform section modify the following lines from true to false: "mode_switches": false, "hsm": false, Just keep in mind that you need to restart homebridge whenever you modify the cong.json file before the changes will take affect. You can also hide the temperature attributes by device. You just need to add the device id and the attribute you want to exclude to the "excluded_attributes" section of your config.json file. Here's one of my config.json files as an example: { "bridge": { "name": "Homebridge@1", "username": "AB:22:3D:E2:CE:31", "port": 51826, "pin": "033-44-254" }, "accessories": [], "platforms": [ { "name": "Config", "port": 8080, "auth": "form", "theme": "purple", "temp": "/sys/class/thermal/thermal_zone0/temp", "tempUnits": "f", "sudo": true, "standalone": true, "restart": "sudo -n systemctl restart homebridge@1", "log": { "method": "systemd", "service": "homebridge@1" }, "platform": "config" }, { "platform": "Hubitat-MakerAPI", "name": "HomeBridge1", "app_url": "", "access_token": "dd253efa-3be9-468b-80fd-9c7aa8ca14b9", "polling_seconds": 300, "temperature_unit": "F", "mode_switches": true, "hsm": true, "excluded_capabilities": { "169": [ "Switch" ], "706": [ "Switch" ], "707": [ "Switch" ], "708": [ "Switch" ], "709": [ "Switch" ], "710": [ "Switch" ], "711": [ "Switch" ], "712": [ "Switch" ] }, "excluded_attributes": { "33": [ "temperature" ], "34": [ "temperature" ], "37": [ "temperature" ], "38": [ "temperature" ], "39": [ "temperature" ], "40": [ "temperature" ], "42": [ "temperature" ], "43": [ "temperature" ], "45": [ "temperature" ], "46": [ "temperature" ], "47": [ "temperature" ], "50": [ "temperature" ], "55": [ "temperature" ], "57": [ "temperature" ], "59": [ "temperature" ], "61": [ "temperature" ], "62": [ "temperature" ], "67": [ "temperature" ], "69": [ "temperature" ], "72": [ "temperature" ], "76": [ "temperature" ], "77": [ "temperature" ], "78": [ "temperature" ], "79": [ "temperature" ], "86": [ "temperature" ], "87": [ "temperature" ], "105": [ "temperature" ], "106": [ "temperature" ], "141": [ "temperature" ], "142": [ "temperature" ], "143": [ "temperature" ], "144": [ "temperature" ], "149": [ "temperature" ], "150": [ "temperature" ], "151": [ "temperature" ], "169": [ "battery" ], "225": [ "contact" ], "269": [ "contact" ], "360": [ "temperature" ], "376": [ "temperature" ], "377": [ "temperature" ], "450": [ "temperature" ], "451": [ "temperature" ], "452": [ "temperature" ], "453": [ "temperature" ], "454": [ "temperature" ], "456": [ "temperature" ], "457": [ "temperature" ], "756": [ "temperature" ], "770": [ "temperature" ], "771": [ "temperature" ], "772": [ "temperature" ], "773": [ "temperature" ], "775": [ "temperature" ], "776": [ "temperature" ], "777": [ "temperature" ], "961": [ "temperature" ], "1122": [ "temperature" ] } } ] }
  8. Vettester

    Six weeks with Hubitat

    You cannot resize the buttons but you can rename them in the Home app to make them more readable. Just tap on the button and then go into settings and change the name. The button is essentially a link so changing this has no effect on the name of the device in Hubitat. Did you create a separate config.json file for each instance and save it in the correct directory (/var/lib/homebridge@1 and /var/lib/homebridge@2)? All three of my instances of homebridge are configured to start automatically. I did this by creating a systemd service. This is outlined in steps 7 and 8 of the homebridge installation guide.
  9. Vettester

    Six weeks with Hubitat

    I've only been using this for a few weeks but can tell you that it's an awesome configurable interface with more improvements to come in iOS 13. Also, the ability to use Siri is an added plus and it looks great on both an iPhone and an iPad.
  10. Vettester

    Six weeks with Hubitat

    Here you go... Install Raspian on your Raspberry Pi. Since you're new to the pi world I would recommend using NOOBS. Instructions can be found here After you've installed the OS the next thing you should install on your pi is remote desktop. This give you the ability to run the pi headless so you can put it anywhere. Even though you can enable wifi on your pi I would recommend connecting it directly to your router for reliability. You can use this as a guide to install RDP on your pi. From this point on you should be able to RDP into your pi so you can complete the rest of the steps on your computer. Add the built-in Maker API to Hubitat. To accommodate the number of devices on my system I added 3 separate instances of Maker API and named them HomeBridge1, HomeBridge2 and HomeBridge3. Install HomeBridge on your PI using this guide. Install enough instances to accommodate the number of devices you want to include. HomeBridge may create multiple instances of the same device depending on the device's capabilities/attributes so keep this in mind when you are deciding on how many instances to create. You can exclude capabilities/attributes as needed. You can always add additional instances later if needed. Install the HomeBridge MakerAPI plugin starting with step 2 at this link and setup your HomeBridge config with the appropriate app url and and access token. Add the devices you want to include in Homekit using Maker API. Keep in mind that you need to restart HomeBridge when you add or remove devices in Maker API. Add the Home app to your iOS device from the app store. Add the HomeBridge accessory to your Home app by scanning the HomeKit setup code created by HomeBridge. Adding Cameras Install the ffmpeg plugin for HomeBridge using sudo npm install -g homebridge-camera-ffmpeg Install IP camera plugin for HomeBridge using: sudo npm install -g homebridge-ip-camera Add the IP Camera platform to your HomeBridge config file. You can use this link for a reference. I put this together from memory so I might have missed something. If you get stuck or you need examples of my config files feel free to PM me. and I'll do what I can to help.
  11. Summer may have somewhat of an impact but I think the majority of the regulars on this forum have moved on to bigger and better things.
  12. Vettester

    Six weeks with Hubitat

    I think I tried just about all the different ways of doing this and through trail and error I now have a configuration that is fairly simple to maintain. Here is what I am using: Hardware Raspberry PI 3 B+ running Raspian NOOBS Setup iPad Gen 6 with Homekit enabled - A Homekit server is required for remote access. An Apple Homepod or a newer Apple TV can be used instead. Hubitat HE. Software Maker API Homebridge - I used this Guide to setup 3 instances of Homebridge. I found that there is a 147 device limit per Homebridge instance so depending on your system you may need more or less. The guide uses systemd and has a UI to simplify the system management process. Homebride Plugins: 4. Apple Home app If I get time later on I will put together a guide on the process to set this up.
  13. Vettester

    Six weeks with Hubitat

    I've figured out how to integrate Hubitat, Blue Iris and Homekit into a single app. Now with the camera integration my system has all of the functionality I had with Iris and then some.
  14. This forum is on life support and just waiting for someone to pull the plug.
  15. Vettester

    Iris Centralite / v2 range extender?

    I have almost 100 V1 devices running on Hubitat and they are all working well.