InfluxDB plugin

Posted on
Mon Oct 16, 2017 11:53 am
smurfless1 offline
User avatar
Posts: 34
Joined: Sep 23, 2015
Location: Round Rock, TX

Re: InfluxDB plugin

YOUR DASHBOARD IS SO MUCH COOLER THAN MINE! Teach me sensei!

I merged his changes so right now both forks of this should be either identical or similar. Thanks!

I'm going to suggest a couple things for the sake of simplicity for future users. It's not reasonable to have to modify the system python like I do now, and now that I -have- a better way, I'm going to streamline that as best I can. Meaning:
1. I'm going to suggest we move to the JSON Broadcaster Plugin coupled with the script mentioned in an above post, which I'll put a proper forum together for.
2. I'll do some cleanup to make it easier to set up, start and stop it with the system using standard Mac launch stuff, and so on.
3. We should REALLY get some cool dashboard samples, because seriously, that is so much better than my hacks.
4. Once all that is done we can deprecate this one that is just a little too fiddly to set up.

Be patient, this is a labor of love for me. I just tinker when the kids haven't exhausted me.

db

Posted on
Mon Oct 16, 2017 12:04 pm
Colly offline
Posts: 216
Joined: Jan 16, 2016

Re: InfluxDB plugin

smurfless1 wrote:
2. I'll do some cleanup to make it easier to set up, start and stop it with the system using standard Mac launch stuff, and so on.
3. We should REALLY get some cool dashboard samples, because seriously, that is so much better than my hacks.
Be patient, this is a labor of love for me. I just tinker when the kids haven't exhausted me.

Looking forward to it. I've plenty of patience too.

Posted on
Thu Nov 23, 2017 3:49 pm
Asconasny offline
Posts: 134
Joined: Jan 16, 2015

Re: InfluxDB plugin

Hi.
Trying your plugin,

i keep getting this error:
Code: Select all
 InfluxDB Plugin Error           Error in plugin execution ServerReplacedElem:

Traceback (most recent call last):
  File "plugin.py", line 134, in deviceUpdated
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 151, in diff_to_json
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 140, in to_json
  File "<string>", line 1, in <module>
NameError: name 'boolean' is not defined


Any clue whats going on?

Posted on
Tue Nov 28, 2017 3:58 am
Juju offline
User avatar
Posts: 108
Joined: Aug 31, 2011
Location: Toulouse - FRANCE

Re: InfluxDB plugin

Hello smurfless,

I'm interested to set-up influxdb + grafana to work with Indigo.
By reading this topic, I understand you suggest to use JSON brodcaster plugin + the associated script instead of the initial plugin.
It's quite easy to install and set-up the plugin, but more complicated to set-up the script.
Could you give me more detailled information ?

Julien

Posted on
Mon Dec 18, 2017 11:07 am
scs offline
Posts: 25
Joined: Nov 28, 2014

Re: InfluxDB plugin

Hey yall,

I have a number of devices that i'd like to graph (my goals are quite simple at the moment. maybe graph the NOAA temp and wind, the indoor and garage temps, and the electrical use from the breaker box sensors).

I installed the latest from GitHub and that went fine, InfluxDB appears to be collecting data.
I installed the latest Grafana on my MacBook Pro, and simply point it to the Indigo server... I loaded the 2 sample dashboards, and fiddled with the queries, but I have not been able to get any output in my graphs ...and I think most of the problem is , I have no idea what all the values in the database are ...

edit: After scanning through the raw data files, it was able to get my bearings on the database schema and select the appropriate data from the tables ... resulting in : [see attachment]

Thanks Smurfless, pretty cool.
Attachments
Screen Shot 2017-12-18 at 4.49.31 PM.png
Grafana dashboard
Screen Shot 2017-12-18 at 4.49.31 PM.png (299.26 KiB) Viewed 711 times

Indigo 7 w/ Insteon and Z-Wave lights and outlets
Security integration.
Energy monitoring

