@pflnpi0305 I believe that @cowboysdude is correct about that line spilling over. It needs to be on one line. When in doubt you can always paste your config.js at http://jshint.com/ and see if there are any errors (one warning about undefined variable module is ok)

@pflnpi0305 are you getting any errors? Looks like you’ve posted your config in another thread, will help you there.

@kurt Cool. Sometimes off brand SD cards is the culprit of data loss. Memory is so inexpensive these days it is worth getting a good brand name card. Hopefully your trouble will now end with a new memory card. Also after so many installs you are a PRO now.

I dug up the CHIP that was sitting and collecting dust to see if I can run MM on it. It was almost successful. I documented my installation and setup path here https://gist.github.com/morozgrafix/db069203ac4d8635a0f27e3dfa52f532

@Leobaillard I think I got it.

Lines 76-81 of MMM-JCD-Bikes.js is the culprit. I believe that once you were going into Object.keys it was losing the scope. Try changing those lines to this:

			// List available bikes via a stations array
			var self = this;
			Object.keys(self.stationsData).forEach(function (key)
			{
				table.appendChild(self.createStationNameRow(self.stationsData[key].name));
				table.appendChild(self.createAmountRow(self.stationsData[key]));
			});

note that I’ve added var self = this; and now calling these when appending children elements to the table: self.createStationNameRow, self.stationsData[key].name, self.createAmountRow and self.stationsData[key]

Another spot that I’ve noticed is that createStationNameRow function didn’t appendHTML name of the station to the cell. I didn’t dig too much into it, but I think this cell.innerHTML = name; was missing from it:

	createStationNameRow: function(name) {
		var nameRow = document.createElement("tr");
		var cell = document.createElement("td");
		cell.className = "stationName";
		cell.setAttribute("colSpan", 2);
		cell.innerHTML = name;

		nameRow.appendChild(cell);

		return nameRow;
	},

Hopefully it will get you going in the right direction.

@roramirez I haven’t played with Docker in a while and never tried raspbian on a docker container. Quickly glanced at DockerHub and it seems that people are able to do that. https://hub.docker.com/search/?isAutomated=1&isOfficial=0&page=1&pullCount=0&q=raspbian&starCount=0
I may take a look into it, but it all depends on my availability.

@kurt I’m not in front of my RasPi at the moment and can’t give you exact instructions, doing it from memory. Hitting Ctrl Alt F1 will drop you into terminal session, hitting Ctrl Alt F7 (if I’m not mistaken) will take you back to X window session. You can try switching to different sessions by hitting Ctrl Alt F1, Ctrl Alt F2 etc. until you get to the right place.

If you are running full Jessie with PIXEL there is also a terminal app in GUI that you can use. Some more info on PIXEL is here

:point_up: see that Terminal Icon? That way you don’t have to switch back and forth.

If you are running Jessie Lite you can hit Windows Key + R (sorry I’m not really sure what the correct terminology for Windows Key on your keyboard) and type lxterminal
and you will have a terminal session in your GUI! It will look something like this (sorry that’s a huge image):

On US English keyboard layout ~ is located to the left of the 1 key and you have to use Shift, but good news is that you can change default RasPi keyboard layout to match your locale by running sudo raspi-config in terminal. Some more information on how to get it done is here: https://www.raspberrypi.org/documentation/configuration/raspi-config.md#change-locale

Good luck and I’m glad you are making progress.

P.S. Thanks about compliments on the profile background. It’s a macro photo of a DVD-R disc that was cooked in the microwave. I have a few more from that series here https://www.flickr.com/photos/morozgrafix/albums/72157626165398064

@djbosman Hi Danie,

In the code snippet that you’ve posted (it’s a good idea to use markdown for code snippets) it looks like you are possibly using “fancy quotes”. Make sure that your config.js file has these ' or " and not these ‘ or “ (it’s possible that they were only converted in your post on the forum and your config is ok). Additionally make sure you have a comma after last } bracket as shown below:

		{
			module: 'MMM-horoscope',
			position: 'top_right', // This can be any of the regions.
			config: {
				// See ‘Configuration options’ for additional options and more information.
				sign: 'aries', // Zodiac sign
				}
		},

Also since this module is using node helper you may need to restart electron app for MM to pickup module helper for horoscopes.
You should see these lines in the console log when you do npm start:

Connecting socket for: MMM-horoscope
Starting NodeHelper for MMM-horoscopemodule.

Hope this helps and thanks for trying out my module.

P.S. I just added instructions about restarting MM in the README

@Leobaillard sent you a DM for API key. Will try to troubleshoot it

@kurt I totally understand your point and reasons for you to use GUI tools for file transfers, editing etc. My personal choice is mostly working in the terminal, but it takes some getting used to. The reason why I mentioned SSH and scp, as alternative to using GUI transfer tools, is because they are very reliable and proven to work well. I just wanted to check your comfort level using them, in case that you are suspecting FileZilla, Cyber Duck or some other GUI tool is messing up your MM installation.

To answer your question about text editors that work in terminal. There are plenty of them and they have existed for a very long time in unix/linux world. Most of the time they are available with any *nix flavor. To name a few: nano (probably easiest to learn), vim and emacs

Hope you get everything sorted with your install and if you need assistance we are here to help.