Kube name to sensor

by gebhardm on

The local visualization currently lacks a capability to detect a kube's name to show it. Digging into the code, there should be a corresponding configuration that also is published as mqtt topic: https://github.com/flukso/flm-ui/blob/flm03/app/scripts/controllers/kube...

  1. var kube = JSON.parse(msg.payloadString);
  2. $scope.kube.data.push({
  3. ...
  4. name: kube[kid].name,
  5. ...
  6. });

Sadly this seems not set as an example message shows - refer to https://github.com/gebhardm/flmlocal/issues/6
  1. {
  2.         "main" : {
  3.                 "encryption" : 0,
  4.                 "max_nodes" : 30,
  5.                 "pair_group" : 212,
  6.                 "null_key" : "0123456789abcdef0123456789abcdef",
  7.                 "cache" : "/usr/share/kube",
  8.                 "collect_group" : 174,
  9.                 "key" : "key-guid"
  10.         },
  11.         "1" : {
  12.                 "sw_version" : 1,
  13.                 "enable" : 1,
  14.                 "hw_type" : 19218,
  15.                 "hw_id" : "hw_guid"
  16.         }
  17. }

Hmm, so, bug or feature request?

‹ v246: Updated FLM local visualization Upcoming FLM v3 - features, changes, points-of-interest ›
gebhardm's picture
gebhardm |

The name in this case was just not set; thus neither bug nor feature, but missing configuration. eot