birthdaylist - discontinued ?

rkorell

The suspending call seems indeed to come from MMM-Pir.
But there is always a resuming…

birthdaylist received a module notification: MMM_PIR-SCREEN_POWERSTATUS from sender: MMM-Pir
birthdaylist.js:337 birthdaylist suspending
birthdaylist.js:108 birthdaylist received a module notification: CURRENTWEATHER_TYPE from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: WEATHER_UPDATED from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: WEATHER_UPDATED from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: CURRENTWEATHER_TYPE from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: WEATHER_UPDATED from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: WEATHER_UPDATED from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: CALL_DISCONNECTED from sender: MMM-FRITZ-Box-Callmonitor-py3
birthdaylist.js:108 birthdaylist received a module notification: MMM_PIR-SCREEN_POWERSTATUS from sender: MMM-Pir
birthdaylist.js:345 birthdaylist resuming
birthdaylist.js:108 birthdaylist received a module notification: CURRENTWEATHER_TYPE from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: WEATHER_UPDATED from sender: weather
birthdaylist.js:108 birthdaylist received a module notification: WEATHER_UPDATED from sender: weather
birthdaylist.js:337 birthdaylist suspending
2birthdaylist.js:108 birthdaylist received a module notification: MMM_PIR-SCREEN_POWERSTATUS from sender: MMM-Pir
birthdaylist.js:345 birthdaylist resuming

I assume that we have to wait until birthdaylist disappears and then check the written logs afterwards if there is something different (I guess: NOT :-(. )

Regards,
Ralf

sdetweil

@rkorell right we have to wait, thanks for the great info

ill look at the init time message

sdetweil

@rkorell notifications are broadcast. so every module gets every broadcast.

thats why you have to check if the broadcast is for you , but logging them all can give an idea what is going on.

if clock seconds was enabled you would see a notification for that too

rkorell

@sdetweil clock seconds are enabled, as far as I know …
at least I haven’t found a parameter to enable/disable seconds
and second hand is shown …

sdetweil

@rkorell you are using the analog clock, not digital

this for digital

displaySeconds	Display seconds.

Possible values: true or false
Default value: true

and I didn’t see this change

sendNotifications	Enable notifications for elapsed time. Used to be always done send prio to v2.23

Possible values: true, or false
Default value: false

rkorell

@sdetweil Yeah…
You’re right.
I’ve set this - my type of clock is set to “both” because I like sunset and day of week information.

This causes an error in your module…

birthdaylist.js:398 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'startsWith')
    at Class.getBD_DAY_from_Date (birthdaylist.js:398:9)
    at Class.getDom (birthdaylist.js:462:154)
    at main.js:132:35
    at new Promise (<anonymous>)
    at updateDom (main.js:112:10)
    at Object.updateDom (main.js:669:4)
    at Class.updateDom (module.js:341:6)
    at Class.socketNotificationReceived (birthdaylist.js:328:9)
    at module.js:240:9
    at Socket.<anonymous> (socketclient.js:32:4)

Not sure if this corresponds with the displaySeconds parameter but seen this error first time…

Regards,
Ralf

rkorell

No, obviously NOT…
I’ve now added “sendNotifications: true” to config.
Mirror reloads and your module starts without this error message.

sdetweil

@rkorell can i see your birthdaylist config

and the date portion of one birthday from the list, which order the date info is in

and this error is trying to check if tye month part starts w a 0
and i figure out which date separator you used
/, or :, or just not ,
and then i split the date with the separator i discovered, they all HAVE to be the same separator and order

rkorell

@sdetweil yes, for sure

