@digied
Oh, did not expect a dead cam resulting in this error message.
Especially as at this point all cams configured in the NAS are fetched.

@3squaremirror
Do you use any other modules which may hide/show modules?
If i copy your configuration to my test environment and add some notifications (change day/night every minute) everything works as expected.

@coernel
Hi,
as i can see this fork https://github.com/drtorchwood/MMM-FRITZ-Box-Callmonitor-py3/tree/code_update_2023 contains all changes needed.
But you will need to either use the current development version of MagicMirror or wait for the next release which i think is planned for 2022-04-01 to get the alerts formatted correctly.

@digied Hi,

looks like a DNS problem to me. Your Mirror can not resolv the ip of “datanas”.

Did there happen a update of your router maybe?

@sdetweil
I should have checked that. Thank you for the link.
With the current develop branch the formatting works as expected, too.

Edit: If the comment is removed of the translation files the translations work as well and the right title is displayed

@coernel
The pythons script is only responsible to fetch the call history and the phonebook of the fritz box. The call notification is handled by java script.
So should see a alter containing the (wrong formatted) phone number for each incoming call.

Are you sure you activated the call notification on your fritz box by dialing

#96*5*

with a phone connected to the box (DECT phone works as well).

Edit:
I do not think the formatting problem is related to this module. As of the documentation of the alert module it should be possible to send either simple text or html formatted text.
As a debug test i tried to send html formatted text with one of my other modules which ends in the same problem

@coernel
@Jan-0

Additional to the wrong rename the fritz_access.py had the mentioned wrong urllib2 imports. I fixed the python script and the import of the PythonShell module in node_helper.js.

I created a pull request a few seconds ago.

@BKeyport
Just released version 0.0.8 of the module which should fix both issues

@BKeyport
Hi,

that’s definitly a bug. It is related to the problem you described in the issue on github.
I found a fix already but i need a moment to solve it proper.
As a quickfix you can change line 299 in MMM-ValuesByNotification.js from

						value = value.replace(/(?:\r\n|\r|\n)/g, newlineReplacement)

to

						value = String(value).replace(/(?:\r\n|\r|\n)/g, newlineReplacement)

@BKeyport
Hi, great that it works now.
There are two different ways of how to change the font-size.
Either by using the classes option and add large to the element you want the font-size to be changed. i.e.:

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

The main problem with this solution is that the font-size of the valueTitle and the value itself is changed.

Or you can use custom.css to do the job:

.MMM-ValuesByNotification .vbn .groupTitle,
.MMM-ValuesByNotification .vbn .itemTitle,
.MMM-ValuesByNotification .vbn .value,
.MMM-ValuesByNotification .vbn .valueTitle {
  font-size: var(--font-size-large);
  line-height: 1;
}

In this example the font-size of all titles and the value is changed. I use the font-size-large CSS variable of the main.css for this job.