Search results

@pete_c Thanks :) Here's Peanut btw:

Apologies, 1.0.3 tried to implement an alternate method of creating a pullpoint subscription (this is why unit tests are a must). Releasing 1.0.4 to address any issues above, hope that works.

@alexdelprete Unfortunately they do not transmit such a message over ONVIF.

@pete_c Thanks so much for the breakdown + schematic. Appreciate it, and will pursue this. What kind of parrot is Kika? We have a pearly conure named Peanut, just turned 8 a few days ago.

@pete_c Absolutely :) I have since removed config.dev.yaml since it had sensitive information in it, but config.sample.yml is still there for consumptions by users. I will be updating the guides section of the README in the next few days to have slightly more detail for platforms (e.g...

No, all good! I just looked through the code and it was a bug in the config validation (my bad). I didn't have the port specified in the schema, and it was getting stripped out. Releasing 1.0.1 / latest right now, but will take 20-30 minutes for Dockerhub to compile and publish it, after that...

@pete_c, Do you have a port specified under mqtt in the config? I will be updating the default configuration later today to include the sensible default for mqtt (1883). The current merge of default configuration + user configuration ends up discarding any deeply nested values.

Hi! I will include the LaView firmware on github somewhere. I don't see the harm in that unless they send over a DMCA. Great thinking, thank you! I am actually using that package to faciliate the onvif communication :) Mostly my code is a glue layer between the two protocol packages with some...

Hi all! For those using the DB1 in automation, I have published a new docker image / node package to capture ONVIF events and transmit them over MQTT. For EzViz and RCA you will have to flash it with Laview firmware to get ONVIF endpoints. The doorbell only publishes the motion detection, but...