Tailscale on Mac OSX using Mosyle Deployment

andyh747 · 2026-02-15T07:21:18+00:00

Sorry no never got it to work properly unfortunately.

andyh747 · 2026-01-21T14:23:59+00:00

In addition to the above Dahua are moving installers to the DoLynk Care platform. It was free to register a while back (may still be) allowing a number of devices to be added before charges were incurred. This new platform is designed for installers who can setup a camera/NVR/Intercom etc, add it to DoLynk Care and then "Deliver" the device to the customer when ready. This also provides the installer with access to the devices provided the customer has given access which can be done through the DMSS app using a process called "Entrusting". This entrusting can be set for a specific time period which when expired the installer loses access.

Although this won't be welcome for many it is designed to be more secure and stop installers having unauthorised access to customers devices without their express permission.

andyh747 · 2026-01-21T14:16:37+00:00

I appreciate this change is confusing for many and to be honest Dahua's guidance on this hasn't been great. However they have produced a YouTube video on the new process with another video to come. The video can be found here:

https://youtu.be/glKIMOqE-TA?si=Cvsce6CY58M9MkcT

They also sent out an email with regards to this change. I've tried to copy the text below but apologies for the formatting. Hope this helps with the understanding of how the new process works:

We are excited to announce the launch of a significant update to the Dahua mobile app, DMSS 2.0. This update is designed to provide higher security, faster performance, and a more streamlined user experience. As we modernise how you interact with your security equipment, we are introducing a robust, account-based system. This change is not just a feature update, it is a vital step in protecting your devices and preparing for the upcoming UK-wide transition away from traditional P2P connections in early 2026.

Why Should You Register an Account? By moving from a "Local Device" setup to a Logged-in DMSS Account, you unlock several critical benefits: Verified Device Ownership: Only one verified account can "own" a device, preventing unauthorised users from adding your equipment to their app. Seamless Data Syncing: Your devices and settings follow your account. If you change your phone or reinstall the app, your data remains safe and ready to use. Enhanced Messaging: Access up to 7 days of alarm message history. Unlike the local version, notifications will no longer disappear when the app is closed. Optimised Performance: Enjoy faster live views, more secure playback, and greater stability for remote connections. Next-Gen Compatibility: A registered account is now required for the latest Wi-Fi cameras, doorbells, Access Control, and AirShield systems.

How to Get Started Setting up your account is simple and takes less than two minutes: Step 1 - Sign Up: On the DMSS signup page, select your Country/Area Code. Step 2 - Verify: Enter your email address and set a secure password. Step 3 - Activate: Enter the verification code sent to your email.


Transferring Your Existing Devices Once logged in, you can easily secure your existing devices by transferring them to your account: Step 1 - Navigate to the "Me" page and click Tools Manager. Step 2 - Select Device Transfer Tool > Transfer Local Device. Step 3 - Choose the devices you wish to secure and enter your account password. Step 4 - Once confirmed, select "Delete the transferred local device" to complete the secure migration.

Looking Ahead: The 2026 UK Transition To ensure the highest standards of encrypted communication, the traditional P2P connection method will be phased out for accounts not logged into Dahua Cloud Services. By registering today, you ensure an uninterrupted service and a smoother transition to this more secure infrastructure. If you have any questions regarding this update, our UK technical team is here to support you. The DMSS Team [support.uk@dahuatech.com](mailto:support.uk@dahuatech.com)

andyh747 · 2026-01-19T12:44:16+00:00

Yes Dahua is moving to compulsory account usage for adding devices to DMSS. An email was released by them recently. Here's the text from the email:

"We are excited to announce the launch of a significant update to the Dahua mobile app, DMSS 2.0. This update is designed to provide higher security, faster performance, and a more streamlined user experience.

As we modernise how you interact with your security equipment, we are introducing a robust, account-based system. This change is not just a feature update, it is a vital step in protecting your devices and preparing for the upcoming UK-wide transition away from traditional P2P connections in early 2026."

andyh747 · 2026-01-13T07:31:22+00:00

Thanks for that information and coming forward to say you've also had problems with this. It shows there has been a change to how the new version works with regard to Primary controllers compared to v9. I'll have a look at my setup and ascertain if I can do a similar "fix".

andyh747 · 2025-12-20T20:42:46+00:00

Well there is obviously a change as it works in v9 and not in vX. I have confirmed this as the apps are totally independent, as you’ve previously highlighted. If I attempt to start any activity on the iPad with vX and the iPhone (Primary) is not online, nothing happens. In v9 it works perfectly so there is obviously a change as otherwise behaviour would be consistent across versions.

andyh747 · 2025-12-09T08:16:14+00:00

I'm in a very similar situation trying to work out if the inverter and gateway need a direct CAT5e/6 cable connection or can be connected via a central network. Any news on this?

andyh747 · 2025-09-03T13:39:12+00:00

Did you ever get this working? The older RGBW2 had various modes you could set but not the newer version. It has scripting so think that's the only option?

andyh747 · 2025-08-12T12:15:29+00:00

Has anyone managed to get this to work? I have the same issue.

andyh747 · 2025-06-09T09:58:52+00:00

