Is lpcal storage used?
Then check 1st post / how to use point 3.
i dont use local or cloud. i just only have the doorbell connected.
Please read the How to use in 1st post.
The app can only use recorded videos to identify a motion.
If you have a new device, you have also 1 month free cloud storage. And if you haven’t installed an USB stick at your sync module, the cloud store is used.
I know but this is nothing to do with motion i guess. Its about when you press the button and the flow starts. Fot example.
The flow is when someone press the doorbel button. Then the sonos speaker has to play dingdong.
But when i press the button it takes 30 seconds to play it. Its nog the sonos. I also tested it with lights.
A button press also only start a video recording. Anf it that’s done and the video is available, the app can start the flow trigger. It’s all about videos.
The Blink API has nothing for real motion alert or button press. The Blink app just sends push messages to your mobile phone.
It should update if a poll interval is set in account device settings.
Hi, since couple of weeks I always get kicked out of the account every other day. This prevents the System to be Disarmed. When trying to login the first attemp fails due to incorrect login data, second try always works. Any idea?
Can you please send me a diagnistics report it this happens again?
And please use the ‘API error’ flow trigger on the account device to catch the error and write it to the timeline. I hope I can see some details.
Hi, got logged out today again. Here is the diagnostics Code. Maybe you can see something. Thank you very much.
da236d74-9ed8-49eb-8d9d-19340f6a0a4b
Error storing SMB: exportVideoSmb(): Error writing file 2025-06-0719-16-19G8T1-K001-4334-00DS.mp4: Failed to GET to url: rest-e008.immedia-semi.com/api/v1/accounts/348475/networks/342030/syncmodules/486126/localstorage/manifest/5274/clip/request/89043014 status code: 404
What should I do here? I have local storage
I have no ideas atm. Http error 404 means, the URL is not valid or the file is not found.
Your SD card has available space? Is the video available in the Blink app?
Hi Ronny, many thanks for replying! My SD card has lots of space, right now it is at 18% of storage used. How should I check if the video was available in the blink app? Which filename should I compare from that debug log with the blink app?
Many times, during try #2, it crashes with this error log: 8686cc6a-94e3-48ad-8e8a-72631744b40b
This export is done after a motion detection. This video should be available in Blink app on your mobile. You can only check this by timestamp.
Your last report has strange errors caused inside Node core modules (crypto).
No idea atm what’s wrong. Perhaps related to a Homey FW update installing new Node module versions…
Error: error:0308010C:digital envelope routines::unsupported at Cipheriv.createCipherBase (node:internal/crypto/cipher:122:19) at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:141:3) at new Cipheriv (node:internal/crypto/cipher:249:3) at Object.createCipheriv (node:crypto:141:10) at /app/node_modules/ntlm/lib/smbhash.js:46:22 at Array.forEach () at lmhashbuf (/app/node_modules/ntlm/lib/smbhash.js:45:20) at Object.encodeType3 (/app/node_modules/ntlm/lib/ntlm.js:106:3) at Object.generate (/app/node_modules/@marsaud/smb2/lib/messages/session_setup_step2.js:14:22) at SMB2Forge.request (/app/node_modules/@marsaud/smb2/lib/tools/smb2-forge.js:16:24)
Last thing, the SMB share is an anonymous guest allowed one, so I used username=guest and password = “” in homey flows
Looks like that the error:
error:0308010C:digital envelope routines::unsupported
is caused by the use of a cryptographic algorithm (createCipheriv) in a context where is no longer supported in Node.js 17+ due to OpenSSL 3 restrictions. Many legacy algorithms (like DES or RC4) are now disabled by default.
Possible solutions (I cannot do that unless given access to source code):
- Update dependencies: Try updating
ntlmor@marsaud/smb2to versions compatible with Node 17+. - Downgrade Node.js: If possible, switch back to Node.js 16 where these algorithms are still supported.
- Use a temporary workaround (not recommended for production):
export NODE_OPTIONS=--openssl-legacy-provider
This re-enables support for legacy crypto algorithms.
This issue could indeed be triggered by a Homey firmware update that upgraded the Node.js runtime or its modules.
I am not in a rush, but @RonnyW do you think it is something you can put in your roadmap?
