Видео

Thanks for the comment mate, point taken!

Hi, you can find the virtual ID of each device from the Tuya App itself (on your phone). Navigate to Device Information from within the app. You can check timestamp 16:34 of the video to see the step.

@@TheHomeAutomationProjectthank you

Nopes, mine is working fine. Can you provide the exact steps you have followed and which step you are getting the error?

@@TheHomeAutomationProject thank you so much for getting back to me! Basically, I installed tuya ble from your link, put the client ID and secret from the developer account and then the login details from my Tuya app account. After many reboots and switching off the Bluetooth from the device where I have the app, I am still stuck with the message “device is not registered in the tuya cloud”. I know you mention on the video that is should happen on the first try, but I must be trying for days now. Thank you once again

If you are using Go2Rtc then you need to use the advanced config file I have provided. You need to set up re-stream from rtsp via go2rtc in the config of Frigate.

Refer this link docs.frigate.video/guides/configuring_go2rtc/ There are some great troubleshooting steps mentioned in there.

Hey, no worries can you paste the full error from the log? Also you can try installing VLC player and hitting the URL stream directly to see if the camera stream is reachable.

@@TheHomeAutomationProject Thanks for the reply, I sort of have doorbell working now with the delay on the conditional card but the shortcut play button could also do with a delay. As with my other Eufy cameras, I discovered that if you disable then re-enable RTSP with camera turned off, it works, so I will try to automate that.

you are perfectly right mate, its a pain with this one!

Thanks for the sub! Welcome to the community :)

Absolutely, it does take almost 75% CPU power away from the host machine. I am planning to publish a follow up video soon with a h/w upgrade for Frigate and will demonstrate the coral TPU performance as well. The detections are really fast with it!

@@TheHomeAutomationProject Fantastic thank you!

Thanks and welcome aboard! Thrilled to be part of the community!!

Unfortunately, yes

@@TheHomeAutomationProject so I actually was able to get it to work without the base, but the camera tends to go unavailable a lot.

Ok I was aware some specific Eufy cams and some versions do work without the Homebase too, but mine didn't. Good to know!

Yes that is a common issue with the doorbell since it is hardwired to only stream for few sec / min at a time and is not like your normal camera which can stream 24/7. Hence, as a doorbell the best way to integrate is to start viewing only when motion detection happens as per the automations I have shown. If you want longer or continuous streaming then you will have to add a different camera (it can be non-eufy) and use Frigate NVR for that. I have that setup and when my doorbell detects the person or is ringing I trigger the overhead camera and record for longer duration.

Sure would be happy to cover Zigbee. Can you elaborate what you mean by non-standard? Zigbee is pretty standard and behaves quite uniformly in HA. Do you mean differences across versions, say 1.0 and 3.0?

Thanks mate! Eufy doorbell actually has a very good "human" recognition on it and I have relied on it without any false positives till date. But none of the EUFY cams support "facial" recognition. I would recommend Frigate to do the facial recognition but it is really cpu intensive and you would need proper hardware to be able to do it, specifically a Coral TPU is recommended if you want really fast recognition. If you ask me for vast majority of use cases detecting a "person" vs other objects is good enough for most home security and automations, so unless you have a very specific use case I would not recommend going down the route of facial recognition. Re the video, I have a series planned on the hardware upgrade and subsequent Frigate tuning to set up the base h/w to be able to reliably use facial recognition. Those will be published over the next few weeks.

@@TheHomeAutomationProject

@@TheHomeAutomationProject Once again thank you for taking the time to answer me. I spotted a sensor in Eufy-security-ws called "sensor.doorbell_person_name", and I would like to be able to use it in a home assistant automation to trigger actions related to the person detected by Eufy. in my configuration, I cannot understand how this sensor is informed. I perhaps naively thought that it displayed the name of the person recognized in the Eufy application (Edge AI Service). Would you have any information to give me about this sensor "sensor.doorbell_person_name" and its use? Thank you for your feedback

