@joseph_1979 Well I for one use the desktop clients. On what do you base your assertion that "Nobody is asking anymore" for these? If you use a desktop the large screens they provide are a much more functional way of accessing cameras than the relatively tiny screens of smartphones. Don't extrapolate from your own use to generalise that everyone works the same way that you do. I would be devastated if Reolink gave up on the desktop versions.

I am running the latest current version (8.17.8) for macOS which in some respects works fine (on MacMini M2Pro with macOS 15.1 Sequoia), although it is very slow to start up, but the main issue is that it always crashes on quitting the app. Any chance of a new version to fix this? I assume you are getting a report every time this happens so your developers must be able to work out what is causing it.

And this is STILL an Intel code version - when will an Apple Silicon version be released? It is FOUR YEARS now since the M1 was introduced which is surely enough time to port the application across to be native on Apple Silicon chips. The iOS app is obviously compiled for Apple Silicon - why not the macOS application as well? This is the ONLY application of the vast number I use on my Mac that is not Apple Silicon native.

@peteintas_654598748397683 Can I second this request? Not only is it well past time for an Apple Silicon native client (over four years since the M1 was first released) but the current version (8.17.8), although stable in use, takes a long time to launch and crashes every time you quit.

What I am not clear about is when you select the camera underneath the heading for the Home Hub, and then click on Playback, are you seeing the recordings on the SD card in the camera, or the SD cards in the Home Hub. I had thought these were the recordings in the camera.

When you look at Event History in the HH the recordings are only the fluent quality, and there does not seem to be any way of accessing a higher resolution than that. For security reasons I am not comfortable with only being able to get at the recordings in the camera, because that could be attacked, whereas the Home Hub can be locked away.

There does not seem to be any way to get the Home Hub to record in Clear resolution rather than Fluent. There is little point to the Home Hub, excellent though its facilities are, if it can't record in Clear resolution as fluent resolution is not good enough to decipher car registration plates or to identify people's faces. Is it likely that this will change?

I am absolutely amazed that five years after Apple Silicon was introduced this new version of the macOS application is still coded for Intel chips only. This is THE ONLY software I use on my Mac mini M4 which is not Apple Silicon native. When will this be compiled for Apple Silicon?

@joseph_1979 Well I for one use the desktop clients. On what do you base your assertion that "Nobody is asking anymore" for these? If you use a desktop the large screens they provide are a much more functional way of accessing cameras than the relatively tiny screens of smartphones. Don't extrapolate from your own use to generalise that everyone works the same way that you do. I would be devastated if Reolink gave up on the desktop versions.

@peteintas_654598748397683 Can I second this request? Not only is it well past time for an Apple Silicon native client (over four years since the M1 was first released) but the current version (8.17.8), although stable in use, takes a long time to launch and crashes every time you quit.

I am running the latest current version (8.17.8) for macOS which in some respects works fine (on MacMini M2Pro with macOS 15.1 Sequoia), although it is very slow to start up, but the main issue is that it always crashes on quitting the app. Any chance of a new version to fix this? I assume you are getting a report every time this happens so your developers must be able to work out what is causing it.

And this is STILL an Intel code version - when will an Apple Silicon version be released? It is FOUR YEARS now since the M1 was introduced which is surely enough time to port the application across to be native on Apple Silicon chips. The iOS app is obviously compiled for Apple Silicon - why not the macOS application as well? This is the ONLY application of the vast number I use on my Mac that is not Apple Silicon native.

user_846994761957606 I had the same problem - this board has a ridiculous limitation on how often you can post (only once every 24 HOURS!) which is undoubtedly more inconvenient for legitimate posters than serving any purpose to stop illegitimate ones.

@wisemanjaw This is obviously an important issue in these modern scary times. It seems to me that we have to take quite a bit on trust. There are three scenarios I have come up with:

1. Do not connect your cameras and other connected devices to the internet - set up a VLAN for them which cannot get to the internet. Or alternatively block every individual device in the router (based on its MAC address) if it has that functionality.
2. Allow the devices to connect to the internet in which case you can access them from anywhere using their UIDs, which is undoubtedly very convenient. Ensure that the username and password are BOTH changed from the default settings and the default "admin" user is disabled. The safety of this scenario depends on trusting that Reolink do not surreptitiously upload the username and password you have set to their "DDNS" or relay system and then make use of them. Hopefully this is not the case.
3. Do not change the default settings for username and password (much harder for this to happen now for newer devices that the EU has mandated that this should happen automatically when the camera is first set up) and then your cameras are less secure but this still depends on someone finding out the UID. This could however be achieved through randomly trying UIDs, although hard to target any individual this way.

It is pretty certain that the access to 129.146.110.167 would be for the purposes of registering the IP address which corresponds to the UID.

@joseph_1979 That's not correct, I'm afraid.

The issue is that in countries which don't have as much light in the winter (such as the UK) the standard panel does not generate enough power to keep the camera charged all the time, particularly through the whole night in the darkest part of the year. I have used a panel which has twice the output of the standard panel successfully, and although it may be, as you say, that the maximum charging current is limited, the larger panel will generate that maximum current very much more of the time.

This is the same as having more solar panels on a house solar PV system than an inverter is rated for - as an example if you have 10kWp of solar panels but only a 6kW inverter, you will not get 10kW out of it, but you will get 6kW very much more of the time.

So oversizing the solar panel on a camera is definitely worth doing when the amount of light is limited.

The new app works really well on my Mac mini M2. I am very impressed at how quickly it launches and starts showing all the feeds - wish the desktop app were anything like as good as this is.

The only issue is that I did manage somehow to get the window to rotate as if it was running on a phone and I had rotated it. The way I got it back to the correct orientation was to choose the smaller window size in Settings... for the app, then when it relaunched it was the correct orientation again.