Posted on
Thu Jan 18, 2018 10:05 am
dduff617 offline
Posts: 391
Joined: Jul 05, 2006

Re: InfluxDB plugin

I'm wondering if there are any active users of InfluxDB + Grafana + Indigo out there? ...Is this forum is still the right place for discussion of that particular trio?

My situation: I'm getting started. I have influxDB installed. Have the InfluxDB plugin installed and working.

From some earlier communication in this thread, my first question is whether using the InfluxDB plugin is still considered the latest/best way of getting data out of Indigo vs. broadcaster/receiver components. I didn't see any specific instructions for other approach, so I'm still using the plugin, however there are some patches/improvements discussed here that do not seem to be present in the version that I'm using (v0.5.4).

I've got some promising early results in Grafana, but right now, I have hit a hitch attempting to plot some thermostat data. I have a few Nest thermostats and have successfully plotted temperatures and states from them. However, I also have an Insteon thermostat, and I can't seem to find the right way to plot the heat set point, current temp, etc. from this device. There are lots of fields that look like they might be correct ones, examples: state.heatSetpoint.num and others, but they don't seem to yield any values that Grafana can use. Wondering if anyone else might have run into this...

I've tried manually querying influxDB from the command line, but the results are hard to interpret.... "Select * from thermostat_changes ..." produces records that are very "wide", i.e. they have 100's of fields and thus my debugging progress is slow. Anyone have suggestions on how to attack/debug this?

Thanks!

Posted on
Thu Jan 18, 2018 10:54 am
vtmikel offline
Posts: 322
Joined: Aug 31, 2012
Location: Boston, MA

Re: InfluxDB plugin

I still use my Influx / Grafana setup regularly.

I do not have a Insteon thermostat, but I have had the problem of "discovery" for the precise variable names regularly. I recommend looking at Chronograf. I use it to manually browse the data and see column names. It's very easy to set up, especially if you are using Docker for deployment of Grafana / Influx.

Another option is to use your SQL logging tool to discover the columns for the data. They should be the same in Influx.

Also be aware that if you use my fork of the plugin, I introduced a filtering method that could be preventing the data from getting to Influx. If you are using smurfless1's plugin, all data should make its way there.

Hope this helps.

Posted on
Thu Jan 18, 2018 11:52 am
scs offline
Posts: 25
Joined: Nov 28, 2014

Re: InfluxDB plugin

I still use mine as well....as I mentioned above, it’s a bit of a challenge getting a handle on the variable names.
The instructions for smurfless’ plugin have a one-liner that sends the entire database to /tmp/raw-data.txt which can be useful to browse and find values to query
Hope that helps
Last edited by scs on Thu Jan 18, 2018 1:46 pm, edited 1 time in total.

Indigo 7 w/ Insteon and Z-Wave lights and outlets
Security integration.
Energy monitoring

Posted on
Thu Jan 18, 2018 1:42 pm
Asconasny offline
Posts: 134
Joined: Jan 16, 2015

Re: InfluxDB plugin

hi vtmikel.

I use your fork, works good but im getting this error quite often in my log

Code: Select all
   InfluxDB Plugin Error           Error in plugin execution ServerReplacedElem:

Traceback (most recent call last):
  File "plugin.py", line 134, in deviceUpdated
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 151, in diff_to_json
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 140, in to_json
  File "<string>", line 1, in <module>
NameError: name 'boolean' is not defined


Any clue whats going on?

Posted on
Thu Jan 18, 2018 2:11 pm
vtmikel offline
Posts: 322
Joined: Aug 31, 2012
Location: Boston, MA

Re: InfluxDB plugin

Asconasny wrote:
hi vtmikel.

I use your fork, works good but im getting this error quite often in my log

Code: Select all
   InfluxDB Plugin Error           Error in plugin execution ServerReplacedElem:

Traceback (most recent call last):
  File "plugin.py", line 134, in deviceUpdated
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 151, in diff_to_json
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 140, in to_json
  File "<string>", line 1, in <module>
