#hubitat — Public Fediverse posts

I'm a bit of a #HomeAutomation nut, and I have two cats whose #litterbox is a #LitterRobot made by #Whisker. The mobile app is supposed to notify me whenever the litter drawer gets full, but it's never worked. (Yes, I've already tried logging out/in, uninstalling/reinstalling, clearing cache, disabling battery optimization, etc.)

My main hub is a #Hubitat C-7, and until recently, there was an unofficial Litter Robot integration in #HubitatPackageManager that allowed me to circumvent the Whisker app notification issue. Then, Whisker changed their #API, which broke the Hubitat integration, and I was back to manually checking the Whisker app every day.

Turns out, there's a #HomeAssistant integration that supports the new API, so today, I implemented the most #RubeGoldberg workaround I've ever seen. I installed #Portainer on my #RaspberryPi, spun up HA in #Docker, installed #HACS, enabled the Hubitat #MakerAPI integration, connected it all up, and now my notifications are working again!

I'm a bit of a #HomeAutomation nut, and I have two cats whose #litterbox is a #LitterRobot made by #Whisker. The mobile app is supposed to notify me whenever the litter drawer gets full, but it's never worked. (Yes, I've already tried logging out/in, uninstalling/reinstalling, clearing cache, disabling battery optimization, etc.)

My main hub is a #Hubitat C-7, and until recently, there was an unofficial Litter Robot integration in #HubitatPackageManager that allowed me to circumvent the Whisker app notification issue. Then, Whisker changed their #API, which broke the Hubitat integration, and I was back to manually checking the Whisker app every day.

Turns out, there's a #HomeAssistant integration that supports the new API, so today, I implemented the most #RubeGoldberg workaround I've ever seen. I installed #Portainer on my #RaspberryPi, spun up HA in #Docker, installed #HACS, enabled the Hubitat #MakerAPI integration, connected it all up, and now my notifications are working again!

I'm a bit of a #HomeAutomation nut, and I have two cats whose #litterbox is a #LitterRobot made by #Whisker. The mobile app is supposed to notify me whenever the litter drawer gets full, but it's never worked. (Yes, I've already tried logging out/in, uninstalling/reinstalling, clearing cache, disabling battery optimization, etc.)

My main hub is a #Hubitat C-7, and until recently, there was an unofficial Litter Robot integration in #HubitatPackageManager that allowed me to circumvent the Whisker app notification issue. Then, Whisker changed their #API, which broke the Hubitat integration, and I was back to manually checking the Whisker app every day.

Turns out, there's a #HomeAssistant integration that supports the new API, so today, I implemented the most #RubeGoldberg workaround I've ever seen. I installed #Portainer on my #RaspberryPi, spun up HA in #Docker, installed #HACS, enabled the Hubitat #MakerAPI integration, connected it all up, and now my notifications are working again!

I'm a bit of a #HomeAutomation nut, and I have two cats whose #litterbox is a #LitterRobot made by #Whisker. The mobile app is supposed to notify me whenever the litter drawer gets full, but it's never worked. (Yes, I've already tried logging out/in, uninstalling/reinstalling, clearing cache, disabling battery optimization, etc.)

My main hub is a #Hubitat C-7, and until recently, there was an unofficial Litter Robot integration in #HubitatPackageManager that allowed me to circumvent the Whisker app notification issue. Then, Whisker changed their #API, which broke the Hubitat integration, and I was back to manually checking the Whisker app every day.

Turns out, there's a #HomeAssistant integration that supports the new API, so today, I implemented the most #RubeGoldberg workaround I've ever seen. I installed #Portainer on my #RaspberryPi, spun up HA in #Docker, installed #HACS, enabled the Hubitat #MakerAPI integration, connected it all up, and now my notifications are working again!

I'm a bit of a #HomeAutomation nut, and I have two cats whose #litterbox is a #LitterRobot made by #Whisker. The mobile app is supposed to notify me whenever the litter drawer gets full, but it's never worked. (Yes, I've already tried logging out/in, uninstalling/reinstalling, clearing cache, disabling battery optimization, etc.)

My main hub is a #Hubitat C-7, and until recently, there was an unofficial Litter Robot integration in #HubitatPackageManager that allowed me to circumvent the Whisker app notification issue. Then, Whisker changed their #API, which broke the Hubitat integration, and I was back to manually checking the Whisker app every day.

Turns out, there's a #HomeAssistant integration that supports the new API, so today, I implemented the most #RubeGoldberg workaround I've ever seen. I installed #Portainer on my #RaspberryPi, spun up HA in #Docker, installed #HACS, enabled the Hubitat #MakerAPI integration, connected it all up, and now my notifications are working again!

@thomastraynor Depends on which company you choose. #Firewalla, for instance, charges enough for the product and makes it w/open source linux and other tools - guaranteeing future ability to hack it if I need to.

#Hubitat? The same.

So, yes, most companies are selling you a pricy brick. SOME good ones sell user-handle-able devices.

@serge #LitterRobot can be connected to #Hubitat, which can control other devices, such as air filters. You'd only need to add a bit of logic and a timer.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

How an Engineer Designs a DIY Energy Recovery Ventilator - We have no idea whether [Nick Goodey] is a trained engineer or not. But given the detailed design ... - https://hackaday.com/2020/10/21/how-an-engineer-designs-a-diy-energy-recovery-ventilator/ #energyrecoveryventilator #heatexchanger #greenhacks #homehacks #coroplast #arduino #hubitat #hvac #mqtt #erv