birth, name
17/01/1965,Carola
31/12/1963, Ralf
27/01/1993, Lennart
11/07/1987, Levin 
28/07/1985, Katharina
4/1/1953,Norbert L.
18/3/1939,Jürgen
22/3/1996,Chrizzy
27/3/1985,Hochzeitstag
31/3/2012,Hannah
31/3/2022,Nilo
11/4/1974,Claas
26/4/1965,Ralf B.
30/4/1989,Rahel
7/5/2020,Mathilda
27/5/1994,Elaine
10/6/1960,Melanie
5/2/1965,Stefan
26/5/2002,Leonie
4/1/2004,Carolin
10/6/95, 2.Hochzeitstag
10/6/1964,Petra B
23/6/1984,Colin
29/7/1995,Jassi
29/7/1955,Shirley P.
20/7/2001,Helene
5/8/1963,Harald
16/9/1997,Shirley Pi.
20/9/1965,Heiko D.
15/8/1967,Uta
23/8/2019,Emil
17/11/68,Susanne
27/9/1987,Severin
9/11/1948,Marianne
12/11/1967,Silvia
27/11/1956,Martina L.

rkorell

Ahh…
in the code listing it shows up a difference …
“10/6/95, 2. Hochzeitstag”
with an additional space and a dot…
is this a problem?
I can change the taxt and delete space if nacessary (althoug I mean I’ve read that you are truncing entries …
But the dot could be eliminated if useful.

Ralf

rkorell

interesting enough the error shows up first time as I reported - the list is always the same - literally unchanged until first day of installation…

sdetweil

@rkorell nvm i see it… let me look at it

sdetweil

@rkorell I don’t see the error… can you show me the bdlist config

also, that line of code would only happen is there WAS a birthday to display
and your list doesn’t have one for tomorrow or later (in this month)
are for next month…

still don’t see the error…
my code strips off the extra leading space on the name field.

rkorell

@sdetweil indeed - should have done this at the begin, sorry:

// Geburtstagsliste 
// Gelesen wird: ~/MagicMirror/modules/birthdaylist/data/bdl.csv

		{ 
	        
	        module: "birthdaylist",
	        disabled: false,
	        position:'top_right',  
	        config: {
						dimmEntries: false,  // true: dims entries and the associated symbol when the date has expired. false: dont display entries and the associated symbol when the date has expired.
						initialLoadDelay: 0, // How many seconds to wait on a fresh start up.
						updateDelay: 5,      // How many seconds after midnight before a refresh
						currentMonthOnly: false,  // will show birthdays for the current month only if true
						maxEntries: 3,	     // maximum entries to show, default is all
						dateFormat: '',	     // date format for birthday (default is none), could be 'Do' for 'Sep 12th'
						ageFormat:'',	     // some format string for the persons age, '[ n ]'  n will be replace by age value
						withMonth: true ,    // then true, add the month display as part of the date field, 
						debug:true,
	                }
		},

warmest regards,
Ralf

rkorell

Stefan, Jürgen and Chrizzy are shown - which is correct, as far as I understand the parameters.

sdetweil

@rkorell correct, same as what i see. no fault tho

the init message appears to be an MagicMirror bug
i opened https://github.com/MagicMirrorOrg/MagicMirror/issues/3708

rkorell

@sdetweil OK; thanks.
this is regarding the init error.
Yesterday night birthdaylist disappeared again.
And my initial finding is at least reproducable:
Birthdaylist disappears from physical screen (connected via HDMI) and from VNC remote session.
BUT: In webbrowser it disappears NOT:

If I do a reload in Webbrowser - instantly the birthdaylist appears on screen as well as in VNC session.

console log shows:
birthdaylist received a system notification: MODULE_DOM_UPDATED

I had assumed that I can find all of the console logs in the logfiles in $HOME/.pm2/logs but this is not true.

Any idea regarding this discrepancy?

Thanks again a LOT for your kind and great support!
Warmest regards,
Ralf

(sorry for the rubbish Browser - rendering but I’m not able (or too stupid) to scale this correctly)

sdetweil

@rkorell ok, that message comes in response to a module updating its content. but I see a bug in my code i cant get to today

to work around it add another config parm for the module

debugging:true,

you will get additional messages during setup and nightly refresh (5 seconds after midnight by default)

maybe its not a bug, but a document error

rkorell

@sdetweil OK; cool.“workaround” is OK for me :-)

so

debug: true,

AND
debugging:true,

both in your module?

Again: Thanks a LOT.
Ralf

sdetweil

@rkorell yes, both