NameError: name 'boolean' is not defined


Any clue whats going on?


That looks annoying. I'll look into it and get back to you.

UPDATE: I haven't looked at the plugin, but in thinking about it, a work around might be trying to exclude the properties of the problematic device. Turning on debugging (proceed with caution) might give you a clue which device is causing the problem.

Posted on
Thu Jan 18, 2018 3:11 pm
Asconasny offline
Posts: 134
Joined: Jan 16, 2015

Re: InfluxDB plugin

Turned on debug, cant see what device is actually causing this.
But i do see that my Timed Device plugin is getting logged every second. i have multiple devices counting down, i really like that plugin but dont see the point in logging the countdown :)
Could it be that plugin causing this?

(Update)
Just had a look at the log.
Dont think its the timed device plugin due to the error shows up when there is no movement in the house. The timed devices is linked to several PIR´s around the house.



Code: Select all
"Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7009.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7009", "lastChanged": 1516308399.0, "id": 942948451.0, "displayStateValRaw": "01:56:49", "lastSuccessfulComm": 1516308399.0, "state.longStatusString": "01:56:49", "displayStateValUi": "01:56:49"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7008.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7008", "lastChanged": 1516308400.0, "id": 942948451.0, "displayStateValRaw": "01:56:48", "lastSuccessfulComm": 1516308400.0, "state.longStatusString": "01:56:48", "displayStateValUi": "01:56:48"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7007.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7007", "lastChanged": 1516308401.0, "id": 942948451.0, "displayStateValRaw": "01:56:47", "lastSuccessfulComm": 1516308401.0, "state.longStatusString": "01:56:47", "displayStateValUi": "01:56:47"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin Error           Error in plugin execution ServerReplacedElem:

[b]Traceback (most recent call last):
  File "plugin.py", line 134, in deviceUpdated
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 151, in diff_to_json
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 140, in to_json
  File "<string>", line 1, in <module>
NameError: name 'boolean' is not defined[/b]

   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7006.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7006", "lastChanged": 1516308402.0, "id": 942948451.0, "displayStateValRaw": "01:56:46", "lastSuccessfulComm": 1516308402.0, "state.longStatusString": "01:56:46", "displayStateValUi": "01:56:46"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7005.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7005", "lastChanged": 1516308403.0, "id": 942948451.0, "displayStateValRaw": "01:56:45", "lastSuccessfulComm": 1516308403.0, "state.longStatusString": "01:56:45", "displayStateValUi": "01:56:45"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7004.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7004", "lastChanged": 1516308404.0, "id": 942948451.0, "displayStateValRaw": "01:56:44", "lastSuccessfulComm": 1516308404.0, "state.longStatusString": "01:56:44", "displayStateValUi": "01:56:44"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]



