@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.
Read the statement by Michael Teeuw here.
Posts
-
RE: MMM-Fritz-Box-Callmonitor: Notification formatting
-
RE: MMM-SynologySurveillance
@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?
-
RE: MMM-Fritz-Box-Callmonitor: Notification formatting
@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
-
RE: MMM-Fritz-Box-Callmonitor: Notification formatting
@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 -
RE: MMM-Fritz-Box-Callmonitor: Notification formatting
Additional to the wrong rename the
fritz_access.py
had the mentioned wrong urllib2 imports. I fixed the python script and the import of thePythonShell
module in node_helper.js.I created a pull request a few seconds ago.
-
RE: [MMM-ValuesByNotification] Display the payloads of notifications with titles and icons
@BKeyport
Just released version 0.0.8 of the module which should fix both issues -
RE: [MMM-ValuesByNotification] Display the payloads of notifications with titles and icons
@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 fromvalue = value.replace(/(?:\r\n|\r|\n)/g, newlineReplacement)
to
value = String(value).replace(/(?:\r\n|\r|\n)/g, newlineReplacement)
-
RE: [MMM-ValuesByNotification] Display the payloads of notifications with titles and icons
@BKeyport
Hi, great that it works now.
There are two different ways of how to change the font-size.
Either by using theclasses
option and addlarge
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 thevalue
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 themain.css
for this job. -
RE: [MMM-ValuesByNotification] Display the payloads of notifications with titles and icons
@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 index0
of theconditions
object which is part of thedata
object.
This results in a more advancedjsonpath
…{ 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
. -
RE: JSON request module
@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.