kwijibo007 wrote:
Yeah, so it looks like it's working? Did you see the device state actually change in Indigo? 11189196 translates to 0xAA 0xBB 0xCC (AABBCC). The API makes no mention of this. I will add some debugging functionality to the plugin so you can provide me the full UDP packet before decrypting and the content after decrypting (if it can decrypt it). Just to confirm, this model is a D2101V, running firmware 000112? Strange as this is the exact model/firmware that I have.
yes that's the device however both devices appear to be reporting identical information (though in a different order of events?) - and are both working fine (with the exception that motion isn't being reported [via the plugin] on the device with 000111 firmware). As you say this is actually a documented difference so no surprise on the latter issue.
I'm actually seeing 4 repeats of the unknown identifier message in the log. I've seen state changes on the motion device, I cant confirm yet with bell press.
from the 101 running 000111:
- Code: Select all
DoorBird Debug DoorBird Laneway: Unknown packet identifier (11189196)
DoorBird Debug DoorBird Laneway: Unknown packet identifier (11189196)
DoorBird Debug DoorBird Laneway: Unknown packet identifier (11189196)
DoorBird Debug DoorBird Laneway: Unknown packet identifier (11189196)
DoorBird Debug doorbird.doorbell_event() called
DoorBird DoorBird Laneway Bell: Doorbell pressed
and from the 2101 running 000112:
- Code: Select all
DoorBird Debug doorbird.doorbell_event() called
DoorBird DoorBird Front Bell: Doorbell pressed
DoorBird Debug DoorBird Front: Unknown packet identifier (11189196)
DoorBird Debug DoorBird Front: Unknown packet identifier (11189196)
DoorBird Debug DoorBird Front: Unknown packet identifier (11189196)
DoorBird Debug DoorBird Front: Unknown packet identifier (11189196)
presumably with debug logging turned off none of this would be visible anyhow...so no apparent issue for me...but if you want me to debug further happy to assist.