Read the statement by Michael Teeuw here.
MMM-Traffic
-
@gr1dl0ck can u look at the terminal window where u start mm to see the messages.
if you use pm2, then the pm2 logs --lines=???
command,
where ??? is a number, default 15,
will show this infoalso open the developers window, ctrl-shift-i on the mm keyboard, and select the console tab
you can filter messages by module, by putting part of the module name in the filter field,
traff should be enough.show any errors (usually red text)
-
The console logs display this, sorry dont know what it means
Uncaught TypeError: console.log is not a function MMM-Traffic.js.135 at Class.socketNotificationRecieved (MMM-Traffic.js.135) at module.js.250 at socket. <anonymous> (socketclient.js.39) at Socket../node_modules/component-emitter/index.js.Emitter.Emit (index.js.145) at Socket.emitEvent (socket.js.253) at Socket.onevent (socket.js.240) at Socket.MMSocket.self.socket.onevent (socketclient.js.33) at Socket.onpacket (socket.js.204) at Manager.<anonymous> (index.js.21) at Socket../node_modules/component-emitter/index.js.Emitter.Emit (index.js.145)
-
MMM-Traffic author here, just wanted to post here on the forum that this was resolved in a Github issue here: https://github.com/SamLewis0602/MMM-Traffic/issues/95
This is caused by a different module, the MMM-GoogleMapsTraffic module, as seen in this unmerged PR here: https://github.com/vicmora/MMM-GoogleMapsTraffic/pull/24
Anyone using both that module and my module in their mirror would see MMM-Traffic stuck on loading. Judging by the activity on that other module, it looks to be unsupported. See the issue I linked on my repo above for a manual fix if you wish to use both modules together.
-
@samlewis0602 I have the fixed Googlemapstraffic module on my github
-
@sdetweil Good to know, I’ll point people this way if I see it again.