I gave this as sample: organization_name: myc_org
update to your organization, when you setup indluxdb 2
Yes also the deletion of fields/nodes/gateway are not possible with the interface, it remains in memory, I am obliged to go in the yaml file and delete them
I will check this
I'm going to take a little vacation.
Enjoy your vacation 
@JeeLet can you share your database configuration?
@JeeLet I tried influxdb2 locally and work ok.
once you setup influxdb2 in your host, setup a API TOKEN for mycontroller.
Details are in https://docs.influxdata.com/influxdb/cloud/security/tokens/create-token/#manage-tokens-in-the-influxdb-ui
metric database configuration will be looking like this,
metric:
disabled: false
type: influxdb
uri: http://192.168.122.1:8086
token: uBykOQ_17_m-KMdBkWa_UiTNpBViQH***akY_Rec_49kV0gLg_zZZw==
username:
password:
organization_name: myc_org
bucket_name: myc
batch_size:
flush_interval: 5s
@JeeLet can you show your metric configuration? hide credentials
sample configuration: https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/#sample-of-cloud-influxdb-configuration
@NielBierman My guess you have downloaded wrong arch executable.
if your OS is x86_64 download mycontroller-server-*-linux-amd64.tar.gz
To know OS arch run the command: uname -m
@vidpix welcome to MyController
if you use labels as filter append labels. as prefix of the key.
samples: labels.ms_node_id, labels.ms_sensor_id
in the filter key you can choose anything. you can easily understand if you see yaml view of a field.
@JeeLet said in Grafana install:
a new hardware base, maybe an Odroid-N2 !?
I have not owned Odroid-N2. But it should work
@JeeLet I missed this thread somehow
I don't understand the difference between StorageDB and MetricDB
https://v2.mycontroller.org/docs/overview/architecture/#storage-database
you say "You can also use influx 2.x. MyC supports influx 2.x"?
Yes, influx 2.x supported, more configuration details on https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/#influxdb
on a next new installation I switch to the influxDB-2 version I don't have anything to modify in mycontroller ?? .... I may try ??
You have to update the configuration file as mentioned on the above link
For the last test with grafana, the "mc_gauge_float_data" values work but not the "mc_binary_data" numbers
(maybe I'm wrong in the config)
binary data is in the form of true or false.
@JeeLet You can go with influx 2.x as well. MyC supports for influx 2.x
@JeeLet for now MyC do not delete influx data, when you remove your sensors from MyC. But it is required. I will add this feature soon if possible.
@JeeLet some special cases you need 2mqtt. For example you want to share your USB GW for MyC and other software (via mqtt). If you are using your USB GW only with MyC. 2mqtt is not required.
2mqtt creates a mqtt communication to your USB GW
@JeeLet can you please explain the requirement? It will be easier to guide.
@JeeLet Happy New Year!!
Great! Finally you got it.
Gw and stick to the controller, it does not do much, it relays, it is an intermediary.
Couldn't we use the Gateway-Usb to monitor the nodes ?
of their values ? of their states ?
It is possible to fetch node/sensor values. But it is ok when you have few nodes. If your node network grows, this eats lots of your RF bandwidth. IMO, it is unnecessary to poll the values. We have a push mechanism (node sends data to MyC) and in this situation, It is not a good idea to implement pull mechanism as well (MyC asks data from from each node).
@JeeLet MyController v2 operates like event based. It means it receives the data from the node or whatever and updates into the database with the timestamp of the data. On a restart of MyC server the data will be loaded again from database. So no change on the data/value, until it receives new value from that node.
The node down status maintained by MyC. If there is no data/heartbeat received from a node for a specified time. MyC assumes that the node is down and marked as down.
@JeeLet It is not a ghost value. You can note the timestamp (Last Seen) the value received 20 hours ago after that data not received. So it is a 20 hours ago data.
Please let me know if it is not clear
changes in start script introduced from this commit
everything updated in the script mcctl.sh
if you use manual binary execution, you should replace -config with --config
@JeeLet yes, only yaml based backup from old version will not work with the new version. I would recommend you to take json backup before moving to the new version.
Hi,
This is applicable if you are using MyController v2.
Recently(02-Dec-2022) in the source code I have updated the yaml keys to sync with json keys. This leads existing yaml backup and yaml memory storage invalid.
json backup with your existing MyController v2json backup. all done. You have all your existing data in the new system@JeeLet I have not tried with Grafana. I will give a try and update you