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