I suspect that INfluxDB is looking at the data and trying to make the best determination based on what is in it. This is part of the problem with community drivers that have custom attributes vs standardized attributes as defined by capailities.
This is also why I asked to see what the calls were that worked vs didn't work. There may be a change in parts of the data stream that make it incompatiable at times. Like as you pointed out in this case going from Double Number type value to a string value. This would take time to analyze what the driver is passing as events to see if the data type information is inconsistant.
ohh I think i see whats going on now: if you look at the device events that is polling data every 5 mins and sometimes the attribute reports actual number and sometimes just says "N/A" instead of "0.0"
No, I haven't seen anything like this on my instances. I have alarms that go off from the Grafana side if the data goes stale.
It sounds like cron dumped everything. This could come from a memory issue. I have had an instance of a sudden out of memory situation on one of my hubs, which affected pretty much all the events on the hub at the time.
When you save the app (like enabling logging), it recreates the entire state, subscriptions and timers, so that it resumed publishing definitely makes sense.
If you haven't already rebooted the hub in question, I would recommend doing so.
InfluxDB does not allow mixing of types in a column. String, double or integer, you have to pick one and stick with it. If you want to log this data as a numeric value to InfluxDB, you will need to modify the driver to either use zero as the unknown value, or simply not post an event if the value is unknown. There are arguments in favor of either approach, but my personal preference is "don't post it if you don't know it."
I have a rule that restarts the hub at low memory and it did triger last night becuase though the hub recovered the memory hit never really did. Strangely though there wasn't a memory issue when this occured and it wasn't everything. Just a few device drivers and INfluxDB Logger. It was far from everything. It was more like jobs that ran in small interval couldn't schedule their next run so they got stuck and didn't complete there method they were running
I suspect that Hub just kind of lost it's brain about how to scedule jobs. All of the things that failed depend on the previous run to complete to schedule the next one in a way.
How are you getting the memory value? If cron dumped, things like Hub Information are not going to update.
FWIW, what I saw on my memory event was that almost all events just stopped processing, including the Hub Information driver. The only indication I had of a memory issue was a system alert.
Well i should clarify there was no memory issue before it occurred, or more simply it wasn't low. I am not saying something could have just killed the hub memory momentarily. just that leading up to that point the memory looked fine and it had enought that i am suprised something would have caused a memory problem. Anything is possible and clearly something happened.
Because I had two occasions with this recently I updated the InfluxDB Logger to include some notification functionality. I have created a pull request to add my edits into the main repo.
Basically, yes, but the login method is different so you will want to make an API token in Influx as well.
Or, Influx has upgrade / migration docs which if done correctly you will keep your data and it will create legacy DBRP mappings so any existing integrations will work with the same credentials.
I just tried making my first database as I was used to in v1, and holy cow they changed everything. I wasn't using any authentication before with any of my stuff.
Just FYI if you have any existing dashboards tied to Influx v1, you will need to create a DBRP mapping and point your existing datasource in Grafana to it so they keep working. The new v2.x Flux language is totally different for the queries in the dashboards.
Think there's really much reason to migrate? My main reason was, I'm spinning up a new VM and starting fresh because I'm having some issues with my existing setup. Plus it's running on an out dated version of ubuntu.
I figured now was the time to migrate, but the more looking I do the more I see folks talking about influx v2 nearing it's end of life with v3 coming out.