@mumblebaj Ok, the good news, the module works, the lights are updated. :-)
But I can’t change the time for the update, so no matter what value I enter, it always stays at around 10 minutes. :-(
This is part of the current config, after 10 minutes the lights will be updated.

                        refreshTime: 60 * 1000,
                        lightsOrGroups: "groups",
			animationSpeed: 2 * 1000,
			showOnlyOn: false,

@mumblebaj
Is that correct in your config 5x10000?
On your module page it says 60x10000

@mumblebajI
did it and it works :-)
Now let’s see how long the display takes to update.

Thank you

@mumblebaj said in MMM Hue Lights is not updated:

@JoeFranz Show me your config please.

{
		    module: 'MMM-PhilipsHue',
		    position: 'top_right',
		    config: {
			bridgeip: "192.168.178.xx",
			userid: "xxxxxxxx",
			colour: true
			
		    }
		},

@mumblebaj This is displayed when your module is installed, no lights… :-(
IP and userid are correct.

@mumblebaj Ok, I installed it and am trying it out. However, I would like to exclude several groups in the line “hideGroupsWithString”. How do I enter multiple groups in the line?

@mumblebaj I tried Mitch’s (https://github.com/MitchSS/MMM-Hue). That seems similar to yours. However, I have problems excluding individual rooms or zones using “hideGroupsWithString”. How do I enter multiple zones in the line?
"hideGroupsWithString: “Entertainment Area 1”, “Garden” doesn’t work. So I haven’t let it run for a long time and don’t know if it works. But I’ll try it :-)

@mumblebaj No errors are shown anywhere :-(

@mumblebaj How can I display errors?

@mumblebaj
No errors are displayed :-(

@mumblebaj
Yes, the bridge still has the same address. It works for about 1-2 hours after starting, but then the display no longer updates :-(

@sdetweil Ok, I don’t really understand. Does that mean the module no longer works with the new MM version?
It’s the mmm-hue-lights module, not Mitch’s MMM-Hue.
Then I’ll try that :-)

@sdetweil

{
    			module: 'mmm-hue-lights',
    			position: 'top_right', // pick whichever position you want
    			config: {
        			bridgeIp: '192.168.178.68',
        			user: 'xxxxxxxxxxx',
				displayType: 'grid',
				displayMode: 'groups',
				minimalGrid: true,
				minimalList: true,
				alignment: 'center',
				
        			// ... and whatever else configuration options you want to use
    		}
		},

@sdetweil After “npm start mm” nothing from the hue-lights module is shown. Do I have to enter something else?

@sdetweil Nothing about the Hue lights is displayed

Hello,
since the last MM update, MMM-Hue-Lights is no longer updated. After starting, the lamps are all up to date, but shortly afterwards they stop updating.

Greetings Jörg

@sdetweil
Don’t work so hard…
It was just a calendar where the appointments weren’t displayed. I have now copied these into another calendar and they are now displayed there. I’m glad that everything else is working fine again, thank you for your help! :-)
The command “git tag -l” only shows me up to version v2.2.0.
I think I’ll leave it like that for now…:winking_face:

No, unfortunately not… :-(

@sdetweil
That worked, thank you very much :-)
Now I’m only missing two calendars that aren’t displayed.
One from icloud and one from google. Other iCloud calendars are displayed. I hope I find the error :-)

@sdetweil

MMM-Tado doesn’t start, here are the error messages :-(

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
1|MagicMir |     at process.processTimers (node:internal/timers:512:7)
1|MagicMir | [02.01.2024 16:25.56.242] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36)
1|MagicMir | [02.01.2024 16:30.56.239] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: TypeError: self.tadoClient.login is not a function
1|MagicMir |     at Class.getData (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:20:25)
1|MagicMir |     at Timeout._onTimeout (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:103:22)
1|MagicMir |     at listOnTimeout (node:internal/timers:569:17)
1|MagicMir |     at process.processTimers (node:internal/timers:512:7)
1|MagicMir | [02.01.2024 16:30.56.240] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: Unhandled promise rejec

tion. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40)
1|MagicMir | [02.01.2024 16:35.56.242] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: TypeError: self.tadoClient.login is not a function
1|MagicMir |     at Class.getData (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:20:25)
1|MagicMir |     at Timeout._onTimeout (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:103:22)
1|MagicMir |     at listOnTimeout (node:internal/timers:569:17)
1|MagicMir |     at process.processTimers (node:internal/timers:512:7)
1|MagicMir | [02.01.2024 16:35.56.243] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 44)
1|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT