@MMRIZE That worked…after I figured out I spelled instanceId incorrectly (I had instanceID). Thanks!

@MMRIZE I have two instances of CalExt3: monthly (currentMonth) and weekly (currentWeek). Except for one calendar (Dinner), they both currently shows events with the event time like this:

What I’d like is for only the currentMonth instance to show events without the event time like this:

@MMRIZE Perfect. Thanks!

@MMRIZE Sigh. I knew it was going to be something easy like that and I was overthinking it. Thanks! Couple more questions:

1. How can I remove the CW? I’ve tried:

.CX3 .cell.cellHeader .cw {
        display: none;
}

.CX3 .cell .cellHeader .cw {
        display: none;
}

.CX3 .cellHeader .cw {
        display: none;
}

and

.CX3 .cell .cw {
        display: none;
}

2. How can I remove the start time in an instance? I’ve tried:

.CX3_currentMonth .event .time.startTime {
        display: none;
}

I got it working with a specific calendar using:

.CX3 .event.calendar_Dinner .time.startTime {
        display: none;
}

I have a Cozi calendar for dinner and the event comes over as “All: Pork Tenderloin”. Is there any way to get rid of the “All:” (with either Transform or preProcessor) and keep the rest?

@viktorzonix Wow! Thanks for this. In my searching a couple of years ago, this never came up and nothing else ever had the correct info. I had just lived with the fact that I had to keep re-entering it periodically. Woo hoo!

@Manino You have to do a couple of things. The best explanation is here. Basically, find the name of your monitor, and then do this command in terminal:

xinput set-prop ‘name of your device’ ‘Coordinate Transformation Matrix’ 0 1 0 - 1 0 1 0 0 1

This will rotate the touch controls to the right (depending on which way you turned your monitor, this might have to be adjusted). The only problem is that I haven’t found a way to make it permanent (in Raspbian), so it reverts every so often and you have to run the command again. I’ve written it to etc, but it doesn’t take. If anyone has any suggestions for permanence, I’d love to hear it.

@MMRIZE
That did it. Thanks!

I finally found a touch module that I could easily use for the glance notification and have the payload step as 1. However, two things are happening:

1: on the first press it’s going back to June. Second press goes to April. Third press goes to August. Fourth press goes to December (which would be correct, however, due to the other jumps it could just be random)

2: no events are populating in the glance

Here’s what I have for the button:

{
      module: "MMM-TouchButton",
      position: "top_left",
      config: {
          buttons: [
               {
                name: "Next",
                icon: "fa fa-calendar-days",
                notification: "CX3_GLANCE_CALENDAR",
                payload: {instanceID: [], step: [1]},
                  },
                ]
              },
           },

And here’s my CX3 config:

{
            module: "MMM-CalendarExt3",
            position: "middle_center",
            config: {
                    mode: "month",
                    instanceID: "currentMonth",
                    firstDayOfWeek: 0,
                    useSymbol: true,
                    glanceTime: 60000,
                    calendarSet: [],
            }
        },

Any thoughts?

@sdetweil

What’s worse, I had an example right above it that I knew worked, and I still didn’t register that the 09 was the issue.