@dkhorse74 said in Default Calendar not updating with new info:

@sdetweil
I created a test event today… I will update the location of this test event tomorrow and run the curl command to see results

@sdetweil
so the issue is isolated with repeated events.

If, for example, I enter a repeated event which is to occur every Sunday at the same location and then I edit the location of just one of those repeated events that’s where the location update fails.

I redirected the URL output (per your suggestion) and I still see the old location in the file. Any ideas what would cause this?

@sdetweil
I created a test event today… I will update the location of this test event tomorrow and run the curl command to see results

@sdetweil said in Default Calendar not updating with new info:

@dkhorse74 can u pull the ics file after your update and verify the event is there

curl -sL your_ical_url  >somefile.txt

then examine somefile.txt for your modified event

Will do once I get back into town tomorrow. Thanks @sdetweil

MM Software = 2.21.0
Module = Default Calendar
Calendar = Google ical using secret address

Issue:
If I update the original location to a new location in my google calendar, the update of new location doesn’t reflect in MM Default Calendar module. Reboot/Restart to no avail. The default calendar still shows the original location when I had first created the event.

I tried updating “calendarfetcher.js” using the following link:

https://forum.magicmirror.builders/topic/9894/default-module-calendar-not-updating

however, this did not work either. At a loss… Any advice?

@grena said in MMM-PIR-Sensor-Lite does not switch HDMI off:

:thumbs_up: Yes, You can also run the python script of the module: python3 -u ~/MagicMirror/modules/MMM-PIR-Sensor-Lite/pir.py SENSOR_PIN

Got everything to work perfectly…

For anyone else who maybe considering using the doppler sensor with a potentiometer, you can follow the “how-to” thread in my initial post BUT use the MMM-PIR-Sensor-Lite module only as it keeps things simple. The other PIR modules may not work with Debian 11 (Bullseye)

As for the resolution, the mistake was on my end:

• I had “GND” and “Vout” swapped on the board pins

• I had to join my raspberry login id to group “gpio”

The following page is very useful to test the functionality of the sensor before you implement the change to mirror config file (thanks to @sdetweil for posting the link in a different thread):

https://projects.raspberrypi.org/en/projects/parent-detector/3

Again thanks to all for the help…

@sdetweil
Found another post where you shared a link on how to run a PY script to test the sensor:

https://projects.raspberrypi.org/en/projects/parent-detector/3

Going to try this later tonight.

@sdetweil
yep, understood… Still not able to wake up the screen… I tested the sensor with a meter and getting correct input voltage… is there anything I could be missing?

@sdetweil
that did it! Screen goes to sleep… now need to figure out how to get the doppler sensor to “wake-up” the monitor

@sdetweil
Thank you I will try… I ran:

xrandr -q

which show HDMI-2 is what is currently plugged in… Will report back