![]() I’m trying to move over from the HACS version of motion eye integration to the one native one inside the integrations panel. I’m probably a good example of the kind of guy that the binary sensors that come with the custom integration really help out…but I can learn I visited the page in your link(to your Github) prior to posting and looked at the devices(in my install) and their associated entities with your default integration(a few handy switches).ĭoes the current non custom integration have for example “motioneye.motion_detected” occur in the event bus or is that only in the custom integration? An example of how to do this (for either the default, or custom versions) can be found here: GitHub - dermotduffy/hass-motioneye: motionEye Home Assistant Component Motion automations may also be triggered by listening for the events that the integration generates. With the non-custom version of the integration, this is a few switches. … this will show you the list of what’s available. You can see the entities that your motionEye integration supports by going: Home Assistant -> Configuration -> Integrations -> (Click the ' devices') link -> (Choose a device) The codereview process is slow, so this is taking quite a while. All functionality is being migrated from the custom version, to the Core version – then the custom version will be retired. The integration that is part of Home Assistant Core (not the custom HACS version) has more limited functionality, but comes out of the box. Integration: Code that allows Home Assistant to talk to a huge array of devices/systems (including to those running as addons). Add the content-id to events to allow stored media to be played/cast as it arrives ( #49) Add raw media URL to events ( #48) Add binary sensor entities for motion and file storage events ( #44) Add sensor that shows configured actions ( #41) Make a common base class for all motionEye entities ( #42) Bump codecov/codecov-action from 1 to 1.5.0 ( #47) Bump black from 21.5b0 to 21.5b1 in /.github/workflows ( #46) Bump flake8 from 3.9.1 to 3.9.2 in /.github/workflows ( #45) An easy way to run a totally different system/binary/server on Home Assistant OS.Please file an issue against the custom component if that doesn’t work for your add-on configuration, so I can experiment and improve the documentation. I also got the integration working with the motionEye add-on fairly easily – see section in documentation. New release has some new features below – the most exciting being media content-id included in file storage events: Cast your motionEye media as they’re created! View saved movies/images straight from the Home Assistant Media Browser.Custom services to set camera overlay text, to trigger motionEye snapshots, and to perform arbitrary configured motionEye Action Buttons.Camera motion detection events, and file (image or movie) storage events propagate into HA events which can be used in automations.Control major motionEye camera options as HA switch entities.View motionEye MJPEG video streams as HA camera entities with no additional configuration.Dynamic motionEye camera addition/removal.It will take quite a while for the full functionality to get through the Home Assistant codereview process, but in the meantime I wanted to announce the custom component and get some feedback. This is the first part of a move of motionEye functionality from a new “full-featured” custom component into Core. You may have noticed there’s now a motionEye integration in the new release, that allows automated motionEye camera discovery and streaming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |