Thank you for the overview. It really helped me wrap my head around it. i got it working the way i like. After getting MMM-Alexacontrol working i added this to the config section of the AlexaControl module in config.js

notifications: [
	{		
	name: 'next month',
	port: 11100,
	OnOff: false,
	notification: ["CX3_GLANCE_CALENDAR", {step: 5}]
	}
	        ],

Search for new devices in the Alexa app, it should find “next month”. I have my calendar in week mode showing six weeks. I say “Alexa, turn on next month” and it advances the view 5 weeks(i might change it to 6) , stays there for a min then goes back to the default view.

you configure the notifications section, a list of
{
name
port
notification to send
}
(repeat as many times as needed)

name is the thing u will tell Alexa to turn on.
(it’s a fake outlet)
notification is two things

a string, with the notification name/identification
and some data ( called payload)

in the info you posted,
CX3_GLANCE_CALENDAR (the name)
{instanceId, step} ( the payload)
but I don’t know where u get those pieces of data from. they have to be hard coded in the ac config

you cannot set anything dynamically with these ac switches/plugs…

they are either on or off

you either turn it on or off

Alexa turn on {name}