Posts made by jkandasa

@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.

@JeeLet

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.

Workaround to retain your existing data

• create a json backup with your existing MyController v2
• upgrade MyController v2
• restore the json 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

@JeeLet you can add influxdb.service as dependency.

can you add the following lines on mycontroller.service file and try on boot?

[Unit]
Requires=influxdb.service
After=influxdb.service

[Service]
Description=MyController V2
Type=oneshot
RemainAfterExit=yes
ExecStart=/opt/apps/mycontroller/mcctl.sh start
ExecStop=/opt/apps/mycontroller/mcctl.sh stop

[Install]
WantedBy=multi-user.target

@JeeLet can you stop and start the service manually?

systemctl stop mycontroller
systemctl start mycontroller

If it works you have to add influxdb as dependent service for MyController service.
My assumption: On boot influxdb is not ready and MyController service terminated

@JeeLet I am unable to reproduce this issue. If you are trying to access mycontroller from external system, enable the port 8080 and/or 8443 on your host firewall.

Service status

[root@fedora-vm ~]# systemctl status mycontroller
● mycontroller.service
     Loaded: loaded (/usr/lib/systemd/system/mycontroller.service; enabled; vendor preset: disabled)
     Active: active (exited) since Wed 2022-11-09 13:24:03 IST; 3min 28s ago
    Process: 3973 ExecStart=/opt/apps/mycontroller/mcctl.sh start (code=exited, status=0/SUCCESS)
   Main PID: 3973 (code=exited, status=0/SUCCESS)
      Tasks: 9 (limit: 4653)
     Memory: 34.4M
        CPU: 221ms
     CGroup: /system.slice/mycontroller.service
             └─ 3981 ./mycontroller-server -config ./mycontroller.yaml

Nov 09 13:24:03 fedora-vm systemd[1]: Starting mycontroller.service...
Nov 09 13:24:03 fedora-vm mcctl.sh[3973]: start command issued to the MyController server
Nov 09 13:24:03 fedora-vm systemd[1]: Finished mycontroller.service.

Access MyController server

[root@fedora-vm ~]# curl http://localhost:8080/api/status -v
*   Trying 127.0.0.1:8080...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> GET /api/status HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.82.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Vary: Accept-Encoding
< Vary: Origin
< Date: Wed, 09 Nov 2022 07:57:34 GMT
< Content-Length: 307
< 
* Connection #0 to host localhost left intact
{"hostname":"","documentationUrl":"","login":{"message":"Default username and password to login: \u003cb\u003eadmin\u003c/b\u003e / \u003cb\u003eadmin\u003c/b\u003e","serverMessage":""},"startTime":"0001-01-01T00:00:00Z","serverTime":"0001-01-01T00:00:00Z","uptime":0,"metricsDBDisabled":true,"language":""}

Verify MyController server is running

[root@fedora-vm ~]# ps -ef | grep mycontroller
root        3981       1  0 13:24 ?        00:00:00 ./mycontroller-server -config ./mycontroller.yaml
root        4111    3650  0 13:29 pts/1    00:00:00 grep --color=auto mycontroller


[root@fedora-vm ~]# tail -f /opt/apps/mycontroller/logs/mycontroller.log 
#   enabled: false                                                                                        #
#=========================================================================================================#

2022-11-09T13:24:04.127+0530	info	handler/service_listener.go:33	handler service filter config	{"filter": {"Disabled":false,"MatchAll":false,"Types":[],"IDs":[],"Labels":{"location":"server"}}}
2022-11-09T13:24:04.128+0530	info	gateway/listener.go:32	gateway service filter config	{"filter": {"Disabled":false,"MatchAll":false,"Types":[],"IDs":[],"Labels":{"location":"server"}}}
2022-11-09T13:24:04.130+0530	info	handler/handler.go:110	secure share directory included	{"directory": "mc_home/secure_share", "handlerPath": "/secure_share"}
2022-11-09T13:24:04.130+0530	info	handler/handler.go:115	insecure share directory included	{"directory": "mc_home/insecure_share", "handlerPath": "/insecure_share"}
2022-11-09T13:24:04.130+0530	info	listener/listener.go:32	web console direcory location	{"web_directory": "web_console"}
2022-11-09T13:24:04.130+0530	info	listener/listener.go:64	listening HTTPS/SSL service on	{"address": "0.0.0.0:8443"}
2022-11-09T13:24:04.130+0530	info	listener/listener.go:44	listening HTTP service on	{"address": "0.0.0.0:8080"}

@Yourry I have added patch to avoid empty secret. It will not be allowed in the latest release. you need to update your secret and passwords,tokens, etc., used in MyController server

@Yourry

• web_directory: web_console - used in binary installation
• web_directory: /ui - used in docker container

My config file that works (without the secret line):

I will check this and let you know

@JeeLet No change in the influxdb installation side. Change are in the MyController yaml

• Quick installation: https://v2.mycontroller.org/docs/installation/quick-installation/
• Backend Configuration: https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/