JSON request module

ELMAGO

I correct myself, it is displayed but thus, having created the custom.css file in css:

Here is my config file:

// AFFICHAGE

{
		module: "MMM-ValuesByNotification",
		position: "top_right",
		header: "TEMPERATURE MAISON",
		config: {
			updateInterval: 10,
			reuseCount: 100,
			addClassesRecursive: true,
			groups: [
				{
					items: [
						{
							notification: "TEMPSALLE",
							itemTitle: "Salle  ",
							classes: "withIcons",
							values: [
								{
									valueUnit: " &#176;C",
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
						{
							notification: "TEMPBUREAU",
							itemTitle: "Bureau  ",
							values: [
								{
									valueUnit: " &#176;C",
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
					]
				},
			]
		},
	},

wishmaster270

@ELMAGO
Today, with my notebook ready things are getting easier.
I styled the module like the example you provided…

Let’s look at the steps to do this now:

First we tell the itemWrapper? to display the items in rows and not columns and set the line height to the regular value 1.0` to avoid a great space in between:

.MMM-ValuesByNotification .vbn .itemWrapper {
  flex-direction: row;
  line-height: 1.0;
}

Next we tell the itemsWrapper to set a small space of 5px between the rows:

.MMM-ValuesByNotification .vbn .itemsWrapper:first-child,
.MMM-ValuesByNotification .vbn .itemsWrapper
{
  gap: 5px;
}

We then remove some margins of the title if items, remove the underlining and set the min-with to 60px to get a straight lining of the values:

.MMM-ValuesByNotification .vbn .itemTitle {
  margin-top: 0px;
  margin-bottom: 0px;
  min-width: 60px;
  text-decoration: unset;
  color: white;
}

If you do not like the gray border around the items you can remove it with:

.MMM-ValuesByNotification .vbn .groupWrapper {
  border-style: none;
}

If you copy all these contents to the MagicMirror/css/custom.css file and restore the original valuesByNotification.css you should the style of above.

ELMAGO

@wishmaster270
good evening
thank you for your return, for the config file I put back yours or mine is good? I would test this tomorrow morning, tonight it’s rugby.
good evening and thank you again

ELMAGO

@ELMAGO

Good evening,

I couldn’t wait…it’s almost great, I just have to find how to align the text on the left and the temperatures on the right.

Thank you very much for your help

wishmaster270

@ELMAGO
Do you mean something like this…

We first define a width for the most outer wrapper. I choose 200px but can adjust it to the value you want:

.MMM-ValuesByNotification .vbn .groupsWrapper{
  width: 200px;
}

Then we configure the next two deeper wrappers to expand to the maximum width:

.MMM-ValuesByNotification .vbn .groupWrapper,
.MMM-ValuesByNotification .vbn .itemsWrapper {
  width: 100%;
}

And we tell the itemWrapper to expand to maximum width and justify its content by putting space around the items equally:

.MMM-ValuesByNotification .vbn .itemWrapper {
  flex-direction: row;
  line-height: 1.0;
  width: 100%;
  justify-content: space-between;
}

The rest stays the same as before:

.MMM-ValuesByNotification .vbn .itemTitle {
  margin-top: 0px;
  margin-bottom: 0px;
  min-width: 60px;
  text-decoration: unset;
  color: white;
}

.MMM-ValuesByNotification .vbn .groupWrapper {
  border-style: none;
}

ELMAGO

@wishmaster270

Re Goodnight

It’s awesome, it’s exactly what I wanted.

Thank you so much.

ELMAGO

@wishmaster270

Hello

sorry to bother you again but is it possible to display an answer following the answer of the request.

example :
The JSON request returns false I would like to display “NON”

wishmaster270

@ELMAGO Sorry, but i do not understand exactly what you mean. You can override the “na” value which is the one displayed if no value could be parsed in the JSON.

The config option is:

naValue: "NON"

There might also be a chance to do add a valueFormat which checks for the “false” value in the JSON but that would be a little more complex and i need to know the exact format of the output.

ELMAGO

@wishmaster270
Hello

No, not al all.
the returned value will be “false” or “true” and I would like to replace it with “Non” or “Oui” in French.

wishmaster270

@ELMAGO
You can use valueFormat for this purpose.

valueFormat: "\"${value}\".replace(\"false\",\"Non\").replace(\"true\",\"Oui\")",

This will convert the value to a string (if needed) and replaces all “false” with “Non” and “true” with “Oui”.

ELMAGO

@wishmaster270

great, thank you.
Is there a “lexicon” with these commands?

wishmaster270

@ELMAGO
I added some to the [documentation] (https://github.com/Tom-Hirschberger/MMM-ValuesByNotification/blob/main/doc/value.md) of the module.
As there can be used any build-in JavaScript function in valueFormat there are nearly endless possibilities.

ELMAGO

@wishmaster270

good evening,

I tested the replace function:

{
		module: "MMM-ValuesByNotification",
		position: "top_right",
		header: "INFORMATION M&#201;GANE",
		config: {
			updateInterval: 300,
			reuseCount: 100,
			addClassesRecursive: true,
			valueFormat: "\"${value}\".replace(\"false\",\"Non\").replace(\"true\",\"Oui\")",
			groups: [
				{
					items: [
						
						{
							notification: "AUTBATTMEGANE",
							itemTitle: "Autonomie  ",
							values: [
								{
									valueUnit: "&#160;Km",
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
						{
							notification: "BATTMEGANE",
							itemTitle: "Charge batterie  ",
							values: [
								{
									valueUnit: "&#160;%",
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
						{
							notification: "PLUGMEGANE",
							itemTitle: "Voirture branch&#233;e ",
							classes: "withIcons",
							valueFormat: "\"${value}\".replace(\"false\",\"Non\").replace(\"true\",\"Oui\")",
							values: [
								{
									
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
						
					]
				},
			]
		},
	},

But unfortunately it doesn’t work.

Would you know why?

Thanks

wishmaster270

@ELMAGO As valueFormat settings further down in the hierarchy override setting further up you only have to much valueFormat settings.

This config should do the trick:

	{
		module: "MMM-ValuesByNotification",
		position: "top_right",
		header: "INFORMATION M&#201;GANE",
		config: {
			updateInterval: 300,
			reuseCount: 100,
			addClassesRecursive: true,
			groups: [
				{
					items: [
						
						{
							notification: "AUTBATTMEGANE",
							itemTitle: "Autonomie  ",
							values: [
								{
									valueUnit: "&#160;Km",
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
						{
							notification: "BATTMEGANE",
							itemTitle: "Charge batterie  ",
							values: [
								{
									valueUnit: "&#160;%",
									valueFormat: "Number(${value}).toFixed(2)",
									jsonpath: "data",
								},
							]
						},
						{
							notification: "PLUGMEGANE",
							itemTitle: "Voirture branch&#233;e ",
							classes: "withIcons",
							values: [
								{
									valueFormat: "\"${value}\".replace(\"false\",\"Non\").replace(\"true\",\"Oui\")",
									jsonpath: "data",
								},
							]
						},
						
					]
				},
			]
		},
	},

ELMAGO

Hi @wishmaster270

I come back here, it will be simpler.

My code is:

//INFORMATION HOMEY EUFY

{
   module: "MMM-CommandToNotification",
   disabled: false,
   config: {
    updateInterval: 300,
    commands: [
     

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/ETATEUFY",
           timeout: 1000,
			
           notifications: [
            "ETATEUFY",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMSALLE",
           timeout: 1000,
			
           notifications: [
            "CAMSALLE",
            ],
          },

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMPALIER",
           timeout: 1000,
			
           notifications: [
            "CAMPALIER",
            ],
          },

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMARRIERE",
           timeout: 1000,
			
           notifications: [
            "CAMARRIERE",
            ],
          },

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMGARAGE",
           timeout: 1000,
			
           notifications: [
            "CAMGARAGE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMGAUCHE",
           timeout: 1000,
			
           notifications: [
            "CAMGAUCHE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMAVANT",
           timeout: 1000,
			
           notifications: [
            "CAMAVANT",
            ],
          },
{
      script: "/usr/bin/curl",
      args: "-s  http://192.168.100.244:3000/TEMPSALLE",
      timeout: 1000,
      notifications: [
       "TEMPSALLE",
       ],
     },

     {
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPBUREAU",
           timeout: 1000,
           notifications: [
            "TEMPBUREAU",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHELENA",
           timeout: 1000,
           notifications: [
            "TEMPCHELENA",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHLOUCA",
           timeout: 1000,
           notifications: [
            "TEMPCHLOUCA",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHALAN",
           timeout: 1000,
           notifications: [
            "TEMPCHALAN",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHPARENT",
           timeout: 1000,
           notifications: [
            "TEMPCHPARENT",
            ],
          },
{
      	script: "/usr/bin/curl",
      	args: "-s  http://192.168.100.244:3000/AUTBATTMEGANE",
      	timeout: 1000,
      	notifications: [
       	"AUTBATTMEGANE",
       	  ],
     		},

     {
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/BATTMEGANE",
           timeout: 1000,
           notifications: [
            "BATTMEGANE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/PLUGMEGANE",
           timeout: 1000,
			
           notifications: [
            "PLUGMEGANE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CHARGEMEGANE",
           timeout: 1000,
			
           notifications: [
            "CHARGEMEGANE",
            ],
          },

     ]
   },
  },

So I think it launches all requests at the same time, because my server which must answer crashes.

I wanted to split it like this:

//INFORMATION HOMEY EUFY

{
   module: "MMM-CommandToNotification",
   disabled: false,
   config: {
    updateInterval: 300,
    commands: [
     

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/ETATEUFY",
           timeout: 1000,
			
           notifications: [
            "ETATEUFY",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMSALLE",
           timeout: 1000,
			
           notifications: [
            "CAMSALLE",
            ],
          },

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMPALIER",
           timeout: 1000,
			
           notifications: [
            "CAMPALIER",
            ],
          },

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMARRIERE",
           timeout: 1000,
			
           notifications: [
            "CAMARRIERE",
            ],
          },

{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMGARAGE",
           timeout: 1000,
			
           notifications: [
            "CAMGARAGE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMGAUCHE",
           timeout: 1000,
			
           notifications: [
            "CAMGAUCHE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CAMAVANT",
           timeout: 1000,
			
           notifications: [
            "CAMAVANT",
            ],
          },
     ]
   },
  },

and

//INFORMATION HOMEY EUFY

{
   module: "MMM-CommandToNotification",
   disabled: false,
   config: {
    updateInterval: 300,
    commands: [
     


{
      script: "/usr/bin/curl",
      args: "-s  http://192.168.100.244:3000/TEMPSALLE",
      timeout: 1000,
      notifications: [
       "TEMPSALLE",
       ],
     },

     {
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPBUREAU",
           timeout: 1000,
           notifications: [
            "TEMPBUREAU",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHELENA",
           timeout: 1000,
           notifications: [
            "TEMPCHELENA",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHLOUCA",
           timeout: 1000,
           notifications: [
            "TEMPCHLOUCA",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHALAN",
           timeout: 1000,
           notifications: [
            "TEMPCHALAN",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/TEMPCHPARENT",
           timeout: 1000,
           notifications: [
            "TEMPCHPARENT",
            ],
          },


     ]
   },
  },

and :

//INFORMATION HOMEY EUFY

{
   module: "MMM-CommandToNotification",
   disabled: false,
   config: {
    updateInterval: 300,
    commands: [
     



{
      	script: "/usr/bin/curl",
      	args: "-s  http://192.168.100.244:3000/AUTBATTMEGANE",
      	timeout: 1000,
      	notifications: [
       	"AUTBATTMEGANE",
       	  ],
     		},

     {
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/BATTMEGANE",
           timeout: 1000,
           notifications: [
            "BATTMEGANE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/PLUGMEGANE",
           timeout: 1000,
			
           notifications: [
            "PLUGMEGANE",
            ],
          },
{
           script: "/usr/bin/curl",
           args: "-s  http://192.168.100.244:3000/CHARGEMEGANE",
           timeout: 1000,
			
           notifications: [
            "CHARGEMEGANE",
            ],
          },

     ]
   },
  },

But it doesn’t work, only the last element appears.

wishmaster270

@ELMAGO Hi,

thats right. The module does not support multi instance configurations.
You will need to copy the complete module folder and change some things to get it work.
But to me it looks like your server is stressed with the 16 calls straight after each other. So you do not need more parallelism but less.
So i will check if i can at a configurable delay after each command to stretch the time the calls get made to your server a little bit.

ELMAGO

@wishmaster270

good morning

I don’t mind doing it by hand if you explain to me what I need to change

wishmaster270

@ELMAGO Hi,

i just released a new version of the module which has a new option delayNext that can be added to each command.
The module then starts the command and waits this amount of milliseconds before the next one is processed.
So in your case you can add a delayNext: 1000 to each of the commands to give your server some time between the calls.

sdetweil

@wishmaster270 you could make it support multi instance easily

in the modulename.js when u sendSocketNotification… add the module id to the data

in the node_helper, send the id back

in the modulename.js in receiveSocketNotification
check that the returned id matches this instances id

sendSocketNotification from the node_helper is a broadcast , all instances get it at the same time, thus the need for the check.

wishmaster270

@sdetweil Hi Sam, I will check that for the next release.
I already added something similar to one of my other modules but did not know that there is a module id already and added a uuid instead.