From an old 2013 post (1) is still relevant today and will definitely work)
(Always works) On the machine that you are ssh'ing from (say, your "laptop" or whatever), put an entry in the /etc/hosts files (for Unix/Linux/Mac, it is /etc/hosts. On Windows, it is C:\windows\system32\drivers\etc\hosts), associating the IP address with a name. Then you can use that name in future. This always works, but the annoyance is that you have to do it on each machine that you want to be able to ssh from.
(Works sometimes, sometimes not - you know, phase of the moon, whether or not the hour is odd or even, probably other factors involved) Install "avahi-daemon" on the Pi. When this works, it is great. It makes the hostname of the Pi visible on your LAN. Then you can use that hostname in your "ssh" command.
And for the day after tomorrow, see if your router or other local DNS supports "hairpin NAT". This lets you define domain names that point to local IP's when running on the local network even though they point to Internet addresses when working elsewhere.
The great advantage being that you can use a publicly validated TLS certificate for both external and internal use. And, of course, you can use the same URL inside and out (if you expose your Node-RED endpoints to the Internet that is - fully secured of course).