jolka
6 Styczeń 2021 12:41
3
Cześć, ja mam i polecam bardzo z całego
sprzęt już mamy, ale cały projekt easy to więcej niż tylko sprzęt cała architektura łączenia i działania będzie troszkę inna dlatego trochę to jeszcze potrwa, AIS Easy to jest plan na 2021
implementujemy i testujemy takie coś teraz
Czy można postawić AIS na jakimś swoim PC ?
Można tu są kody i opis: GitHub - sviete/AIS-home-assistant: ☀ Awaken your home 🇵🇱
Nam to zajeło 4 lata
Do obsługi 6 kamer IP bo obawiam się ze DEV2 też nie pociągnie strumienia rtsp
6 kamer przesyłających na żywo obraz w tym samym czasie, nie pociągnie Ci PC z i7
cała koncepcja polega na tym żeby jednocześnie wysyłać obraz z 1 kamery - obsługiwać tylko jeden strem
w ten sposób możesz mieć więcej kamer na DEV2 (a już na 100% 5 bo tyle my mamy )
czyli wykrywasz ruch, albo ktoś dzwoni do drzwi, to wtedy robisz zdjęcie czy nagrywasz, albo jak klikasz w podgląd wybranej kamery to wtedy z niej oglądasz filmik
We wszystkich nowych systemach to kamera jest inteligentna i nie wysyła cały czas wideo do urządzenia tylko sama wykrywa ruch (lub nawet obiekty).
Niedługo kamerka na ESP32 będzie wykrywała ludzi:
Faktycznie ta kamera ESP ma potencjał
Okazuje się, że na ESP32 można już korzystać z biblioteki TensorFlow Lite. Czyli można dodać małe modele ML i np. wykrywać ludzi z kamery na ESP32.
Jeszcze jakiś czas temu wszyscy myśleli, że TF na czymś takim jak ESP32 to jest nie możliwe!
Tu jest gotowy przykład dla Arduino
Myślę, że to już tylko kwestia czasu i PIR będzie tylko uruchamiał wykrywanie człowieka kamerą w AIS-Tasmota
Powinmo być tak:
PIR -> ESP3…
Jeżeli chodzi o takie zastosowania jak 6 kamer to w drodze jest AIS PRO.
Dodatkowo pracujemy nad dodaniem integracji z AIS do HA.
Mamy nadzieję, że niedługo każdy postawi sobie co chce, na czym chce oczywiście, połączy się z AIS
Może mając wybór więcej ludzi zrozumie, że sprzęt od AIS to najlepsza opcja jeżeli chodzi o stosunek ceny do możliwości.
home-assistant:dev
← asystentka-jolka:ai_speaker_integraion
opened 10:59PM - 01 Jan 21 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [X] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example entry for `configuration.yaml`:
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR. Furthermore, for new integrations, it gives an impression of how
the configuration would look like.
Note: Remove this section if this PR does not have an example entry.
-->
```yaml
# the configuration is done via config flow
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [X] The code change is tested and works locally.
- [X] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] The code has been formatted using Black (`black --fast homeassistant tests`)
- [X] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [X] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [X] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [X] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [X] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [X] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [X] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
4 polubienia