-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySensors naming scheme #10
Comments
hi @findnix thanks for being a member of MyController since the beginning. You have to rewrite your influx query. sample data from v2.
In the future we may add additional plugin to publish metrics data to the external database. |
Hi @jkandasa ! I always appreciated Your mapping from the IDs to the long names. Unfortunately this feature is gone. This "forces" me to realize an old idea to write a little wrapper for this. Either catching and rewriting the MQTT topics or simple inject "translated" events into influx. I've to think about now a bit more detailed ;-) I would be a pleasure to share the code with you on success. |
@findnix In v2 some changes on the name/id to make it more generic. I do rethink possibility for this in v2. and update if I get an great idea. |
Hello @jkandasa!
First of all I would like to thank you for your great work.
I use v1 since the beginning. Now it's time to move to v2. I welcome this because I have been using influx with telegtaf for a long time.
My request now: is it possible in influxdb (1.8) to get a naming scheme that matches the "external server" functionality of v1?
I have been using this form for a long time:
host=myController,gategatewayName=$gatewayName,nodeName=$nodeName,nodeEui=$nodeEui,sensorName=$sensorName,sensorId=$sensorId,variableType=$variableType,variableTypeId=$variableTypeId
Thank you and greetings from Austria
The text was updated successfully, but these errors were encountered: