You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I understand node-red-contrib-influxdb version right now, there is no way to provide InfluxQL Style querys (like "select * from iot") for InfluxDB2 database. I try ver1.x configuration but no succes "error no valide autorisation"
When I use a simple curl call from Linux Terminal and provide -t parameter with valid API Token all works fine with InfluxDB2 and InfluxQL style query.
Request:
please anhance node-red-contrib-influxdb to recive results for InnfluxQL style querys
provide configuration "Ver2 influxQL" in dropdown
provide field for API Token (as in vers2 Flux Style)
Many thanks in advance
BR J
The text was updated successfully, but these errors were encountered:
It's not clear to me how to do this with the Javascript Client Library library we use for accessing influxdb 2.x servers as mentioned in the README yet. It seems to support only flux queries? Suggestions are welcome.
With InfluxDb 3.x on the horizon, perhaps yet another client library is in the works. I'm again thinking it might be worth considering breaking this node down into multiple nodes for different versions, especially given that flux will be put into maintenance mode.
I wanted to share that I was able to run InfluxQL queries with InfluxDB V2. The key was to select the version "1.x" in the configuration node. However, this only works after creating the DBRP mapping and setting up a 1.x basic authentication.
As I understand node-red-contrib-influxdb version right now, there is no way to provide InfluxQL Style querys (like "select * from iot") for InfluxDB2 database. I try ver1.x configuration but no succes "error no valide autorisation"
When I use a simple curl call from Linux Terminal and provide -t parameter with valid API Token all works fine with InfluxDB2 and InfluxQL style query.
Request:
Many thanks in advance
BR J
The text was updated successfully, but these errors were encountered: