I have a question regarding the openDoor1 and openDoor2 channels: I use them with autoupdate=“false” and added them to the sitemap with a switch, which is using a mapping. The result is a single button in the sitemap. I use this method for many other channels. But in the left of the doorbird channels the switch’s state is shown. Is it possible to hide the state?
This is the model A1081? If so, it’s currently not supported. However, it looks like it might use the same API as the video doorbells. You might want to try adding a D210x thing, then trying to operate the doors using the openDoor1 and openDoor2 channels. Let me know if that works.
Is the D205 functionally equivalent to the D101?
I’ll add these to my list of things to do. I’m currently focused on getting the binding through the review process and into the distribution. Once that wraps up, I’ll see about adding the D205 and Controller.
After a false start in which I thought the DoorBird was DoA but actually turned out to be because I’d plugged it into the non-PoE switch instead of the PoE switch I’ve got it up and running on the bench. However, the doorbell and motion channels are greyed out and don’t provide the option to attach an item to them:
Is this expected? I’ve enabled debug logging to a separate file and can see entries added to the log when I press the doorbell.
I created a second user as you suggested and enabled all permissions for it. I was a bit surprised that you can’t select the username and password, you just have to accept the username and the password it autogenerates for you every time you tap the “change password” button. Not a big deal though.
Hmm. I’ve not seen that before. In the version you’re running, the doorbell and motion channels are defined as triggers, with profiles that provide the Switch ON/OFF functionality. It’s possible that defining items based on profiles doesn’t work in PaperUI. Can you confirm that you’re using PaperUI to link the channels to items?