@BKeyport Hi,
i formatted your output to understand the JSON structure you are using:

{
    "data": {
        "did": "001D0A71573B",
        "ts": 1675287003,
        "conditions": [
            {
                "lsid": 434637,
                "data_structure_type": 1,
                "txid": 1,
                "temp": 47.4,
                "hum": 52.8,
                "dew_point": 31.0,
                "wet_bulb": 38.4,
                "heat_index": 46.4,
                "wind_chill": 47.4,
                "thw_index": 46.4,
                "thsw_index": null,
                "wind_speed_last": 2.00,
                "wind_dir_last": 31,
                "wind_speed_avg_last_1_min": 2.62,
                "wind_dir_scalar_avg_last_1_min": 6,
                "wind_speed_avg_last_2_min": 2.81,
                "wind_dir_scalar_avg_last_2_min": 358,
                "wind_speed_hi_last_2_min": 5.00,
                "wind_dir_at_hi_speed_last_2_min": 340,
                "wind_speed_avg_last_10_min": 1.43,
                "wind_dir_scalar_avg_last_10_min": 36,
                "wind_speed_hi_last_10_min": 5.00,
                "wind_dir_at_hi_speed_last_10_min": 336,
                "rain_size": 1,
                "rain_rate_last": 0,
                "rain_rate_hi": 0,
                "rainfall_last_15_min": 0,
                "rain_rate_hi_last_15_min": 0,
                "rainfall_last_60_min": 0,
                "rainfall_last_24_hr": 0,
                "rain_storm": 0,
                "rain_storm_start_at": null,
                "solar_rad": null,
                "uv_index": null,
                "rx_state": 0,
                "trans_battery_flag": 0,
                "rainfall_daily": 0,
                "rainfall_monthly": 0,
                "rainfall_year": 1750,
                "rain_storm_last": 4,
                "rain_storm_last_start_at": 1674798601,
                "rain_storm_last_end_at": 1675000860
            },
            {
                "lsid": 434634,
                "data_structure_type": 4,
                "temp_in": 79.4,
                "hum_in": 20.5,
                "dew_point_in": 35.5,
                "heat_index_in": 77.4
            },
            {
                "lsid": 434633,
                "data_structure_type": 3,
                "bar_sea_level": 30.125,
                "bar_trend": -0.013,
                "bar_absolute": 29.660
            }
        ]
    },
    "error": null
}

The hum value is part of the first element with index 0 of the conditions object which is part of the data object.
This results in a more advanced jsonpath…

		{
			module: "MMM-ValuesByNotification",
			position: "top_left",
			header: "Module-1",
			config: {
				groups: [
					{
						items: [
							{
								notification: "WEATHERLINK",
								itemTitle: "Item-1",
								values: [
									{
										valueTitle: "Value-1",
										jsonpath: "data.conditions[0].hum",
									},
								]
							},
						]
					},
				]
			},
		},

This config works out of the box ;-)

Edit:

If the order of the elements of conditions varies you can use

jsonpath: "data.conditions..hum"

This one selects the hum value of any element of conditions.

@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.

@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.

@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.

@digied Great to hear that. You are welcome.

@cweinhofer Hi,

I do not know ESPHome but it looks like it sends the data via MQTT.
So you can use MMM-MQTTbridge to receive messages and MMM-ValuesByNotification to format and display them.

@digied Just released a new version which fixes the host part replacement

@digied Perfect. I will look into the module to check if I can accept self signed certificates and why the host part is not replaced correctly.

Edit:
You should be able to set the cam with by adding some CSS to the file MagicMirror/css/custom.css:

.MMM-SynologySurveillance .cam { 
    width: 100%; 
 }

@digied Hi,

it’s nearly perfect. Now the needed library and the access to the NAS works.
The output of your log shows that the fetched URL contains the hostname of your NAS AND the IP.
Maybe there is a bug in my replaceHostname function.
Your config contains a replaceHostPart set to true.
Can you set it to false please.

Edit: Now that I see all your posts things are clearer ;-)

@digied That log looks totally different than the other one. What did you change?