mgriffin13

To give more context here, this is the error I get when trying to use `/dev/usb/hiddev8` ``` 2019-11-09 21:24:00 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.wyzesense 2019-11-09 21:24:00 DEBUG (SyncWorker_4) [custom_components.wyzesense.binary_sensor]...

@gitaroomaan Can you give some more details on which Docker version you're running. Until the native Synology version is working, I think I'll need to use the rPi/MQTT configuration.

A big motivating factor to moving to Synology was so that I didn't have to run a separate rPi. The other alternative would be to somehow update the library to...

I gave up and bought another mini pc and moved my HA installation to the mini-pc. everything working great there. You can continue to use the Synology for your database...

Thinking about it a little more, it seems to me that the appropriate path forward would be to update this component to a top-level integration, instead of just a binary_sensor...

nope, see the discussion at https://github.com/kevinvincent/ha-wyzesense/issues/21

If/when this gets published upstream, make sure to note that the wyze dongle requires `hidraw` drivers. There are some platforms (like synology) that only have `hiddev` drivers, and no `hidraw`...

I am experiencing the same behavior. We are using Terraform Enterprise, so importing the resource becomes much more challenging for us. Would it be possible for TF to just delete/create...

After some more testing, I think that setting the **Default branch protection** to `Not protected` might be a suitable workaround. If TF is creating the Gitlab project and immediately also...

> Only other alternative is to accept potentially unwanted defaults on main branch for maintainers and above to be able to push and merge. Or simply not maintaining main branch...