Ahh, that name thing only works with Homebase3 and is not perfect at the moment. Apparently due to the speed of "human" detection the AI on the homebase is not able to correctly identify the name of the person before it notifies and hence you will probably see the value as "unknown". But the speed at which AI is improving, I would say wait for a few months and you might see it working reliably (assuming you upgrade to Homebase 3). Reading some comments apparently you can get it to work on Homebase 3 by switching to "Most Efficiency"option for now. I can't test it since I have Eufy HB2 only. If you have HB3 and want to try it, here is the link to the name setup page in Eufy App: support.eufy.com/s/article/How-to-add-a-face-profile-to-Smart-Detection-of-S330-S300-eufyCam-System.

Yups, but you still need the LAN to be up and assign static IP addresses. In my setup I have a second router assigning the IP addresses whereas the main router which has the fiber coming in creates the VLANs, so mine is a bit more complex setup. But it definitely works without Internet.

Forgot to mention, you need to setup manual DNS server (I use OpenDNS servers) and manual IP address range under WAN settings to ensure it works even when internet is not operational.

@@TheHomeAutomationProject Can you explain this further ?

Sure, will try :) I am assuming you have WIFI router in which you plug in the cable from the ISP which provides the internet and then supply wifi to your devices n the house from this router. Generally the router setup is automatic which defaults the DHCP to automatic and DNS servers to default ISP server IP addresses and a default IP address for each of your devices. Example 192.168.0.1 can be your router's IP and 192.168.0.10 can be say home assistant, etc. What you would need to do is: 1) change the automatic DHCP to "manual" and add 2 DNS servers (example google DNS or OpenDNS) 2) Assign a static IP to your router, example 192.168.0.1 and 3) select an IP address range manually, example from 192.168.0.1 to 192.168.0.100. Then this sets your LAN up with the router as the DHCP server and will work even when Internet is down. Here is the link on doing this in Asus router (this is the one I have): www.asus.com/au/support/faq/1011703/. You can find similar for your router as well. One note: you may need to connect to your router via a LAN cable from your laptop or desktop to configure this (especially when changing the IP address), but once done can connect to it wirelessly. Hope this helps.

Thanks! you can try the solution mentioned here: community.home-assistant.io/t/error-28841105-no-permissions-on-local-tuya/498187

Thanks for your reply. Unfortunately I have that box checked and I am using the same data server regions. The permission issue also shows up if I try to add devices to Local Tuya without using the cloud. When I do a device query in IOT Developer the json says permission denied also. Interestingly the devices are unsubscribed even though when I subscribe to IOT Core is says "subscribed successfully". Any other ideas?

Well I have these services subscribed as well, not sure if that can help: Smart Home Basic service and Authorization token management. Also, which device is it? Could be an issue with a specific device too, though unlikely.

I am assuming you have done the step of Link app account. When you click on "Manage devices" it should show the devices as "Linked". If not you can manually link a device and test.

I had this also but to get it work I had to select a lower protocol version (3.3) in the under local key because my device wouldn't support 3.4

Thanks! Ok so this is one of the most common errors encountered and is a bit hard to debug. There are 2 things that can be happening: have you created a separate account and are not using that account on the EUFY app itself (should be logged out)? Second is that for some reason when the stream stops or your card is not showing on the dashboard, the p2p stream in the background is continuing to run. I hope you have added all the automations I have mentioned in the video including the "delay" to start and the "stop" automation as well when the card is hidden.

@@TheHomeAutomationProject I have created the additional account. I did have an issue with the first automation as I never got a trigger on HA and just in the Eufy app itself. I was wanting to have a live feed on the HA dashboard and not just a snippet of the last human action event.

Hey sure, if you follow the steps in the video you should definitely be able to stream as I have shown in the video. Unfortunately Eufy doorbell is a bit tricky set up and you would need to add all those automations in that I have mentioned to be able to make it work.

@@TheHomeAutomationProject I got it working. I would love to stay tuned for more features and being able to stream other Eufy cameras as well.

@@brandonhough4623 I have same issue, any clues, please

Sure, please post the details of the issue / error

Hi, most likely issue is with the RTSP url / streaming. Are you sure the pc on which you have your Home assistant has access to the URL / IP address of your cam? One way to find out is to install VLC (free software) and play RTSP stream on it (instructions / how to in the VLC user guide). Also, I found this link to test / discover your camera streams: dev.ipcamlive.com/streamtest. There seems to be a tool linked there which should give you the correct rtsp url for your camera. I would say try both of these methods.