Code: Select all
"Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.TxPowerReceived": 71.0, "name": "Beacon_Magnar_Watch", "state.Pi_2_Distance": 14.1, "lastChanged": 1516308610.0, "state.Pi_2_Time": "2018-01-18 21:50:10", "state.lastUp": "2018-01-18 21:50:10", "state.Pi_2_Signal": -23.0, "state.Pi_2_Signal.num": -23.0, "lastSuccessfulComm": 1516308610.0, "id": 1247531964.0}, "tags": {"folder": "piBeacon-OK", "folderId": "1708968173", "name": "Beacon_Magnar_Watch"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"name": "Pi_0_Teknisk_Skap", "state.Pi_2_Distance": 11.2, "lastChanged": 1516308610.0, "state.Pi_2_Time": "2018-01-18 21:50:10", "state.Pi_2_Signal": -80.0, "state.Pi_2_Signal.num": -80.0, "lastSuccessfulComm": 1516308610.0, "id": 1980934807.0}, "tags": {"folder": "piBeacon", "folderId": "122938458", "name": "Pi_0_Teknisk_Skap"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 6798.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "6798", "lastChanged": 1516308611.0, "id": 942948451.0, "displayStateValRaw": "01:53:18", "lastSuccessfulComm": 1516308611.0, "state.longStatusString": "01:53:18", "displayStateValUi": "01:53:18"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin Error           Error in plugin execution ServerReplacedElem:

[b]Traceback (most recent call last):
  File "plugin.py", line 134, in deviceUpdated
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 151, in diff_to_json
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 140, in to_json
  File "<string>", line 1, in <module>
NameError: name 'boolean' is not defined[/b]

   InfluxDB Plugin                 [{"fields": {"name": "Fuktighet - piBeacon-3 - Maria", "lastChanged": 1516308611.0, "state.lastSensorChange": "2018-01-18 21:50:11", "lastSuccessfulComm": 1516308611.0, "state.Pressure": "991.4", "id": 911065307.0}, "tags": {"folder": "piBeacon-PI", "folderId": "1893611973", "name": "Fuktighet - piBeacon-3 - Maria"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"name": "Temperatur - piBeacon-3 - Kryploft", "lastChanged": 1516308611.0, "state.Humidity": 71.0, "state.status": "11.8\u00baC/71%", "state.Humidity.num": 71.0, "state.lastSensorChange": "2018-01-18 21:50:11", "id": 64824930.0, "displayStateValRaw": "11.8\u00baC/71%", "lastSuccessfulComm": 1516308611.0, "state.Temperature": "11.8", "displayStateValUi": "11.8\u00baC/71%"}, "tags": {"folder": "00.Temperatur", "folderId": "1366538435", "name": "Temperatur - piBeacon-3 - Kryploft"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"name": "Temperatur - piBeacon-3 - Loftstue", "lastChanged": 1516308611.0, "



Code: Select all
"AlarmARMED2Bevegelse1min"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7172.0, "name": "Timerloftstuefilm2time", "state.timeLeftSeconds": "7172", "lastChanged": 1516308701.0, "id": 942948451.0, "displayStateValRaw": "01:59:32", "lastSuccessfulComm": 1516308701.0, "state.longStatusString": "01:59:32", "displayStateValUi": "01:59:32"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "Timerloftstuefilm2time"}, "measurement": "device_changes"}]
   InfluxDB Plugin Error           Error in plugin execution ServerReplacedElem:

[b]Traceback (most recent call last):
  File "plugin.py", line 134, in deviceUpdated
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 151, in diff_to_json
  File "/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB.indigoPlugin/Contents/Server Plugin/indigo_adaptor.py", line 140, in to_json
  File "<string>", line 1, in <module>
NameError: name 'boolean' is not defined[/b]

   InfluxDB Plugin                 [{"fields": {"energyCurLevel": 239.9, "name": "Bryter - Media - Stue", "lastChanged": 1516308701.0, "state.curEnergyLevel": 239.9, "lastSuccessfulComm": 1516308701.0, "id": 1517892937.0, "state.curEnergyLevel.ui": "239.9 W"}, "tags": {"folder": "2.05.Stue", "folderId": "1521890392", "name": "Bryter - Media - Stue"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 1.0, "name": "AlarmARMED2Bevegelse1min", "state.timeLeftSeconds": "1", "lastChanged": 1516308702.0, "id": 289007968.0, "displayStateValRaw": "00:00:01", "lastSuccessfulComm": 1516308702.0, "state.longStatusString": "00:00:01", "displayStateValUi": "00:00:01"}, "tags": {"folder": "Timers", "folderId": "102675553", "name": "AlarmARMED2Bevegelse1min"}, "measurement": "device_changes"}]
   InfluxDB Plugin                 [{"fields": {"state.timeLeftSeconds.num": 7171.0, "name": "Timerloftst

Posted on
Thu Jan 18, 2018 4:53 pm
vtmikel offline
Posts: 322
Joined: Aug 31, 2012
Location: Boston, MA

Re: InfluxDB plugin

I'm also an extensive user of the Timed Devices plugin. I created my fork of the Influx plugin to handle the filtering so that updates are not logged every second.

The lines creating problems for you in the plugin are lines that came from smurfless1's plugin and I haven't touched (and frankly he's a better python coder than I am, so I'm not sure how to fix them).

Here's what I recommend:
  • Make sure the plugin is in "include" mode in the configuration. I just noticed that the field is incorrectly labeled "Login Mode". Ha!
  • Set the "include globally" to something like the following. This is what I have set for mine: batteryLevel, state.batteryLevel, state.onOffState, state.hvac_state, onState, energyCurLevel, energyAccumTotal, value.num, sensorValue, coolSetpoint, heatSetpoint, state.ui_color_state
  • Make sure you have Global Property Manager plugin installed and enabled
  • In the Plugins Menu, go to the Global Property Manager, select "Manage Global Device Properties"
  • Select each of the devices that have preceded a error log and add a property called "influxExclStates". For the value, add "all"

Let me know how this works.

Posted on
Fri Jan 19, 2018 11:57 am
dduff617 offline
Posts: 391
Joined: Jul 05, 2006

Re: InfluxDB plugin

Great to hear there are some active users of Influx/Grafana/Indigo. In my short time experimenting thus far, I am much more satisfied with results I have bene able to achieve than with other Indigo plotting plugins.

Thanks for helpful input and suggestions. quick responses...

Thanks vtmikel, I had not previously heard of Chrongraf, but I will try it out. At this point anything that provides better visibility as to what's going on is a win for me. If I learn what the problem is that is preventing me from seeing any useful updates to my Insteon thermostat, I will post a followup.

Regarding timers - I had the same "problem" that others observed with plugins with the Timers and Pesters plugin which ships with Indigo, namely that with the default mode of "pass every state change of every device to influx", I would get >20 updates per second just from various timers counting down. I cut down the magnitude the problem of in my specific case by getting rid of a bunch of legacy timers that I no longer needed (e.g. for detecting missed daily heartbeats from leak detectors). Still, it seems that long term success and broader appeal of InfluxDB is going to require there to be to provide whitelist, blacklist or both for states whose updates should/should not get passed to InfluxDB.

Regarding which particular version of the InfluxDB/Indigo interface is most current or preferred or whatever.... I think this is a point of confusion for new users (like myself). Here are ones that I see referenced in this thread and quick comments about what i know about them -- owners, PLEASE provide corrections/updates to this or mark your versions as deprecated if appropriate:

smurfless1 original version - linked at the top of this thread. Lives in GitHub. Easy to install the indigo part. this has minimal config details and by default loads (almost?) all state changes for (almost?) all devices into Indigo. seems to do some extra work so that for states which are not actually numeric but which look like numbers, a additional state with name with ".num" added is created in InfluxDB alongside the original value, which tends to make things work better in Grafana. Creates four separate tables for variable, weather, thermostat, and device changes. Also makes Indigo folder data visible in Influx.

smurfless1 2-part version - Two plugins. Both in GitHub. Introduced in this post: viewtopic.php?p=145008#p145008. Splits the original plugin into two separate components and thereby solves some python dependency problems (?).

vtmikel modified version - Lives in GitHub under user "mlamoure". Seems to be based on original smurfless1 version. Adds patches that prevent dumping useless changes (like timers) into InfluxDB and to force a minimum update frequency for some states to address the issue of not knowing initial(prior) state for any given time interval that you want to plot in Grafana.

Questions:
Smurfless1, does your 2-part plugin supersede your original plugin, and therefore should the original now be considered obsolete? If so, perhaps it might make sense to edit the first post in the thread, as that is where new users are going to tend to look to download, as there is seems to be a convention elsewhere in some forums, where the link at the top of the introductory thread maintains a pointer to the latest/greatest version of the plugin under discussion. So in this case, that would cause a needless sidetrack for users.

Smurfless1, you mentioned in a post that folded in changes from multiple forks. Did these changes merge into your "2-part" plugins? And were the changes referred to the ones introduced by vtmikel? Does that mean that vtmikel's fork is now essentially obsolete?

Vtmikel, your most recent post seems to indicate that you are still using your forked version. Do you plan for this fork to live on and be used by others?

Vtmikel, you posted a link to picture of your dashboard, hosted on dropbox. FYI, I'm not able to see the image (404 error). I would love to see some examples of what other users are doing.

Perhaps when things settle down, it might make sense to create a sticky README post so users (like me) aren't left guessing about which versions are active vs. which are dead-ends. Also, in a few cases I was having a hard time telling which versions were being talked about in various posts to this thread.

Right now afaik, everything about using Influx and Grafana with Indigo is in a single thread (this one) which currently lives in the forums in User Contributions>Plugins, but it seems to me it might more naturally reside in "User Contributions>Open Source Plugins". Alternatively, perhaps smurfless1 or someone would like to officially "adopt" it and move it to their 3rd Party Developers>* location? Would be great to have a separate subforum and factor discussion into topics like installation, Indigo state changes and filtering, Grafana tips, tricks, and example dashboards, etc.

Posted on
Fri Jan 19, 2018 12:27 pm
vtmikel offline
Posts: 322
Joined: Aug 31, 2012
Location: Boston, MA

Re: InfluxDB plugin

I took a new screen shot and posted my dashboard. Available here: https://www.dropbox.com/s/9nho6p1ijqv1h ... e.png?dl=0

I am currently using my forked version of the plugin. I have no problems semi-supporting it the best that I can for others, which is why I posted it. My caveat is that smurfless1 wrote 90% of the code. I understand that smurfless1 may incorporate my contributions to his future versions.

Agree that we could certainly make improvements to make this easier! Thanks for the clarifying post for new users.

A word of warning for anyone considering this kind of setup - I find that Docker for Mac is very unstable. A while back, I moved my Grafana and Influx dockers to my Indigo Mac (previously was on my Synology but it was slowing my NAS down too much) and I have constant problems. I wrote a script to restart Docker 4x per day to combat the problems. The Docker project has not responded to my issue ticket (link: https://github.com/docker/for-mac/issues/2265). I had this problem on El Cap, Sierra, and High Sierra with clean installs. It is too bad, because Docker makes installing these components so easy.

Posted on
Sun Jan 21, 2018 1:01 pm
dduff617 offline
Posts: 391
Joined: Jul 05, 2006

Re: InfluxDB plugin

I wanted more ability to configure what does and doesn't get sent to InfluxDB, so was going to try working with vtmikel's fork.

I'm trying to use that version of the plugin now. I deleted the old plugin and installed this one: https://github.com/mlamoure/indigo-influxdb.

Maybe something weird is happening because I thought previously when running that version, I got a different configuration dialogue from the plugin that had some extra values - a field for filling in a list of included state names, and a minimum update frequency. However, now having just re-installed the plugin, I'm somehow seeing the old configuration dialog (without those additional settings). Any idea how that can happen? I tried completely deleting the old old plugin, re-downloading from GitHub and re-installing. Whah?? Am I misremembering having seen those settings previously? Was I dreaming?

I've not seen this kind of thing before, but could it possibly a side-effect of the two versions not following the same version numbering conventions? or perhaps they have identical version #'s?? Tried server restart to see if that would clean things up (I'm grasping at straws here). Did not seem to help.

Attempting to re-install the plugin, in see this:
Code: Select all
 Installing and enabling plugin InfluxDB Plugin v0.0.3
   Error                           ReloadPlugin() caught exception: FileIOError -- cannot move: destination file exists


Any idea what that means or how to fix it? I think I already tried completely deleting /Library/Application Support/Perceptive Automation/Indigo 7/Plugins/InfluxDB. Are there other cache or log directories that I need to clean out also?

Who is online

Users browsing this forum: No registered users and 0 guests