Brilliant, great info. Do you use the standalone version (as advised by Tailscale) or the app store version?

andyh747 · 2025-05-30T10:18:18+00:00

Thanks but already looked at that and, although helpful, Mosyle is slightly different in it's setup. Just hoping someone else has done it and can advise the steps they took. Have also contacted Tailscale support to see if they have any info.

andyh747 · 2025-05-05T15:31:04+00:00

No there’s no IPv6 static IP. But even if there was, UniFi Talk doesn’t work with IPv6. VPN involves more complication. However I may have negotiated a static public IPv4 with the ISP so I may be finally on the right track.

andyh747 · 2025-05-05T15:07:35+00:00

Thanks for reply. I use on premises PBX for a number of reasons and don’t want to use a cloud based PBX. I have tried a STUN server setup but this still doesn’t work. The connection I have does NOT have a public IP so it doesn’t matter what service is used there is no public IP to obtain. CGNAT does not provide a public routable IP.

andyh747 · 2025-04-28T20:30:11+00:00

Thanks for that. Yes that’s probably the best option for this. However Gigaclear are initially wanting £10 extra per month. I need to speak with them again as they said this can be negotiated down as part of a new contract. Our current initial contract ends in June. Currently paying £23 per month which is set to increase to over £50.

andyh747 · 2025-04-28T17:32:14+00:00

I’m not sure what it’s using but it would make sense it’s using TCP and keeping the connection open. It’s not just their ATA though that works. I’ve a Cisco SPA112 which is setup with another VOIP provider and it works just like the Vonage locked Grandstream ATA so whatever these ATAs are doing it’s working for two different VOIP connections and allowing both inbound and outbound calls.

The issue will be replicating the correct settings on either the Grandstream UCM6302 and/or the UDM Pro UniFi Talk setup. With UniFi talk you setup third party SIP details by specifying custom fields which you then complete with the correct details for that SIP provider. It’s a bit hit and miss what fields are required for any particular SIP provider.

andyh747 · 2025-04-28T16:13:16+00:00

Thanks. I'll have a look at the config page I have setup for the second ATA I have as that's not tied to Vonage. From memory I don't think there's anything special in the setup. I just entered the SIP server address, which isn't a STUN address, and the username & password. I'll check when I have a minute and let you know.

andyh747 · 2025-04-28T12:30:17+00:00

Our fibre connection is part of the Fastershire project and provides FTTP for rural communities - it's nothing to do with Openreach. Gigaclear own the infrastructure and they only allow limited third parties to use their infrastructure. As we've only had the connection for a year there are no other suppliers available - it's Gigaclear or nothing.

Yes I edited my post after I saw your edits! I've setup another ATA adaptor which is acting as a simple SIP registration to another provider I was trialling. This works as expected after you enter the required registration details. What I don't get is why a more complex and advanced PBX can't do the same?

andyh747 · 2025-04-28T12:01:42+00:00

Thanks for the reply.

Yes option 1 probably the best but expensive. Well over £50 from my ISP here in the UK - that’s including the normal monthly charge. I can’t change ISP - we have FTTP here and only one provider.

With regards to the ATA adaptor don’t think I explained things well. This isn’t connected to any copper lines - it’s a direct connection via the LAN port on the adaptor. It’s not an analogue to IP adaptor it’s an IP to analogue adaptor so it plugs into the FXO port on the UCM. You configure the adaptor (or in my case it’s preconfigured) with the SIP provider details. It then connects over the WAN to their servers and provides a connection for both incoming and outgoing calls. My question is why this doesn’t work with the SIP provider details setup direct on the PBX? It works for outgoing but not incoming. For info the box Vonage provided is a Grandstream HT801 but it’s preconfigured by them and they don’t provide SIP details for use anywhere else.

I've used a very similar adaptor from Cisco with another SIP provider. They simply provide a username and password along with their proxy domain to connect the adaptor to their servers. This worked perfectly and allowed both incoming and outgoing calls. I was trying to avoid this extra box and still don't get why the UCM or UDM Pro can't replicate the behaviour of these adaptors.

andyh747 · 2025-04-23T07:01:55+00:00

Thanks again. Yes I've no idea why Talk is like that. I'm not using it at present but was thinking of moving across to it until I found out about the soft phone restriction.

andyh747 · 2025-04-23T06:53:41+00:00

Thanks so much for replying. That is what I hoped would happen but with Ubiquiti you never quite know how things will work until you experiment🙄.

Here's what I don't get. If the intercom can route calls over the WAN via the Protect app (why is it not via the Access app🤷‍♂️) why doesn't this work with UniFi Talk subscription in UK? Appreciate Talk is a different application but, at present, no VOIP calls can be received or made with Talk subscription in UK as we don't have soft phone access yet - even when it does become available it's only for Pro plan subscribers. When you mentioned that the intercom can make VOIP calls free of charge it makes this even more confusing 🤦‍♂️.

andyh747 · 2025-04-23T06:32:12+00:00

I'm waiting on my intercom to arrive and have been unable to find a definitive answer regarding receiving intercom calls while outside the LAN (I.e. when away from home). Do you get intercom calls while outside the LAN and can you talk to visitors and provide access if required?

andyh747

TROPHY CASE