Indigo Domotics

Posted: **Tue Jul 31, 2018 4:23 am**

As reported here: viewtopic.php?p=164463#p164463

Some DoorBird plugins are logging (when debug is enabled ) "Unknown packet identifier (11189196)". This does not appear to affect functionality.

I'll make some changes to the plugin in a future release to allow me to better troubleshoot this kind of message.

Pete

Posted: **Tue Jul 31, 2018 5:55 am**

I have a hunch...

Given this only occurs for doorbell presses (not motion) and agame has mentioned that he's using the IP Chime, I wonder if the two are related?

I have the IP Chime still waiting to be set up in its box. I'll get to it over the next couple of days and see if I can replicate it.

Is anyone else using the IP Chime and seeing the message with debug logging turned on?

Pete

Posted: **Tue Jul 31, 2018 5:49 pm**

good detective work.
fortunate I posted a random comment on the chime!

Posted: **Tue Jul 31, 2018 8:14 pm**

lanbrown wrote:
Affirmative

Excellent! Thanks for confirming. It's looking very likely that the IP Chime is the cause. I'll set mine up tomorrow which will definitively confirm.

agame wrote:
fortunate I posted a random comment on the chime!

Seriously!

I wounder if the IP Chime is triggered by UDP broadcast too? Makes sense as multiple Chimes can be triggered by multiple Doorbirds. I wonder if we can make Indigo trigger the Chimes directly? There's probably encryption in the mix and IP filtering... but it would be nice if it worked? @agame, this might allow you trigger a different sound depending on which doorbell was pressed. I think you mentioned this in the general discussion thread?

Pete

Posted: **Tue Jul 31, 2018 9:57 pm**

Seriously!I wounder if the IP Chime is triggered by UDP broadcast too? Makes sense as multiple Chimes can be triggered by multiple Doorbirds. I wonder if we can make Indigo trigger the Chimes directly? There's probably encryption in the mix and IP filtering... but it would be nice if it worked? @agame, this might allow you trigger a different sound depending on which doorbell was pressed. I think you mentioned this in the general discussion thread

I was wondering that also! Though from what I can see I think the chime soundbite is being set on the device rather than dynamically in the notification. So what I would need to mimic is whatever message the DoorBird sends after a 'storey call': "a storey-call button can be connected to the door chime via two-wire cable and, an individual ringtone profile can be configured for this purpose".

Posted: **Tue Jul 31, 2018 10:08 pm**

lanbrown wrote:

I don't believe there is an API for the IP Chime...which is a shame.

this is what I was advised in august last year: "Our Door Chime API is still in development by our team of product specialists. It should be available by Winter 2017 but this is still subject to change."

I'm easily confused by northern hemisphere seasons being used as dates but I'm fairly sure that means its way overdue. I have a live query in to them on this topic.

(In parallel I'm trying to use this trigger to create a supplementary alert by way of a system TTS announcement sent to a HomePod via the Airfoil plugin - advising which bell has been pressed. I'm finding it unpredictably laggy though may be just me & still working on it. But thats another thread.)

Posted: **Tue Jul 31, 2018 11:36 pm**

lanbrown wrote:
So I started on a capture on my switch (the wonders of enterprise equipment) and I see TCP and UDP traffic.

Wow! Great info. So does this occur every time you press the doorbell - that being the Chime contacts the cloud? Surely the Doorbird contacts the Chime via the local network and not via the cloud? Do you see any TCP traffic going from the Doorbird to the chime?

I'll test that the chime still works when there is no internet connection tomorrow.

agame wrote:
this is what I was advised in august last year: "Our Door Chime API is still in development by our team of product specialists. It should be available by Winter 2017 but this is still subject to change."

An API would be great. I can think of many uses.

Posted: **Wed Aug 01, 2018 4:38 am**

Well we can put this one to bed...

I've set up my chime and the "Unknown packet identifier (11189196)" magically appeared. I'll filter this identifier out in the next plugin release. I'll keep the logging of unknown identiefers though as I think it's handy to capture.

I very quickly tried to dycrypt the packet but didn't get anywhere. I think we'll need to wait for the chime API to move forward.

Thanks for everyone's help in working this one out.

Pete

Posted: **Wed Aug 01, 2018 7:51 pm**

cool!
I'll post if I hear any more on the chime API

Posted: **Thu Aug 02, 2018 1:54 am**

I have a D2101V which seems to be working fine with the plug-in. Thanks for that!
I am looking forward to implementation of the RFID functionality in the API, then it should be possible to switch on the lights when coming home using an RFID tag.
Firmware 000112 btw.
Tim

Posted: **Thu Aug 02, 2018 6:20 am**

Sevilsivle wrote:
I am looking forward to implementation of the RFID functionality in the API

Yeah me too. Identifying which tag was used is a killer feature.

Pete

Posted: **Sun Aug 05, 2018 5:38 am**

Just released an update to the plugin (0.4.0) which includes a fix for this bug: https://forums.indigodomo.com/viewtopic.php?f=287&t=21090

Posted: **Fri Aug 17, 2018 4:53 pm**

there was discussion above regarding an API for the DoorBird chime. I just had a response that didn't address the API issue, but advised its now possible to configure distinct chimes from multiple intercoms.

Please take the Digital Passport of DoorBird one, go into the administration and to peripheral settings.

You should see your chimes paired with DoorBird one. In case you do not see the chimes paired, sure to get them paired.

Then click on DoorChime one in the list of peripherals, deactivate default and storey call and click on "add", chose your ringtone, repeat settings etc. and then save it. It should now be listed below "ring settings" in the same list where default and story call are listed. Then click on save again.

Now you configured DoorBird one to ring your chime.

Then save everything in the administration menu when asked and log into the administration of DoorBird two.

Click on the DoorChime and you will see that default and storey are still deactivated (because it is a global setting for this certain chime) but you are able to click add again and add this specific DoorBird two station now. Add it with a different ringtone.

In your list of "ring settings" you shoud now have:
default - off
storey - off
doorbird one (you can identify it with the name e.g. ggaaaa) - ringtone
doorbird two (you can identify it with the name e.g. ggbbbb) - another ringtone

Posted: **Sun Aug 26, 2018 4:40 am**

lanbrown wrote:
I bought a brand new DoorBird IP I/O door controller for $65 shipped. They have one left if anyone is interested. I'll see how the plugin handles that controller.

I bet a new unknown packet identifier will show up. If so I'll filter it out. I'd be interested to know how you find the controller when it arrives

Posted: **Mon Aug 27, 2018 6:09 pm**

lanbrown wrote:
With that said, I don't see the three relays that the I/O Controller adds to the overall DoorBird setup.

The plugin (wrongly) assumes that you have two relays, regardless of the actual number you have. I'll need to work with you to make this work. If you're happy to help I'll PM you with a script to run offline (within a few days)?

Pete

Indigo Domotics

Unknown packet identifier (11189196)

Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)

Re: Unknown packet identifier (11189196)