I had the same problem today morning when I updated my Raspbian OS. The /dev/serial/by-id directory was gone with the entity in it with the name usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_<device_serial_number>-if00-port0
Quick solution: create a symlink from existing by-path directory entity to the original by-id directory like this:
mkdir -p /dev/serial/by-id && ln -s /dev/serial/by-path/platform-fd500000.pcie-pci-0000\:01\:00.0-usb-0\:1.4\:1.0-port0 /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_<device_serial_number>-if00-port0
Longer story: After some searching and root cause analysis I found nothing what happened exactly within the OS update. Tried different solutions what worked for others (this and this), but unfortunately not for me… So no by-id directory anymore. What I found is a /dev/serial/by-path which contains a cryptic entity, but after some lsusb and dmesg inspection, I found that this is the same Zigbee dongle what was there before in the by-id directory. So I tried to add this new path to the docker-compose.yaml (I am using a containerized version ot HA), but turned out I cannot do this because of the character in the filename ( “:” aka colon character). At the end, I found a simple workaround on a forum with the same docker issue: just create a symlink to hide the cryptic filename. Finally, simply created the missing entity in the by-id directory with a symlink, so I have to change nothing at other places (like docker-compose.yaml or HA settings) related to the dongle device path. Now it works fine again.
PS: If somebody knows what happened exactly with the OS update which changed this default behavior, please write it down.