Reolink updates Learn More
Meet Reolink at IFA 2024! Learn More
Reolink Q&A Learn More
Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
I'm going to make a label for the doorbell button (cos there are other flats/it isn't as clear as we want it to be which button to push for our place).I already know how to make round stickers from other community group/pricing labels I've done, and have software to make a full page of the same round design (that can also just do 1). I also have transparent stickies to put over it and make it weatherproof. I just needed to go measure the button; its 1" / 25.4mm (not including the LED-lit ring around it). If you don't have round printable sheets of sticky labels (or white ones to print the label on and clear ones on top to waterproof it) you could cut out some paper and a disc of sticky-tape (or smaller) e.g. 25mm wide roll of sellotape/other branded one. I aim to make it look as professional as possible, and I think there's no risk to the doorbell in heat or usage terms (if sticker was too big or thick it could stick the button and the facia around it making it harder to press, or make the round ring LED not so visible).
What does the push notification frequency setting actually do? ie. What does it mean when it is set to 20 seconds (the default)? I can't guess it. For further context, I am wondering if it is that it sends a notification every 'setting value' seconds (eg. 20) while a notification event is happening? Is it doing a check-in every 20 seconds when nothing is happening? (would that cause extra network or power usage in the phone for normal non-notification times if I change it to a shorter time?)
@joseph_1979 SIP has the most support IMO but maybe XMPP has the most functionality; as long as they use something there's good Linux foss software support from / mobile phone apps (including for whatever encryption), I would be happy to see it.
The terms and conditions on the Android app changed and forced me accept before getting into the app proper today, and they didn't offer a "here's what changed" section or explanation. It's quite a long document and in kinda legal style, so most people I'm sure just click accept. But I wanted to dig a little - and getting at the text from the app was harder - why no copy paste on that reolink/link to the terms so it can open in your own browser if you for instance prefer to read it with different style or with a tool that helps you for accessibility?So I copy-pasted them into documents and used a free comparison tool website to look at the differences. Its mostly formatting and re-wording without changing the meaning (but I am not a lawyer), and being more explicit (e.g. "Reolink" instead of "this" or "our"), and that anyone who hacks your account or other person with non-consensual access isn't seen as legit user of services, or a "password holder" who would be allowed to use it (multiple places where one possible interpretation allowed that before). Sometimes the wording is just made more explicit and less standard-legalese, e.g. from "Your rights" ... "may not be used for commercial activities" and are "non-transferrable", reworded to "You may not resell"... or otherwise "make available for third parties".The general pattern of changes how I see it, is of internationalisation (rewording or removing USA-specific terms to be more general), tightening up/being more explicit about what the reverse-engineering parts refer to and that they can terminate services for it.Summary of differences I spotted that were slightly less than trivial:New "harmful or objectionable" term in ways you aren't allowed to use the serviceInstead of "please contact us" if you find any unauthorized use, its "You agree to notify us immediately", noting the standard "Reolink will not be liable for any loss or damage"More explicit about "decompiling or reverse engineering"Added "We reserve the right, in our sole discretion, to refuse service, terminate accounts, cancel orders, or terminate your rights to use Reolink Services."There's a big set of changes under where "Prohibited Contents and Behaviours" section is now removing USA-specific terms relating to the constitution and following laws (those obviously apply anyway, but only in USA).
I can't link to my comparison but I used draftable (free online service that can compare documents, after I saved each one copy-pasted into a Word doc). Remember, I'm not a lawyer, and I might have missed something or misrepresented but I did my best to check it (for my own satisfaction) given the things I care about more/less. If you're a company, or likely to otherwise have notably different use or engagement with the services than me (who is a resident in the UK), I recommend you do your own checks.
@helipad-haven_760967332798719 yep, still happens on mine too. Its pointed south-west ish so sees sun in evening, but usually (not always) happens in morning too. Can see the rise/set getting later and earlier through the year because of it (slight variation in time due weather, cloud level etc.)Note: if its recording while the switch happens, it should probably continue recording for a moment til detection has a chance to spot whether event is over/a new one. Or at the very least, pause it temporarily. Wouldn't want a gap in an important moment cos it stopped recording for that reason (and/or didn't start again).
@quizzical have reported it and had a brief discussion with support, they've passed my issue on and its still active. I've tried an old tablet (Leonovo from 2017) which works fine for volume at the doorbell, but is a bit underpowered nowadays to use for chat for it (and the battery doesn't last long enough to leave it where we would use it more). My Samsung Galaxy (S8+, so a bit older) is too quiet, just about audible when right up close to the doorbell on maximum app volume. My wife's S10 also is just as quiet. I saw someone say an S21 was fine. So maybe it's not ALL Samsung's. But more than just the odd one. And not just older Android devices (cos the Lenovo is fine). Maybe it is the thing someone suggested about using the wrong microphone - I did try it with a bluetooth headset connected but same result (maybe worse, so am not sure it uses the headset, maybe it was still using the normal phone mic, but could be persuaded that was me doing it badly if someone else sees it helping).
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!