Also found this link: www.ipcamlive.com/newcamera#howtovideodiv

@@TheHomeAutomationProject Thanks for the super promp response. I noticed that I am unable to add integration of frigate to devices & Services. I get a error "Unable to connect". The Addon logs throw this ""127.0.0.1:5001/auth", host: "127.0.0.1:5000" 2024-08-17 14:13:12.707977180 2024/08/17 19:43:12 [error] 189#189: *3141 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000" 2024-08-17 14:13:14.760201834 127.0.0.1 - - [17/Aug/2024:19:43:14 +0530] "" 400 0 "-" "-" "-""... Also i have NGINX and MQTT running in docker on another machine(Raspberry Pi5) on my home network . The mqtt broker running here is the same for home assistant too. So is it more complicated than just camera config?

@@TheHomeAutomationProject Thanks for a very prompt response. I noticed that I am unable to integrate frigate into devices and services, an error throws up "unable to connect". Secondly, I have my mqtt broker and nginx proxy running on another Raspberry pi machine in my home network (192.168.0.10). The HASS(192.168.0.12) uses this broker in its configuration setting. MQTT is running ok on HASS. Frigate.yaml has mqtt broker configured with the broker(192.168.0.10). Log of frigate addon ( [error] 188#188: *328 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"). So looks more complicated than just misconfiguredd camera. ANy help will be as much appriciated.

Right, so this can be an issue for the specific Frigate version. Example this bug: github.com/blakeblackshear/frigate/discussions/11569 When it comes to running Frigate on its own docker container and MQTT inside HASS, it is a bit tricky always, even when you have connected successfully. Best option is to run MQTT server in its own container and connect to both HA and Frigate using the config settings. Let me know if any of this helps. I am assuming you have tried to ping the HA IP from within your Frigate container and vice versa and there is no firewall issue at play here.

Thanks! Definitely will be coming soon.

Hi, thanks. Have you an idea when it will be comi g.? Thdre is no more expert studying face recognition using homme assidtant and eufy. Aniway you are very clever and you explain so well. We are wainting for you next video about it and be sure we are numerous to congratulate you and your stunning works👍

Hey this looks like more of a network issue and it is possible that your router's firewall is blocking traffic from and to the devices. Can you check the IP addresses of the Eufy devices and that of your Home assistant - specifically the subnet (192.168.x) bit if it is same or different. If different you may have to log into your router and search for an option called "LAN access" and enable traffic across the two networks. Hope this helps.

Hey thanks! Yes it is absolutely free, you can keep extending the account with no charge. Regarding the automatic config there are many helpful videos on YT, also, that is the default config steps mentioned in the documentation of the github page: github.com/rospogrigio/localtuya which might be a good starting point. In my video you can find the step where you can check all the IDs and keys for each attribute of a device in the Tuya cloud. If there is any specific error you are facing, post it here and I can help.

To set up the consumption values you need to open your tuya mobile app or smart life app and check the consumption values, then select a value closest to the one in the drop down. This link explains it at the bottom: smarthomecircle.com/how-to-setup-local-tuya-in-home-assistant.

Hello, yes unfortunately a Homebase is required for this integration to work :(

Payment is not an option ;) but would gladly take likes and subscribes :D Please join my discord server with the below link and share the exact error. Let's see if I can help resolve your issue. discord.gg/sWkqzm3k

Hey, must be an indentation issue in the frigate.yml file around line 32. Refer this as an example: community.render.com/t/yaml-is-saying-did-not-find-expected-key-what-am-i-missing/4401

Thanks! Ha ha, nothing mate just sharing some knowledge!

Glad it helped!

Thanks a lot for the encouraging words and the handy tips!

You're welcome! I'm glad you found the tips helpful. If you ever want to chat more about how to boost your channel’s reach, feel free to reach out. I'd love to help you optimize your SEO and thumbnails to get your amazing content the audience it deserves. Keep up the great work!

Unfortunately no. Frigate needs a 24/7 camera live stream to analyse the footage for tracking / detection but Ring cameras do not support 24/7 streaming capability.

Thank you! Keep the videos coming, they have been great!

Oops, thanks for the feedback mate. I have now added a link to download the yaml files.

Trying to improve in the upcoming videos, appreciate the feedback!