No worries @inetjnky, if you've got an alternative in your QNAP NAS that makes perfect sense. I didn't have an "always on" server I could really use and looking through a lot of the posts for some of the solutions I was after, many of them were developed and documented around running on a rpi.
I haven't read much on Node Red, but am I interested to learn more sometime soon. Given the recent and continual discussion on this topic in the community I'm sure you'll find a way to accomplish what you are after.
I can also sympathize with "life getting in the way", perhaps not to the same scale, but I know how it can drain our time and enthusiasm at times. All I can suggest is to keep chipping away at it and keep active on the community as a way to keep up on what people are doing and potential answers to what you want to do.
You can read about how I am using my QNAP NAS with Hubitat in this article. I just updated it this morning with the most accurate information including a link to my flow to download hub backups.
As mentioned in the above article this is what I am doing. It is very easy to setup.
I fixed my 408 problem by using IP number instead of hostname in the Host-field of the InfluxDB Logger app configuration. Turns out my hub uses Google DNS instead of the local DNS servers I pass in the DHCP reply, so it is unable to convert my local "mon" server name to the correct IP (in my case 10.0.0.19). Why the app code gets a 408 when it hasn't even sent the POST-packet in the first place is probably down to the app not testing async http library errors properly. YMMV
I also fixed my 408 problem this afternoon. I use HTTPS in front of my influxdb instance, and the InfluxDB Logger has a hardcoded http:// in the postToInfluxDB function. I stripped out that part, and added https:// to the Host field, and it started working for me.
