node-red-contrib-influxdb3 1.0.2 → 1.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -52,6 +52,8 @@ A configuration node that stores connection details for your InfluxDB v3 instanc
52
52
  - **Host**: Your InfluxDB v3 host URL (e.g., `https://us-east-1-1.aws.cloud2.influxdata.com`)
53
53
  - **Token**: Your InfluxDB v3 authentication token
54
54
  - **Database**: The default database (bucket) name
55
+ - **Verify TLS**: Toggle TLS certificate verification (unchecked sets `NODE_TLS_REJECT_UNAUTHORIZED=0`)
56
+ - **CA Cert Path**: Optional filesystem path for a custom root CA (`NODE_EXTRA_CA_CERTS`)
55
57
 
56
58
  ### InfluxDB v3 Write Node
57
59
 
@@ -344,6 +346,13 @@ Simply reference them in the Node-RED UI using `${INFLUX_HOST}` syntax (if using
344
346
  - Check that your token has write permissions for the database
345
347
  - Ensure the database name exists in your InfluxDB v3 instance
346
348
 
349
+ ### TLS / Custom Certificates
350
+
351
+ If you are connecting to a local InfluxDB v3 instance with a custom certificate:
352
+
353
+ - Set **CA Cert Path** in the config node to the PEM file containing your root CA. This sets `NODE_EXTRA_CA_CERTS` for the Node-RED process.
354
+ - As a last resort, disable **Verify TLS** to set `NODE_TLS_REJECT_UNAUTHORIZED=0` (this disables TLS verification globally for the process).
355
+
347
356
  ### Data Not Appearing
348
357
 
349
358
  - Check the node status - it should show "written" briefly after successful writes