How many devices do you guys have enabled? I just tried this again today and my zigbee radio went offline. Could be incidentally but it happened shortly after adding lots of devices to Influxdb app.
Maybe consider adding a switch to disable the app to quickly troubleshoot if the app is causing problem without having to uninstall/reinstall everytime.
I've got in the region of 150 datapoints heading to it. I've had the hub lock up a couple of times, but not frequently, and I've no way of knowing if the logger is related.
I have about 20 devices reporting data to InfluxDB from my Prod hub, and another 20 on my Dev hub.. I am trying to only send the data I truly want to visualize. I have 2 Hubitat hubs, both running the InfluxDB Logger App. Both are sending data to the same InfluxDB database. I haven't had any issues since deploying the async version, but it is really too early to tell if InfluxDB is even the cause of my very infrequent Hub lockups.
As an aside to this... My guess is that memory exhaustion (of some variety - don't know enough about how the hubitat innards work to know more) is probably what's killing these environments, as the linux oom-killer that kicks in when there's not enough memory for the platform is pretty indiscriminate in terms of which app it stands on.
So we then get into user-apps and whether they're causing the problem or not. I've written a few bits and pieces, and released them, but I'm entirely ignorant of exactly what practices are likely to cause excessive memory usage (barring deliberately trying to allocate enormous objects, I guess), or, to be honest, how it's possible to profile code or similar to work out if you're a bad actor.
Hubitat staff - is there any guidance you can provide on the subject? I presume you've got instrumentation for your own code that helps you to track this stuff down - is any of that something you could make available to us mere mortals? It's one of the challenges for developing for this platform that you start out in an incredibly bad place - for most of us, our development, test, staging, and production platforms are all the same thing - if you were developing in any sort of professional setting, you'd be out on your ear for even SUGGESTING such a thing.
I do accept that I could simply purchase a second hub... but to be honest... without better instrumentation and probably a good simulator and test rig, it doesn't really solve the problem, either.
I'm sure the internet has various bits of requirements, but given that there's a few components to this, and somebody has already gone to the effort of packaging it, I'd recommend the docker container for it:
There were some great links above - did you try them and have issues?
They're both very popular platforms, and a web search for the OS you prefer plus 'how to' or 'tutorial' will get you very detailed instructions.
I'd say - try that, and see how it goes.
It's a bit intimidating for a non-programmer perhaps but these are definitely within reach for anyone who's wiling to mess about with home automation.
Briefy, I installed both on MacOSX in about 15 minutes. I don't remember a single issue at any point. They can be run with docker, but that's not necessary. I didn't bother, figuring it'll be easy to do it over if I need to. But docker can also be the easy route, because someone has probably prepared a docker container all set up with all of the above for you, too.
Above all, be willing to give it a try and see. You can't really hurt anything and it gets easier every time you screw it up and have to start over!
I believe it'll install on Windows, too, but Docker is an easy way for sure. If you're not into Linux already, RaspPi could be an additional learning curve to avoid - and frankly, Windows is frequently a speed bump, too. There are scads of docker tutorials - some in this thread!
Another option is just to try it in a Virtual Machine with something like VirtualBox. A bit more resource intensive but would allow you to get comfortable and test it.
If it’s not for you, it’s simple to uninstall both the virtual machine and VirtualBox.
Just got Initial State working perfectly with Hubitat using their DIY Smartthings app. Not much in there as I'm still porting from ST, but worked great. And IS now has a free tier... =)