I will definitely have to try this out. I have a couple of those PCIe tensor processing units working with Frigate, so paired with OH would be an ideal case. (Hoping to avoid home assistant with its Frigate integration)
This 2x
I am testing a single esp cam and frigate hehe
I have just released a build against 5.0.0-SNAPSHOT. I couldnāt get it to build against 5.0.0.M1 for some reason. However, do note it is an untested build as I do not (yet) have a running OH 5 system to test with. Please report bugs in the normal way but unless trivial I may not be able to fix them until I do have am OH5 system to test against.
Heh Iām on the M1 myself
Iāll wait and provide feedback when you have time to sort it! Looking forward to it ![]()
I donāt think it will ever build against M1. I tried again building against a ācleanā M1 tree, but get dependency errors that do not seem to be related to my code; these do not appear when building against the head (snapshot) of the OH addons tree and thus I donāt intend to spend further time trying to debug it. However, thereās a very good chance that the 5.0.0-SNAPSHOT build of frigatesvr will work with M1 - why not give it a try?
Fair enough
Iāll try that later today or tomorrow.
Btw would this binding be an alternative to sending notifications related to detections for example? I was planning on starting to study the mqtt possibilities but perhaps this could be a shortcut?
@jgow Iām trying the binding with latest version of Frigate and 4 cameras in Openhab 4.3.5 and so far so good but I noticed some things that are not working as expected.
FPS channels for cameras are always NULL (both MQTT and API request give correct values).
When you restart Frigate it seems that the binding is receiving and old snapshot (not the last one) in āLast snapshotā channel.
Iāll let you know if I find something else. Thanks a lot for your work!
Thanks for the report - such reports are always helpful! Iāll have a look shortly. Are you using a version of the binding built from the source tree, or one of the releases?
You could use the binding to provide input to a rule that sends notifications - the binding itself doesnāt have a mechanism to send notifications. You could have a rule watch for changes in one or more of the channels and make a decision to send a message based on this?
Thanks for the report - such reports are always helpful! Iāll have a look shortly. Are you using a version of the binding built from the source tree, or one of the releases?
[quote=ājgow, post:89, topic:148311, full:trueā] You could have a rule watch for changes in one or more of the channels and make a decision to send a message based on this?
[/quote]
Exactly what I was thinking, for example, is there a channel for ādetected = yes/noā? Or one for what was detected like ādogā āhumanā etc?
What I may be trying to say, is that we could use a description of what channels you have available ![]()
Try the v2.1 I have just released - this should fix the camera stats channels (including FPS) not being updated. Let me know if it works. I will look at the snapshot issue later.
They are in the documentation on the github page, and these map directly to the Frigate event messages in the Frigate documentation.
@jgow Iām using 2.0 release for 4.3. Can you please share 2.1 for 4.3, please?
I have just released v2.1 for 4.3.0 with the fixes backported - this should work for you.
@jgow FPS reading is now correct. I think the last snapshot channel is still receiving an old image when the server restarts. Thanks a lot for your work.
@jgow another little problem. Sometimes (not every time) when the server binding goes offline and immediately online (I think it happens after an HTTP timeout) the cams things stay offline and I have to manually put them back online.
Thanks for this, it looks awesome.
Would it be possible to have it included in the Add-On Store?
Itās a simple matter of creating a properly formatted message in the expected location, as detailed here: Announcing the Community Marketplace
Done! Thanks for reminding me
. Version 2.2 should now be available through the Marketplace - hopefully I have got the submission correct. Do let me know if there are any issues accessing it.
Interesting. I havenāt been able to forcibly trigger this behaviour. Can you let me know under what circumstances it is occurring?