Agree with you regarding the Armed status. Due to the fact that only the motion detection can be set on a camera basis.
That is why cameras have the command SystemArm. They cannot be individually armed but I wanted to make it so someone could arm the whole system that a particular camera belongs to.
That could possibly cause problems if someone tries to arm the system from multiple cameras that all belong to the same system (the API would not be happy about getting multiple command that are basically the same right away).
Hi @snell - I've noticed a few times now that I'm unable to update the thumbnail image for a camera (XT2). I'm hitting the Get Thumbnail button in the camera device page on the hub. I also don't see anything show up in the logs. This is a BlinkChild-Camera device type
EDIT: after trying several times I did finally get an updated image. I also noticed nothing shows up in the logs unless the driver has trace debug logging enabled.. next time I'll set that first.
Anyway, I tried again with another camera and got a different thumbnail image this time - but the image is from night and it's day so it can't be just taken.
Anyway, this might not be enough to go on but I figured I'd still ask in case there's something I can try next time it happens.
I have noticed the same thing... and have not been able to solve it yet. Sometimes the new image arrives quickly and sometimes it seems like there is a delay... and does not get populated properly or the API responds with the existing URL (so thus an old thumbnail) before it has gotten the new thumbnail.
It does not help that they made it so much more irritating to get them in their own app. I wonder if they did it as a way to reduce the load on the servers... I have even gotten cases where their app failed getting a new thumbnail! Then try again later and it works just fine.
Either way, I am continuing to see if there is a "sweet spot" I can hit with delays and such.
no worries - I was just wondering if it was just me and this was the first time I tried to debug it by looking at logs.
so i just discovered my cameras haven't been arming and disarming anymore. Just finally dug in to investigate butnothing stands out.
I tried reauthorize, etc. Everything seems happy in the devices, latest version of code, etc. Just can't seem to arm/disarm.
If I arm via the app and refresh, I don't see the status update either.
Any idesa?
No errors in the logs?
I assume, from that error, that the Network does not have a "Network" field in it's State Variables. You are doing the Arm/Disarm through the network and not via the Parent or the particular cameras?
My automations arm and disarm it through the blink child device. Actually by using the on/off switch of the child device.
The network in that number is populated is the device ID for the child.
I also see it as a state variable under the parent device as well.
Now in hindsight, I think those log errors were when I was trying to use the arm button from the parent and child devices during my testing.
I just hit the arm button from the child device and have another log entry about the network ID again.
I'm not quite sure what changed because I've been using it like this for a while and haven't changed anything. Unless something changed on the blink side perhaps?.
Cannot think of anything that I changed but I will check the code. The parent needs an ID provided but child devices should provide their own ID (unless some problem occurs).
EDIT:
Ok, so it is actually the State Variable field "ID" that matters. On/Off just redirect to the Arm/Disarm System commands anyways.
What version of the drivers do you have? I am having issues even finding logging that could generate that error message...
I did try On/Off for my Network and it did work (on the Hubitat and showed the correct status in the Blink app as well)... but I did not get an error either.
Interesting. I have a state variable of ID with that same number in it under the child but not under the parent device.
Off the top of my head, I'm not sure the driver version but this morning when I was started testing before I posted here I checked your GitHub links in the first post and all of my driver's code match the same version numbers and dates as your GitHub.
Although I do see this message as a state variable on the parent device
New patch 0.5.18 available
I have blink API, child, Network, And sync module drivers installed.
Edit API, 5.18, child 0.2.3, network 0.1.1, and sync 0.1.1.
Sorry I'm working from my phone and struggling 
The "New Patch" message is probably an old one from the "Driver Status" which has been replaced with "DriverStatus". I am probably going to have to code in a method to delete the old ones...
As for the versions, they all seem correct except there is not a Camera driver?
The parent device would not have an ID since it is not a "real" device. The real devices that the API allows for are the children. Although I keep debating about killing off sync since there is not much real use in having it...
No camera driver.
Here's my devices and how they show up. If it's not right, I have no idea what happened. I really haven't changed anything in quite a while besides habitat updates and reboots every once in awhile.
I just did a modify on it via HPM and installed the camera child drivers.
In the parent device, I did a re authorize, got the pin, and reverifed it. Then did a get home screen.
Cameras have the correct driver now, but still doesn't seem to want to do anything.
Still getting the same log entries about the network
Out of curiosity, do you have anything configured for the Client Name or User Agent preferences in the parent device or are those the default "blank" values?
Both default blank..
You said you were doing the arm/disarm via the Network child, correct? You need to switch the Network child device(s) to use the BlinkChild-Network driver. The Network driver makes use of the state.ID when making Arm/Disarm calls. The generic child driver uses state.'Network ID'... but a Network child device generally will not have a 'Network ID' because it IS the network.
On a side note... I finally found where that logging error is used... Since it was not in the BlinkAPI parent driver and I thought I was going nuts. That error "Network-124046 does not know Network it belongs to, cannot request info." ONLY exists on the BlinkChild driver and the BlinkChild-Camera drivers.
I've just been following along and decided to have a look at my, always working, cameras. 
I see they are all stuck at Armed and no matter what the piston does to disable nothing happens.
Odd, no log errors and the device is Auth OK and eveything says OK.
The only thing was this today but this is usally just a random blip on your end?
dev:3272024-02-27 18:08:35.338errororg.apache.http.conn.ConnectTimeoutException: Connect to www.drdsnell.com:443 [www.drdsnell.com/192.185.41.207] failed: Read timed out on line 468 (method CheckForUpdate)
1 Like
