MMM-Jeedom

[ELMAGO]

@sdetweil

okay so i would make the effort, no problem, can answer my previous question?

[ELMAGO]

@ELMAGO said in MMM-Jeedom:

@sdetweil

okay so i would make the effort, no problem, can answer my previous question?

Exemple :

			{
				idx: "77", 
				customTitle: "Batterie Etage : ",
				unit : "%",
								},

if the result is greater than 50 then I would like it to be in green

[sdetweil]

@ELMAGO see my prior response

le module ne fournit aucun nom de classe spécial que vous pouvez remplacer dans custom.css.

c’est la seule section du module qui fait des noms de classe
crée une ligne (tr)

[ELMAGO]

@sdetweil

I’m sorry, I understood correctly for the css part, but not for the module itself.

Could you give me this concrete example?

[sdetweil]

@ELMAGO i’m not sure I understand the comment, but i’ll try…

when the module generates content for the screen, each little piece can have different classes assigned.
those classes can be used in the custom.css to manipulate the presentation of that segment.

the cod in this modules does

create tablerow (tr)
assign class = ‘normal’ to everything in the row

then it looks at the sensor data

			if(sensor.boolean && sensor.status==1) symbolClass = sensor.symbolon;

		        ----> if(typeof sensor.boolean== 'undefined') symbolClass = sensor.symbol;
			symbol.className = symbolClass; 

and assigns a value to the (symbol is the icon )
symbol.className

and that is all

so u have a class for the symbol
and a class for the row.

I think u want a class for the VALUE on the row but that was not supplied

[ELMAGO]

@sdetweil

ok but how can i know it?

[sdetweil]

@ELMAGO someone would have to change the code to add a class that you could then manipulate

[chassain 0]

Hello ,

I have tried this module (after an intallation of jeedom on rasp4) and i have no results on mirror… my config is certainly false because the result on terminal is good like this
curl -H “Content-Type: application/json” -X POST -d ‘{“jsonrpc”: “2.0”, “id”: “1000”, “method”: “cmd::execCmd”, “params”: {“apikey”: “my key”, “id”: 1}}’ http://192.168.1.28/core/api/jeeApi.php | python -m json.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 248 100 123 100 125 1556 1582 --:–:-- --:–:-- --:–:-- 3179
{
“id”: “1000”,
“jsonrpc”: “2.0”,
“result”: {
“collectDate”: “2019-12-28 10:00:35”,
“value”: “A570; A57; Quai Marcel Pagnol Toulon”
}
}

my config is like

		{
			module: 'MMM-Jeedom',
			header: 'Jeedom Maison',
			position: "center",
			config: {
				updateInterval: 3000,
			      	jeedomAPIKey: "my key", 
				jeedomURL: "192.168.1.28",
				jeedomPORT: 443,
				jeedomHTTPS: false,
				jeedomAPIPath: "/core/api/jeeApi.php",
				sensors: [
				{
					idx: "1", 
					customTitle: "Itinéraire1",
      				},
				],
 				},
		},

if you have an idea…thanks

[sdetweil]

@chassain-0 said in MMM-Jeedom:

http://192.168.1.28/core/api/jeeApi.php

	jeedomURL: "192.168.1.28",
	jeedomPORT: 443,    // < ---- should be 80 I think, because the url above uses port 80
	jeedomHTTPS: false,

[chassain 0]

hello man,

it’s the same result…