MMM-Domoticz-ext: interact with Domoticz

goedh452

@najtram Looks nice!

I’ll look into the zero-bug.

najtram

Do you have an idea for a flame symbol instead of the text Gas. Maybe with Fontawesome?

goedh452

The name of the device in Domoticz is used. Would you like me to built an option to use a custom header with FontAwesome?

steps39

@najtram great fix, how did you fix the Zero state and change the symbols, could you upload as an issue on github?

steps39

@najtram I hacked it by changing line 933 of MMM-Domoticz-ext centreZero from true to false, so I guess more of a fork or feature request to have the option to change the gauge style rather than a bug.

goedh452

@steps39

I’ll have a look at the requests and zero state bug later this week or this weekend. Can you describe them zero state bug in more detail? Is it that when the value is zero the gauge is not displayed (correctly)?

steps39

@goedh452 I think that for both me and possibly @najtram we really want to have options which you haven’t built into your code.
So, just speaking for me, the zero bug isn’t really a bug, but I want the gauge to start with zero as the bottom anti-clockwise, as I don’t want to display negative values only positive values, as @najtram shows in his figure
Schermafbeelding 2021-04-12 om 20.08.54.png
I have got the same display of the gauge by change line 933:

MMM-Domoticz-ext.js:933:    centerZero: true,

to:

MMM-Domoticz-ext.js:933:    centerZero: false,

It would nice to have an option to choose where zero would be, and possibly a number of other options around size. But would this just make it too complex and should I be using a different tool rather than MagicMirror?

So having discovered Dashticz I am wondering whether I wouldn’t be better off using Dashticz as a lot of the information I want to display comes directly from Domoticz.

goedh452

@steps39

Thanks for the explanation. I’ll make some modifications and let you now.

There are several options for the gauge, but they I didn’t implement it in such a way that they can be set in the config. For instance line thicknesses, etc.

Dashticz is also a good option. In some ways it is more flexible, but in other ways not. But I would definitely give it a try!

najtram

@goedh452 & @steps39

The “problem” with the centerZero value is relative.
I tried the gaugeEnergyMinValue in the config.js and assumed this should do the trick. (So with a min value of 0 or -1 and a max value of 3000).

That didn’t work. So somehow I’m not able to point out what the bug is, but I expected it to work diffrently because of the gaugeEnergyMinValue.

My solution was exactly as @steps39 described in his previous post.

And about the gas flame, I’m also not sure, but maybe a default replacement for default text? So water to a water sybol, gas to a flame, etc. But this is not a big issue, I’m already used to it like this. Looks nice!

najtram

@steps39

Symbols are unicode symbols in the names of the domoticz devices…

eg: Unicode Character “⚇” (U+2687)

Just edit the devicename in Domoticz…

goedh452

@najtram & @steps39

I made some changes to the code:

When min value for the gauge is < 0 then 0 is centered. Otherwise zero is not centered.
Made the config for utility gauges much more flexible

It is now possible to set config options for each individual gauge, including width, line width, marker width and marker color. Also a symbol of font awesome can be used.

Please download the latest code from GitHub. You will also have to modify the config file. I updated the readme accordingly. My config for utilities is now:

utilities: {
  utilityLabel: "Gas - Water - Licht",
  showLabel: true,
  devices: [
    {
       idx: "304",
       deviceHeader: "Elektriciteit",
       counterTodayLabel: "Vandaag",
       gaugeMinValue: -3000,
       gaugeMaxValue: 3000,
       gaugeAppendText: "Watt",
       gaugeWidth: 200,
       lineWidth: 16,
       markerWidth: 16,
       markerColor: "#F4D03F"
     },
     {
       idx: "329",
       deviceHeader: "Gas",
       useHeaderSymbol: true,
       headerSymbol: "fire",
       counterTodayLabel: "Vandaag",
       gaugeMaxValue: 25,
       gaugeAppendText: "m³",
     },
     {
       idx: "1614",
       deviceHeader: "Water",
       useHeaderSymbol: false,
       headerSymbol: "water",
       counterTodayLabel: "Vandaag",
       gaugeMaxValue: 1500,
       gaugeAppendText: "liter",
     }
   ],
 },

Which results in:

Schermafbeelding 2021-04-17 om 13.13.36.png

Schermafbeelding 2021-04-17 om 13.47.39.png

najtram

@goedh452 said in MMM-Domoticz-ext: interact with Domoticz:

Great work! Small detail… The Watt vs the kWh? Where did this option go?

See screenshot.

Also a minor detail. The font used for Watt, and Today, isn’t the default font the MMM uses. Is there a reason for not using that default font?

Again, thanks for your great work!

Schermafbeelding 2021-04-19 om 21.32.58.png

goedh452

@najtram

You are right. I overlooked that. I added an option ‘counterTodayAppendText’ which defaults to ‘kWh’. So you can set it yourself in the config or leave it a ‘kWh’. Latest code is on GitHub.

goedh452

@najtram

Fixed the font. Set to default MM font in GaugeMeter.js.

Thanks for the suggestions!

najtram

@goedh452

These are great improvements!

-kWh is working
-Font is working partially. Actual usage is MM-font, but daily totals still looks like Arial…

goedh452

@najtram

Right again! All fonts should be the default MM font now.

Thanks for the feedback.

najtram

@goedh452

Thanks for making this adjustment.

I am currently having problems. I was curious about your update. So I updated the module with the MagicMirror remote module. (there is an update in the menu.)
Somehow I updated my entire mirror.
⮑ Guess what! → MMM-Domoticz-ext no longer works. (Another calendar module is now also “broken”.) But for the MMM-Domoticz-ext I received this error.

So again, I’m asking for your help. But I can imagine this could be a big thing. Thanks in advance if you can manage to fix this!

pm2 logs mm ↓

0|mm  | [23.04.2021 21:58.08.734] [ERROR] 
0|mm  | ERROR! Could not validate main module js file.
0|mm  | [23.04.2021 21:58.08.796] [ERROR] 
0|mm  | SyntaxError: Error parsing /home/pi/MagicMirror/modules/MMM-Domoticz-ext/package.json: Unexpected token } in JSON at position 669
0|mm  |     at parse (<anonymous>)
0|mm  |     at readPackage (internal/modules/cjs/loader.js:269:20)
0|mm  |     at readPackageScope (internal/modules/cjs/loader.js:294:19)
0|mm  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1164:17)
0|mm  |     at Module.load (internal/modules/cjs/loader.js:992:32)
0|mm  |     at Module._load (internal/modules/cjs/loader.js:885:14)
0|mm  |     at Function.f._load (electron/js2c/asar_bundle.js:5:12738)
0|mm  |     at Module.require (internal/modules/cjs/loader.js:1032:19)
0|mm  |     at require (internal/modules/cjs/helpers.js:72:18)
0|mm  |     at Class.loadModuleDefaultConfig (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:313:30) {
0|mm  |   path: '/home/pi/MagicMirror/modules/MMM-Domoticz-ext/package.json'
0|mm  | }

goedh452

@najtram

Wow, that’s strange. It seams like a more strict interpretation of the code in package.json. I validated the JSON again and made one minor change. Could you pull the code from GitHub and try again? Really hope this solves the problem.

najtram

@goedh452