January 25, 20251 yr Hi team, I have been trying nonstop but I can't seem to get a NAS share to show up in the Aqara doorbell app (its the app that allows you to select a storage device). Currently its set to SD card, but it lets to choose a NAS option. I can see my laptop (this is not where I have unraid running), yet when I set up a SMB share on unraid, I can't get it to show up. I've tried creating it a public and provite windows share, and then I wanted the ability to limit how much space the doorbell folder takes up given it will just rewrite old data so I also had set up the share as Time Machine. I did enable NetBIOS and WSB in the settings but still no luck. Any help is much appreciated mtower-diagnostics-20250125-1730.zip
January 25, 20251 yr Something that kept me from seeing my SMB folder was that I had not set the Export option to Yes in the SMB security settings. You might try that.
January 26, 20251 yr Author 15 hours ago, HutchG said: Something that kept me from seeing my SMB folder was that I had not set the Export option to Yes in the SMB security settings. You might try that. Thank you for the reply, in the diagnostic I didn’t have export set to yes but I did try again and still no luck
February 22, 20251 yr Has anyone managed to figure this out yet? I recently set up a new server with 7.0, and moved everything over from my old Asustor. This is the one thing I can't manage to get working. I can actually get it to show up when the array is down, but it disappears with the array up.
February 23, 20251 yr Community Expert On 2/5/2025 at 9:54 PM, mittygritty said: Bump Run the tool New Permissions on only the share for which you do not have access.
February 26, 20251 yr Author On 2/22/2025 at 7:17 PM, Frank1940 said: Run the tool New Permissions on only the share for which you do not have access. I got this: Processing: /mnt/user/Doorbell ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/user/Doorbell ... chown -R nobody:users /mnt/user/Doorbell ... sync Completed, elapsed time: 00:00:00
February 26, 20251 yr Community Expert 2 hours ago, mittygritty said: I got this: Processing: /mnt/user/Doorbell ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/user/Doorbell ... chown -R nobody:users /mnt/user/Doorbell ... sync Completed, elapsed time: 00:00:00 Does this fix it-- even temporarily? If not, give us a screenshot of this portion of the setup tab for the Doorbell share:
February 26, 20251 yr Community Expert On 1/25/2025 at 5:30 PM, mittygritty said: Aqara doorbell app What is this thing? I can't find it in the Apps plugin for Unraid. Is a Docker Container or something running in a VM?
February 26, 20251 yr Community Expert From syslog: Jan 25 11:15:59 mtower unassigned.devices: Remote Server '192.168.68.113' is offline and remote share 'P' cannot be mounted. Jan 25 11:15:59 mtower unassigned.devices: Mounting Remote Share '//MTOWER/Doorbell'... Jan 25 11:15:59 mtower unassigned.devices: Mount SMB share '//MTOWER/Doorbell' using SMB default protocol. Jan 25 11:15:59 mtower unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,credentials='/tmp/unassigned.devices/credentials_MTOWER_Doorbell' '//MTOWER/Doorbell' '/mnt/remotes/MTOWER_Doorbell' Jan 25 11:15:59 mtower kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified Jan 25 11:15:59 mtower kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified Jan 25 11:15:59 mtower kernel: CIFS: Attempting to mount \\MTOWER\Doorbell Jan 25 11:15:59 mtower unassigned.devices: Successfully mounted '//MTOWER/Doorbell' on '/mnt/remotes/MTOWER_Doorbell'. Jan 25 11:15:59 mtower unassigned.devices: Adding SMB share 'MTOWER_Doorbell'. Jan 25 11:15:59 mtower unassigned.devices: Waiting 5 secs before retry mounting Remote Shares... What is this server at IP address 192.168.68.113? And what is this share MTOWN/doorbell that you are attempting to mount?
February 28, 20251 yr Author On 2/26/2025 at 8:06 AM, Frank1940 said: From syslog: Jan 25 11:15:59 mtower unassigned.devices: Remote Server '192.168.68.113' is offline and remote share 'P' cannot be mounted. Jan 25 11:15:59 mtower unassigned.devices: Mounting Remote Share '//MTOWER/Doorbell'... Jan 25 11:15:59 mtower unassigned.devices: Mount SMB share '//MTOWER/Doorbell' using SMB default protocol. Jan 25 11:15:59 mtower unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,credentials='/tmp/unassigned.devices/credentials_MTOWER_Doorbell' '//MTOWER/Doorbell' '/mnt/remotes/MTOWER_Doorbell' Jan 25 11:15:59 mtower kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified Jan 25 11:15:59 mtower kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified Jan 25 11:15:59 mtower kernel: CIFS: Attempting to mount \\MTOWER\Doorbell Jan 25 11:15:59 mtower unassigned.devices: Successfully mounted '//MTOWER/Doorbell' on '/mnt/remotes/MTOWER_Doorbell'. Jan 25 11:15:59 mtower unassigned.devices: Adding SMB share 'MTOWER_Doorbell'. Jan 25 11:15:59 mtower unassigned.devices: Waiting 5 secs before retry mounting Remote Shares... What is this server at IP address 192.168.68.113? And what is this share MTOWN/doorbell that you are attempting to mount? 113 is a different share that I left unmounted (not using this share for this) On 2/26/2025 at 7:49 AM, Frank1940 said: What is this thing? I can't find it in the Apps plugin for Unraid. Is a Docker Container or something running in a VM? This is the phone app for the doorbell (not an app inside Unraid). Sorry I should have clarified. On 2/26/2025 at 7:45 AM, Frank1940 said: Does this fix it-- even temporarily? If not, give us a screenshot of this portion of the setup tab for the Doorbell share: The fix did not solve the issue unfortunately. Here is my snapshot: Edited February 28, 20251 yr by mittygritty
February 28, 20251 yr Community Expert On 1/25/2025 at 5:30 PM, mittygritty said: Hi team, I have been trying nonstop but I can't seem to get a NAS share to show up in the Aqara doorbell app (its the app that allows you to select a storage device). Currently its set to SD card, but it lets to choose a NAS option. I can see my laptop (this is not where I have unraid running), yet when I set up a SMB share on unraid, I can't get it to show up. It appears that you are trying to have the app on the smartphone store its data on your Unraid server in the share called doorbell. Is this correct? If this is the case, you should not require Unassigned Devices plugin. you want to connect to mtower/Doorbell (or possibly, mtower\Doorbell ) and note that the Unraid share name is case sensitive! You may require a Unraid Share Access user be setup with a user name and password. (I know nothing about the security of the smartphone you are using but it might prevent any connection to a server for which you do not have a login!) You would use this user name and password to set up the login from the smartphone app to your Unraid server. You may need to ask the Aqara APP developers for help. (I know I can't provide you any assistance on this.) Edited February 28, 20251 yr by Frank1940
April 9, 20251 yr I figured this out! Go SMB Settings. Under SMB Extras, put the following configuration so that NAS is dicoverable in Aqara app [global] browseable = yes server min protocol = SMB3 // not sure if this one is needed
April 28, 20251 yr @cbenvenuto I’ve tried your solution, however unfortunately the share still didn’t show up in the Aqara app. Could you maybe share a screenshot of your smb settings?
May 22, 20251 yr @dwffls I had the problem, I'm not sure the setting browseable = yes in global settings is safe since it should be a per share specific setting ?I checked on my phone and the SMB share was showing with an IP address instead of the netbios name, despite the fact I enabled it (NetBios) and the server had the name "homeserver" in settings.Since other visible SMB shares had Uppercase name I decided to set it manually in SMB settings with Uppercase name also (don't know if that matter)I also disabled Enhanced macOS interoperability, I restarted and it worked, so I don't know if it was because of the macOS interoperability or UPPERCASE netbios name.Here is my extra samba config (you can check the whole config in my screenshot)[global] netbios name = HOMESERVER server string = serveur %h (Samba %v, Unraid)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.