Help Me To Get Lucy Working

Mykle1

Ok, the readme needs to be updated so the line numbers weren’t quite correct (My bad). I’ve taken the liberty of adding GoogleMapsTraffic to the defaults of Hello-Lucy. It was just easier for me than trying to explain things here.

Get a new copy of the Hello-Lucy repo.
In the MMM-voice replacement files folder is your new MMM-voice.js file and node_helper.
In the Replacement module files folder is your new MMM-GoogleMapsTraffic.js file.

Replace your current files with the files above.

Any of my modules will work by default, after having installed them. See the Replacement module files folder for other modules that you might want to use (Ex. calendar, clock, compliments, newsfeed etc)

Mykle1

Video quality is pretty bad but I’ve been working on a single, full page module specifically for my system and Hello-Lucy. The orange-ish square (bottom center) is an enlarged CPU core image containing the temperatures of each core.

HardwareMonitor

Mykle1

If only the video quality was this good. Click on images for a better view.

dazza120

@mykle1 thank you very much! At the bottom google traffic bit in the mmm-voice.js folder can I just add new modules underneath it? PS that looks good, it’s not a pi then lol, thanks for your help :)

Mykle1

@dazza120

Take a look at the readme again. Yes, you can add other modules beneath the traffic entry in the voice.js file. You HAVE to. But that’s not the extent of it. For each new module you want to add (except the default modules) you must edit

The module.js file you want to control
The MMM-voice node_helper
The MMM-voice.js file (in 2 places)

dazza120

@mykle1 yep got that in the module itself after the return wrap and in Lucy’s array yep I’ll look at the traffic one and dupe it, thanks for your help, it has been much appreciated.

bhepler

@mykle1 - That raises an interesting question. Since you have to modify the module’s main JS file, does that imply that every time the module updates you’d have to re-enter your changes?

Mykle1

@bhepler

Hey b. :-)

To answer your question directly, yes. It has always been that way. I don’t know another way of doing it that wouldn’t require re-entering the changes unless module authors wanted Lucy functionality by default. In that case, a simple addition to their module.js is all that is required. I would handle the Lucy side.

When I got the idea for Lucy there was nothing like it here. I knew what I wanted her to do and I accomplished that. Simple coding, looking back, but no small undertaking for me with no prior coding experience at all. Look at my first posts on this site. I couldn’t add a module correctly.

Anyway, I continue to use Lucy very successfully to this day,

bhepler

@mykle1 - Ah. That’s fine. Considering the functionality added, it seems a small price to pay. I just want to be sure I’m aware of the ramifications. If I’m building mirrors for friends, I need to weigh the pros & cons of including Hello Lucy into their builds. If I can maintain access to their mirror, then I can make it work. I just have to remember to redo my modifications to the module code.

But if the owners intend to run the updates… then I should probably hold off on the Hello Lucy module. I barely trust myself with modifying the code, let alone teaching someone else how to do it!

Mykle1

@bhepler said in Help Me To Get Lucy Working:

Ah. That’s fine. Considering the functionality added, it seems a small price to pay. I just want to be sure I’m aware of the ramifications. If I’m building mirrors for friends, I need to weigh the pros & cons of including Hello Lucy into their builds. If I can maintain access to their mirror, then I can make it work. I just have to remember to redo my modifications to the module code.

I have not and would not be so bold to ask all module authors to include these four lines to their module.js files. Doing so would not affect their modules but doing so would make them immediately available to Lucy and survive all updates.

if (notification === 'HIDE_COMMAND') {
            this.hide(1000);
        }  else if (notification === 'SHOW_COMMAND') {
            this.show(1000);

But if the owners intend to run the updates… then I should probably hold off on the Hello Lucy module.

Agreed, but it’s there for people that want to use it. Again, when I made Lucy there was no other module like it in function. I wanted to be able to do exactly what it does. I’m sure there are better modules that do it now, but not then. Not a single one. Ironically, Lucy’s name turned out to be more appropriate than I thought. I only used it because it’s my granddaughter’s name.

I barely trust myself with modifying the code, let alone teaching someone else how to do it!

Well, for me, learning involved modifying code. I’m not encouraging anyone to do anything. However, if they want to use Lucy then this is what they must do. If they want to get their feet wet I think that is admirable. Most copy and paste their config.js entries. This is basically the same thing, if they want to experiment and learn.