MMM-Domoticz-ext: interact with Domoticz

sdetweil

@najtram npm install xmlhttprequest

this is a side effect of not documenting the requirements, and depending on mm to supply them.

the Domoticz module should add this to their package.json

najtram

Thanks for this solution. To be clear my MagicMirror is working on a different Pi than the Domoticz Pi. So could you help me out with two hints.
1 should I install the xmlhttprequest in the MagicMirror Pi or the Domoticz?
2 in which directory should i execute this npm install ?

Thanks again, this looks promising!

goedh452

@najtram

You should install it on the pi which runs Magic Mirror. I’ll add a package.json later. That is the right way to do it indeed.

najtram

@goedh452
@sdetweil

Thanks for both your support. I excecuted it in the MagicMirror directory. And it is working!!! This is really awesome!

Thanks for the great module!

steps39

@goedh452 nice add-on thank you.

I am able to get simple things to work ok, but can’t get gauges to display. I assume the communication with my Domoticz server is all working, as number of lights on etc. gets displayed and there are no errors in the log for devices not being found. If I use a non-existent device or wrong type of device, then the Domoticz module just displays Loading.

Do I need another dependency for gauges?

Also having done a git pull to install package.json this causes Magic Mirror to error, but all is fine if I remove package.json

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 loadModule (/home/pi/MagicMirror/js/app.js:126:19) {
0|mm  |   path: '/home/pi/MagicMirror/modules/MMM-Domoticz-ext/package.json'
0|mm  | }
0|mm  | [05.04.2021 15:22.59.747] [ERROR]

I also get a git error, I don’t know if this matters or not:

0|mm  | [05.04.2021 15:36.09.261] [INFO]  Checking git for module: MMM-VoiceAssistant
0|mm  | [05.04.2021 15:36.09.263] [INFO]  Checking git for module: MMM-Domoticz-ext
0|mm  | [05.04.2021 15:36.10.881] [ERROR] Failed to fetch git data for MMM-Domoticz-ext: Error: block timeout reached
0|mm  | [05.04.2021 15:36.11.972] [ERROR]

Thanks, exciting package, a lot of options to make sense of along with the complexities of my Domoticz, having a heat pump there are lots of energies and temperatures that I would like to be able to monitor.

goedh452

@steps39

Which gauges are you trying to display, utilities or weather? I tested the utilities with energy monitors that are collected to Domoticz with a P1 USB cable. You too?

The module should autodetect the type and disregard types it doesn’t know. Maybe this mechanism isn’t working as it should be for the gauges. I’ll look into this.

Regarding the git-error: I added the package.json for the dependencies. I’m not very experienced with GitHub and more of a hobby programmer. I guess there is something wrong with the package.json. Any input is welcome!

steps39

@goedh452 thanks, my skill is also amateur, but I now know that there is no gauge dependency missing.

I have a whole range of energy values captured in my Domoticz - Owl current meter, Nibe heat pump, Solaredge PV panels, I guess none of them are the same type as your P1 USB cable (not something I use/have).

I guess I would really want a flexible gauge that I can use with a number of my Domoticz captured values, so your Javascript is a great inspiration/start to create such gauges.

I will fork your git and then if I actually create something it will hopefully add to your package. As a hobby not sure when I will get around it :-(.

goedh452

@steps39

You could send me the json result of you sensors and I’ll see what I can do. The result is obtained via this URL:

http://<IPADRESS_DOMOTICZ>:<PORT_DOMOTICZ>/json.htm?type=devices&rid=<IDX_DEVICE>

steps39

@goedh452 thank you very much, a couple of examples below.

My Owl device measures watts, but each time I change the batteries it get a new idx, so I use a Lua script in Domoticz to capture the values and post-process before displaying as a Solar below:

{
   "ActTime" : 1617792992,
   "AstrTwilightEnd" : "22:07",
   "AstrTwilightStart" : "04:07",
   "CivTwilightEnd" : "20:30",
   "CivTwilightStart" : "05:44",
   "DayLength" : "13:31",
   "NautTwilightEnd" : "21:16",
   "NautTwilightStart" : "04:59",
   "ServerTime" : "2021-04-07 11:56:32",
   "SunAtSouth" : "13:07",
   "Sunrise" : "06:21",
   "Sunset" : "19:53",
   "app_version" : "4.10717",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CounterToday" : "6.210 kWh",
         "CustomImage" : 0,
         "Data" : "39023.996 kWh",
         "Description" : "",
         "EnergyMeterMode" : "",
         "Favorite" : 1,
         "HardwareID" : 3,
         "HardwareName" : "DUMMY",
         "HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
         "HardwareTypeVal" : 15,
         "HaveTimeout" : false,
         "ID" : "00014179",
         "LastUpdate" : "2021-04-07 11:56:30",
         "Name" : "Solar",
         "Notifications" : "false",
         "PlanID" : "0",
         "PlanIDs" : [ 0 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "SubType" : "kWh",
         "SwitchTypeVal" : 0,
         "Timers" : "false",
         "Type" : "General",
         "TypeImg" : "current",
         "Unit" : 1,
         "Usage" : "1409.4 Watt",
         "Used" : 1,
         "XOffset" : "0",
         "YOffset" : "0",
         "idx" : "298"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

The raw Owl device returns 3 power readings, one from each current clamp:

{
   "ActTime" : 1617793340,
   "AstrTwilightEnd" : "22:07",
   "AstrTwilightStart" : "04:07",
   "CivTwilightEnd" : "20:30",
   "CivTwilightStart" : "05:44",
   "DayLength" : "13:31",
   "NautTwilightEnd" : "21:16",
   "NautTwilightStart" : "04:59",
   "ServerTime" : "2021-04-07 12:02:20",
   "SunAtSouth" : "13:07",
   "Sunrise" : "06:21",
   "Sunset" : "19:53",
   "app_version" : "4.10717",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 100,
         "CustomImage" : 0,
         "Data" : "506 Watt, 138 Watt, 1863 Watt",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 1,
         "HardwareName" : "RFXCOM",
         "HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
         "HardwareTypeVal" : 1,
         "HaveTimeout" : false,
         "ID" : "6700",
         "LastUpdate" : "2021-04-07 12:02:12",
         "Name" : "Owl",
         "Notifications" : "true",
         "PlanID" : "0",
         "PlanIDs" : [ 0 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : 7,
         "SubType" : "CM113, Electrisave",
         "Timers" : "false",
         "Type" : "Current",
         "TypeImg" : "current",
         "Unit" : 0,
         "Used" : 1,
         "XOffset" : "0",
         "YOffset" : "0",
         "displaytype" : 1,
         "idx" : "1286"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

goedh452

@steps39

Thanks! I’ll look into it. A quick glance indicates that the subtype of the solar device is ‘kWh’ and the module scans for a subtype ‘Energy’. This is easy to modify in the code. The Owl device is a bit more complicated since it has the data-attribute, but does not split this into 3 separate attributes.

I’ll let you know if I’ve something for you to test!