u/36260

I own a DS1813+ (2013) and have observed the following behavior: after a clean DSM shutdown, cutting and restoring AC power does not restart the NAS. The "Restart automatically when power supply issue is fixed" option only works if the NAS was running at the time of the power cut.

Note: in our setup, the UPS is not directly connected to the NAS but to a dedicated Linux server running NUT, which shuts down the NAS via DSM API. The NAS therefore cannot use the native Synology UPS standby mode.

Furthermore, after a clean shutdown followed by a power cut, the network card powers off — which is expected — but does not power back on when AC is restored. This prevents WoL packets from being received, making remote wake-up impossible in this scenario.

This creates a problem in my UPS/datacenter shutdown automation: I need the NAS to restart automatically after a power outage that occurs following a graceful shutdown sequence.

Questions for owners of recent models (DS923+, DS1522+, DS1621+...):

1. After a clean DSM shutdown followed by AC power cut and restore, does your NAS restart automatically?
2. If not, is WoL still functional after AC power has been cut and restored (i.e. is the network card powered in standby mode after AC is restored)?
3. Has this behavior improved compared to older models like the DS1813+?

.Hi Mammotion team,

After updating to firmware 1.15.20.44.13 and app 2.4.3.19, the robot has become completely unusable. Please treat this as a critical regression.

**Symptoms observed:**

- The robot no longer follows the planned path on the map — it makes erratic, unexpected turns.

- During operation, the robot stops moving while the blades keep spinning for approximately 1 minute, then the blades stop on their own.

- No error message is displayed at any point.

- After this self-stop, the app incorrectly shows the status as "Pause", even though the robot paused itself — the button state is wrong.

**Environment:**

- RTK satellite reception: perfect (both robot and base)

- This behaviour was not present before this firmware update

**Pre-existing connectivity constraint:**

Wi-Fi and 4G are unavailable at the robot's location — this is a known site limitation that predates this update. Bluetooth is the only available connection channel, which requires physically travelling to the robot for any interaction. This makes iterative troubleshooting extremely difficult and amplifies the impact of any firmware regression.

Prior to this update, the robot was working reliably despite this connectivity constraint. The update introduced all of the above mowing issues simultaneously, so a firmware rollback option or a hotfix release would be the only acceptable short-term path forward.

Please advise on next steps as soon as possible.

Thank you.