Please report missing icons.

Sorry you're running into issues ... and I'm glad you mentioned you're running macOS beta. This is very helpful.

As for the definitions disappearing: I have seen one report about this and had it happen to myself once. So far I have not yet been able to track where that bug sits in the code.
Surprising too, since the code related to saving settings has not been changed in several years now.
This could be macOS related (security rules and such), but I am keeping an eye on it!

GUI glitches;

• Dark mode issues appears beta specific. Not much I can do about this until there is a final release of macOS 27.

(sorry about that - I have waste too many days of my life trying to fix issues in macOS betas in the past, only to find out that these fixed themselves in final macOS release as they were macOS bugs)

• Hiding passwords - this is a known issue, and it is on my to-do list. 😊  Thanks for reporting though!

First, I should mention that I'm using macOS 27 Public Beta 1.

All my share definitions have disappeared. However, this didn't happen immediately after I installed the new version and restarted the app normally; it only happened after I rebooted my computer for other reasons. The app greeted me with a prompt to define new shares.

Now, a few GUI glitches:

• Dark Mode isn’t working.
• The vertical “Details” text in the “Share Details” and “Advanced Options” sections is very bold again and obscures the actual labels.
• Hiding passwords in the input field doesn’t work. They’re always visible.

I hope this helps you a little. Thank you very much for developing the app. It’s a huge help.

Best regards,

Marcus

Thanks for all the support, Hans!

I also noticed that when WiFi is enabled and ethernet connected, macOS should (according to Apple) use the Ethernet connection, but sometimes it doesn't (notice the significant speed drop). Having said that, I think it may have to do with macOS selecting the connection wth the highest theoretical throughput. Maybe.
WiFi would be nice to have though since macOS and iOS do use WiFi for copying and handing off where you left on the other device.
Kind-a like what you are experiencing, maybe a little different, but equally annoying.

In your case it most likely is seen by equipment as a new network connection (maybe).
So software may see this as a disconnect and a different network reconnect.

Glad to hear you're content for now.
Let me know if you see anything happening that I may be able to address in ConnectMeNow 😊 

Unfortunately I don't have enough physical ethernet ports on my switch to connect my laptop right now. It's in future plans. My PC (that doesn't have WiFi and connects via ethernet) gets much better speeds with my NAS.

Anyway, I've also found out another Apple quirk. I use the Handoff/Continuity features with my iPhone (such as using my iPhone as a webcam) very frequently. When that happens, Apple forces the WiFi to drop from 6 GHz to 5.4 GHz and that causes all sorts of issues with the NAS. Not just the NAS, anything that is connected gets briefly disconnected and sometimes issues happens. And macOS requires WiFi to use the Handoff/Continuity features, even if the iPhone and macOS ethernet are on the same network. Apple being Apple...

So, I think this is fine for now. Your app already helps me a lot keeping this share active on "regular" use and if it does disconnect because of Apple's quirks I can easily re-mount it. And I can now FINALLY respect UNIX's filesystem with my regular files not being considered "executables". Thank you!

By default either the text "unavailable" will be shown and/or a small badge will be shown with an exclamation mark in it.
Not what I had in mind.

Took me a while to figure this out, but here is where Card Mod comes to the rescue by applying a CSS style when an entity is not available.

First make sure Lovelace Card Mod is installed! (free)

Next for each card apply this card mod:

type: entity
entity: sensor.example_sensor
card_mod:
  style:
    .: |
      ha-card {
        {% if is_state(config.entity, 'unavailable') %}
          filter: grayscale(100%) brightness(0.8);
          opacity: 0.6;
        {% endif %}
      }

If the entity state is "unavailable" the card will turn grey scale, darker, and a tiny bit transparent.

Example entity available:

Example entity not available:

Hope this is helpful for others ... 😊 

I have all those options enabled. In the left side of the Preferences panel, the only options I don't have enabled are "Restore windows positions", "Audible Mount/Unmount Notifications", "Eject External Drives on sleep" and "Only mount when Mac is Unlocked". I don't think these would change this behavior

You're right, those would be irrelevant for your situation.
Also good to know no other apps are interfering. 👍 

CMN uses a few methods to determine if a share is mounted or not.
The closest to that would be the "mount" output in Terminal.
Sometimes macOS has not yet detected that a share disappeared and holds on to a share for a little bit. I suspect this is so shares wouldn't be unmounted to quickly/often when there are little network hickups.

So, the system still reports a share being mounted, yet in reality it isn't.

Mount output example:

~ $ mount  
/dev/disk3s3s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)

//admin@192.168.1.100/AllShares on /Volumes/AllShares (smbfs, nodev, nosuid, mounted by hans)

(I removed a bunch of local disks - the last line that starts with "//" is a mounted share no matter how it was mounted)

Even though I have the mount "On Network Change" option checked, my personal laptop very rarely (i.e, never) leaves my home. So in reality it is always connected to the same network. I've only enabled that option to guarantee the share was always available. I think, perhaps, when the laptop goes to deep sleep (lid closed, not connected to power) Apple doesn't clean the mounts' connections completely. So when it wakes up, it conflicts what it reports as mounted (what CMN sees) with the reality in the network stack/kernel state. The reason I say this is because I've seen it happen once when Finder reported the share as mounted, I tried to browse to it and it completely hanged Finder (not even `killall Finder` would work). Then I tried cd'ing into it on Terminal and it hanged Terminal the same say, force quitting wouldn't work. I resolved this by killing my WiFi and waiting. When it finally reported the mount was inaccessible, then my apps started working again. This was all Apple, not CMN's fault.

I guess I use my laptop the same way 😉 
However - I always have it wired through ethernet, so no WiFi, since WiFi is much slower and much less reliable (even if the speed indication suggests it would be faster - in reality it rarely is).

Your observation matches my experience, especially with WiFi (as mentioned before).
Try and see if you can try using an ethernet connection for a while and see how well/bad things are.
I actually always disabled WiFi, because even though Apple states it would take the better connection, at times it still uses WiFi (I see a serious speed drop when that happens).

I have all those options enabled. In the left side of the Preferences panel, the only options I don't have enabled are "Restore windows positions", "Audible Mount/Unmount Notifications", "Eject External Drives on sleep" and "Only mount when Mac is Unlocked". I don't think these would change this behavior.

I don't have any other apps for mounting shares. I honestly think it's Finder (or some internal Apple subsystem) that could be interfering with CMN's ability to detect the share. You said those lines mean the share was reported by Apple as mounted, but it was not. That would explain why CMN didn't attempt to mount it again and why it was not available after waking up (although, CMN's tray icon was showing the share as unmounted).

Even though I have the mount "On Network Change" option checked, my personal laptop very rarely (i.e, never) leaves my home. So in reality it is always connected to the same network. I've only enabled that option to guarantee the share was always available. I think, perhaps, when the laptop goes to deep sleep (lid closed, not connected to power) Apple doesn't clean the mounts' connections completely. So when it wakes up, it conflicts what it reports as mounted (what CMN sees) with the reality in the network stack/kernel state. The reason I say this is because I've seen it happen once when Finder reported the share as mounted, I tried to browse to it and it completely hanged Finder (not even `killall Finder` would work). Then I tried cd'ing into it on Terminal and it hanged Terminal the same say, force quitting wouldn't work. I resolved this by killing my WiFi and waiting. When it finally reported the mount was inaccessible, then my apps started working again. This was all Apple, not CMN's fault.