I (my little company) employ a bloke to support https://www.uzerp.com/ - we use it ourselves and ditched Sage (yay!)
If you fancy it then give us a shout - it is open source - you get it for free but our time is costed if you need assistance.
That is the Open Source Covenant
I think we might be writing at cross purposes. The system you had for your mum obviously worked effectively for you and that is the important thing.
POTS provide(s|d) a fixed point of reference - your address is registered against the number for 999 etc; it provides power for a handset or device; Its been like that for a lot of decades! These are cast iron guarantees. A POTS line has guarantees, enshrined in UK law, that mobile etc does not have. POTS is circuit switched (well it was) which means there is a physical path between the ends for the duration of the conversation.
So, by old school, I mean that you currently have important guarantees about telephony in the UK that will evaporate in future. In 2025 or so, we in the UK will have finished migrating from our old school POTS copper lines and will enjoy our smart new SoGEA lines instead. Single Order Generic Ethernet Access. Instead of an emulated circuit switched line we will use VoIP across the entire country. Nothing wrong with that but it probably won’t have the guarantees that POTS had.
Red Care is no more - BT have dropped it on the floor as of Feb this year which may indicate that things are not well with our future comms promises. The general system that Red Care was one product of is still available.
This is the important point: Promises (in law) that we used to be able to rely on for comms may (will) be binned.
In the UK at least, the POTS (Plain Old …) copper phone lines carry an electrical current as well as signals and can power the handset. There are certain guarantees about this so that in an emergency your phone will still work so you can dial 999 (our original emergency number) or 112. Our fire regulations require something like 30 minutes before things should start failing. In the real world, you get out immediately and use your mobile.
We have an emergency alarm monitoring system used by businesses. Its generally known as “Red Care” which was a brand run by BT (British Telecom). You have a small device connected to a phone line (and powered by it) and it will monitor your fire detectors and building access control systems and a 24 hour manned monitoring centre will notify you in the event of an emergency. Nowadays, these devices will use your wifi and internet connection. Sometimes: old school is best.
I know what you mean. You’ve already read a load of log files on behalf of an “engineer” who seems incapable of doing it themself. You’ve also eliminated DNS and NTP and laughed at suggestions relating to SFC /SCANNOW. Then you roll up your sleeves and plug into the Matrix …
Which distro do you use? Ubuntu, Debian, Arch and Gentoo have packages and I’ve no doubt that most others do too. On Linux you should not have to go to random websites and download stuff and faff around - use the built in distribution packages. If you are not sure what you’ve got try this at a command prompt and read the output:
$ cat /etc/os-release
As a last resort, you can run tcpdump on nearly anything and dump to .pcap, transfer that and then open that in Wireshark. Note that modern Windows has a OpenSSH client and server available so getting files around via scp is a doddle. Windows can even do NFS too and there is of course Samba - but CIFS/SMB can be tricksy.
Errm, Wireshark. Please bear with me.
Wireshark is a shining example of an open source project completely and utterly crapping on the closed source competition. As a result we all benefit. I recall spending a lot of someone else’s money on buying a sort of ruggedized laptop with two ethernet ports to do the job back in the day.
Nowdays, I can run up a tcpdump session on a firewall remotely with some carefully chosen timings and filters and download it to my PC and analyse it with Wireshark.
OK, all so convenient but is it any use?
Say you have a VoIP issue of some sort. The PCAP from tcpdump that you pass to Wireshark can analyse it to the nth degree. Wireshark knows all about SIP and RTP (and IAX) and you can even play back the voice streams or have them graphed so you can see what is wrong or whatever. That’s just VoIP, it has loads of other dissectors and decorators built in.
So what?
The UK (for example) will be dispensing with boring old, but reliable, POTS (Plain Old Telephony System) by 2025. Our entire copper telephony and things like RedCare (defunct soon) will go away.
We are swapping out circuit switching for packet switching. To be fair, a lot of the backend is already TCP/UDP/IP that is shielded away from us proles. When SoGEA (Single Order Generic Ethernet Access) really kicks in then the old school electric end to end connection will be lost in favour of packet switching, which never fails (honest guv).
If you are an IT bod of any sort, you really should be conversant with Wireshark.
A quick search comes up with “Phone Link” which only seems to work with Windows on the “PC” end, whereas KDE Connect will work everywhere that KDE works, which includes Windows.
https://www.microsoft.com/en-in/windows/sync-across-your-devices
It really isn’t the same as Konnect which is a bloody marvel! I’ve used it for years.
Nextcloud is simply software that runs on something. You might use DNS to find the something that your Nextcloud runs on … or not. A domain can cost as little as say £10/year (no details given - loose costing provided!) but you say you don’t want one.
You could do some weird stuff involving something like this: Your clients update a database on the server with their current IP address(es) and the server reciprocates in kind regularly.
For an internets conversation, both sides need to know IP address, protocol, and optionally port; for both ends. For example, a webby conversation might involve:
My end: 192.168.100.20/24, tcp port 2399 -> NAT -> 33.22.4.66, tcp port 2245 Remote web server: 99.22.33.44/37, tcp port 443
Now, provided both sides are warned off about changes to addresses and port numbers on a regular basis, then comms will still work.
Say, your home external IP address changes, then your browser writes that new address to the remote server and comms continue. Provided one end knows all the details of the other end at any point in time and can communicate local changes then we are good.
000000000000000000000000000000000000000000000000000000000000000000
Maybe not. Lookup: Dynamic DNS.
My home and work ones both have Zigbee and Zwave. The modern ZwaveJS integration is amazing compared the old effort. Also: ESPHome, NUT, Mossie (MQTT), nginx proxy manager, MariaDB, nodered, Piper and that, Remote Backup, Terminal and SSH, DSS VoIP Notifier, VLC.
HACS with a fair few custom cards etc.
SO: Next door have got their lights up, why haven’t we? Me: (Enable NodeRed flows for gutter and pergola light strings that switches them on at dusk and off late evening) Right, that’s the missus pacified for a week or so. I should probably get BigTimer to sort that out itself.
Employee: I’ve got all the printers for <customer> monitored using an auto entries card. (Good skills) Me: (Installs an addon that can use VoIP to do text to speech to a phone) We warn off the customer and now they get a phone call from “things” that tells them what consumables to buy and also sends an email.
When I finally get around to sorting out my glasses so I can see what my soldering iron is up to, I’ll get many more gadgets installed. My computer room at work needs a tiny ESP8266 and four 1 wire Dallas SC temperature sensors, a bit of vero board, a resistor, power and probably a buck convertor and a case, which I’ll print.
I adore HA.
I only use Reolinks these days. RLC-410 - some dome and some bullet. Cheap and easy to setup. I’m a long term Zoneminder user which I get to watch the low res stream and record on the high res stream. My ZM is a VM on VMware with a cheap Nvidia GPU passed through for CUDA. This still works: https://wiki.zoneminder.com/GPU_passthrough_in_VMWare but I should probably bring the wiki page up to date.
I have a Reolink door bell too - I went for the PoE one. It’s a lot better than my old Doorbird but not as sturdy. The door bird could drive a chime too which was nice. The Reo can’t but it is a PoE powered unit with a UPS backing the switch. That’s pretty resilient.
They never get to see the internet. I fiddle DNS so that pool.ntp.com points at my ntp daemons but I run an IT company so that might be a bit excessive for most! I have three Pis with GPS hats and antennae.
As you say, they are well supported by HA too. If you have a Coral and Frigate then you have lots of options. Just keep them away from the internet if you are concerned about who is looking through them apart from you.
I once named a load of servers for a helicopter company in the UK with elements. The cluster nodes were copper, silicon, etc. The cluster itself was called iron. The volumes were labelled fe_function.
It worked - it was easy to read and the bits that implied “cluster” were grouped appropriately. All the other servers had random elemental names unless they were associated in some way, in which case the group would be used. The engineers (real engineers with oil or distressingly nasty lubricants in their veins) loved it - it made sense, without being too quirky. It was very legible.
When those systems were hoicked out and replaced, the usual nonsense was applied: 2 char country code + 2 char site code etc etc ad nauseam. Followed by my absolute pet hate: 01. Oh so you might need 99 domain controllers? Yes you might, but not on one site.
Let’s face it, it is mostly AD admins who don’t get hostnames. I blame MS - their docs and blogs strive to be … authoritative or at least look so. An entire generation (possibly two) of sysadmins have been sold up the river by MS and their wankery.
It doesn’t matter if you get the result you want. The important thing is you have choice and that what you have chosen … works!