Antoine Gaudreau Simard

Thanks for the quick and insightful response! I am running 1.7.0 (cloned the repo recently, using master). Scan does confirm it is a 3.3 device. The monitoring loop does return...

Also encountering this, it seems most editing does not actually persist, like unchecking a dps does not remove it, and changing the csv for dps, while the csv persists, does...

I am also trying to generate a schema with the `$id` field (for [SchemaStore](https://github.com/SchemaStore/schemastore)). Does anyone have a workaround? (Other than inserting the line after running this crate).

Thanks for all the info! I am closing the Issue since I am finding very little time to work on this so there's no point polluting the Issues' list.

I've created a copy of the repo (with a credit section for the author here in the README) and will be maintaining it, PRs are welcomed: https://github.com/AntoineGS/TeamsStatusV2 I will work...

Yeah I will review the camera monitoring and see about adding it. Right now I am working through the issues with running it as a service though my next block...

After reading up on the other conversations it makes sense that this would fix it, since it was the %appdata% that was yielding the inccorect path. Thanks for the pointer!

Alright I think I've got the camera working fairly well, it's not ideal since it does not seem to generate a log entry when it comes on/goes off so another...

FYI I released a rewrite in Rust that uses their WebSockets API, it connects to HA and MQTT: https://github.com/AntoineGS/teams-status-rs

I have posted an updated version of this project here before but I have a new application that handles the new Teams using the WebSockets API. Their API does not...