Species Identification

[servebeer]

Ever since Ubiquity updated Protect to version UniFi OS 3.1.16, Frigate has quite identifying bird species. It still identifies ~50 "birds" a day, but it doesn't identify the actual species like it used to. I am not seeing any errors that would indicate way.

v/r
Jon

[yayitazale]

Ever since Ubiquity updated Protect to version UniFi OS 3.1.16, Frigate has quite identifying bird species. It still identifies ~50 "birds" a day, but it doesn't identify the actual species like it used to. I am not seeing any errors that would indicate way.

v/r Jon

Do you see something in the logs? Maybe is related to this and you just have to lower the threshold setting

[servebeer]

The only error I am seeing is: WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. I will adjust the threshold setting and see if that makes a difference.

[servebeer]

I dropped the threshold down to 0.1 and I am still not getting any results.

[yayitazale]

It look like it is not connected to your frigate instance. Check if you have the configuration file correctly set up and also check the configuration of the cameras in the config file of frigate is you have enables the mqtt as it is described in the docs.

[servebeer]

I am pretty sure that everything is configured correctly. I went back and looked at the config documentation, and made sure that mine matched:
config.yml

frigate:
frigate_url: http://192.168.100.69:5000
mqtt_server: 192.168.100.69:9001
mqtt_auth: false
main_topic: frigate
camera:
- birdcam
object: bird
classification:
model: model.tflite
threshold: 0.5
webui:
port: 7766
host: 0.0.0.0

I have checked that all of the IP addresses and port numbers in the config resolve correctly. As far as the camera config goes, I am using Ubiquity UniFi G3 Instants. Here is the camera config portion of the Frigate config.yml file:

frigate:
frigate_url: http://192.168.100.69:5000
mqtt_server: 192.168.100.69:9001
mqtt_auth: false
main_topic: frigate
camera:
- birdcam
object: bird
classification:
model: model.tflite
threshold: 0.5
webui:
port: 7766
host: 0.0.0.0

This setup worked for the past couple of months, and nothing changed except Ubiquity pushing an update to the camera app (UniFi Protect). I am not sure if firmware updates for the cameras accompanied this update or not.

[yayitazale]

Try without the port in the mqtt server Joseba Egia Larrinaga

…

-------- Mensaje original -------- El 6 dic 2023, 14:36, Jon escribió:

I am pretty sure that everything is configured correctly. I went back and looked at the config documentation, and made sure that mine matched: config.yml frigate: frigate_url: http://192.168.100.69:5000 mqtt_server: 192.168.100.69:9001 mqtt_auth: false main_topic: frigate camera: - birdcam object: bird classification: model: model.tflite threshold: 0.5 webui: port: 7766 host: 0.0.0.0 I have checked that all of the IP addresses and port numbers in the config resolve correctly. As far as the camera config goes, I am using Ubiquity UniFi G3 Instants. Here is the camera config portion of the Frigate config.yml file: frigate: frigate_url: http://192.168.100.69:5000 mqtt_server: 192.168.100.69:9001 mqtt_auth: false main_topic: frigate camera: - birdcam object: bird classification: model: model.tflite threshold: 0.5 webui: port: 7766 host: 0.0.0.0 This setup worked for the past couple of months, and nothing changed except Ubiquity pushing an update to the camera app (UniFi Protect). I am not sure if firmware updates for the cameras accompanied this update or not. — Reply to this email directly, [view it on GitHub](#40 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABRJ3AIYM26VERZV3C7A3PDYIBYGHAVCNFSM6AAAAABAABNPBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSHEYDEMZTGY). You are receiving this because you commented.Message ID: ***@***.***>

[servebeer]

Try without the port in the mqtt server Joseba Egia Larrinaga Enviado desde Proton Mail móvil

That appears to have the problem. Removing the port number from the mqtt line appears to have fixed the issue!