Just a quick update on my progress migrating from MotionEye to Frigate for my IP camera motion detection / camera feeds. Setting up Frigate was super easy. I had it processing the camera feeds and detecting people in just a few minutes offloading all of the heavy ML pieces to the Google Coral USB. The bit that I've just spent a couple of hours toying with is changing my Home Assistant Lovelace dashboards over to using the Frigate camera feeds. Setting it all up was easy, installed the Frigate HA integration which created all of the HA devices etc, updated my Lovelace cards to show the camera feeds and it all appeared to work. The bit I'm pulling my hair out over at the moment is that the live camera feeds really lag on my phone and PC (phone connected via WiFi, PC on a wired LAN connection). My gut feel atm is that it's because of the image sizes (2 of my cameras are 2k resolution) so I'm going to see if there's a way to downscale them for the dashboards. I'll ...
The first time I experimented with home automation was back in the late 80s when I used a simple reed switch connected to a joystick port on a Commodore Amiga 500 to create a basic alarm for my bedroom door. Since then things have moved on and my current setup is powered by Home Assistant controlling smart lighting (mostly Philips Hue) and includes features such as presence detection, voice notifications, CCTV with motion detection and a bunch of other stuff. I've started this blog to share some of my experiments and learnings in the hope that it helps and inspires others.
I've recently moved from fixed trigger times for certain (mostly lighting) events to user-configurable. This provides me an easy way to configure via a Home Assistant dashboard. This is achieved by the use of some helpers and a simple node-red subflow: The subflow code can be downloaded here for import into your node-red instance. The subflow outputs one of the following values: Morning Day Evening Night Unknown (if no matching timeframe is found) Based on matching the helper values in a cascade of time_range nodes in the subflow. To use it you'll need to create "time" helpers with the following entity ids: input_datetime.morning_start input_datetime.morning_end input_datetime.day_start input_datetime.day_end input_datetime.evening_start input_datetime.evening_end input_datetime.night_start input_datetime.night_end which can then be added to a dashboard for easy editing.
Comments
Post a Comment