MMM-SingleStock

[plainbroke]

I have been trying for a week now to get Single Stock to work again.
I removed and reinstalled it.
tried it again, no luck.
ran npm install in the modules/MMM-SingleStock folder.
still no luck
Went and deleted and made a new API token.
Still no luck.
Any Idea’s as to what I am doing wrong?
I have 32 other modules running using carousel but can not get this one to work.
Do I have to have config.js set to 0.0.0.0 or localhost instead of [ } ?

[bhepler]

@plainbroke - Are you seeing any errors in the log files? Both the front end log file and the back end log. It could be as simple as an API change.

[plainbroke]

@bhepler
Ok, where are these logs you speak of?
I am not very good with all this. I do a lot of trial and error, to figure out what is needed to get MM to work the way I want it to.
After saying that I am pretty good at following instructions.

[Jalibu]

you can just use MMM-Jast as a working alternative.

[plainbroke]

@Jalibu
Thats all fine and dandy, except I now have to figure out how to make it very large to fit middle center on my 48 inch screen.
I had SingleStock all setup to fit my screen. I just need to know how to fix it really. I am using a 120px font with singleStock.

[bhepler]

@plainbroke All right, we’ll start at the beginning. There are two sources for log entries in the MM framework. The front end will be accessible from a web browser. But the front end is unlikely the cause of the problem you’re seeing. So that means finding the back end logs.

Assuming that you have SSH access to your mirror and you used @sdetweil’s installation script to enable pm2*, you can find the logs by:

1. Establish a SSH connection to your Pi.
2. enter pm2 stop all at the command prompt to turn off the Magic Mirror application (Pi and monitor will remain on - you should see the Pi desktop on the mirror after a couple seconds)
3. enter pm2 flush to clear out the logs
4. enter pm2 start all to start up the Magic Mirror application
5. enter pm2 log 0 to see the log entries as they are written. Over the course of the next 30 seconds or so you will see the log entries as the application starts.

Watch the log files as they arrive and look for anything that starts with ERROR. Anything with “warning” can be ignored. You’re specifically looking for any error that also contains the MMM-SingleStock module name, but that’s not always the case.

Report back with what you find. Please copy & paste the error message into a post in this thread. Be sure to use the markup features of the forum.

• If you don’t know how to get an SSH connection to your pi, or you didn’t use the scripts, or you’re not using pm2 to auto-start your mirror, let us know and we’ll deal with that when the time comes.

[plainbroke]

@bhepler
These are the only things not in green. ```
code_text

0|mm  | [1607:0731/171531.058268:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
0|mm  | [1556:0731/171533.905455:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.NetworkManager.GetDevices: object_path= /org/freedesktop/NetworkManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files

[plainbroke]

0|mm  | MESA-LOADER: failed to retrieve device information
0|mm  | MESA-LOADER: failed to retrieve device information
0|mm  | MESA-LOADER: failed to retrieve device information
0|mm  | MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
0|mm  | failed to load driver: kms_swrast
0|mm  | MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
0|mm  | failed to load swrast driver
0|mm  | [1969:0731/182543.028972:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

[bhepler]

@plainbroke - Huh. Those appear to be graphics driver problems. They’re a known issue between the Raspian OS and the Electron framework. They shouldn’t be related to your issue with the module.

Okay, let’s dig up the other log files. Easiest thing to do is to make sure your mirror is running and then use the web browser to view the mirror interface. First, edit the config.js to allow other computers to access the interface. Change the address and ipWhiteList to allow other computers to see your mirror:

var config = {
    address: "0.0.0.0",
    port: 8080,
    ipWhitelist: [], 
...

Save and restart your mirror instance with pm2 restart 0.
Now you should point your web browser at the IP address of your mirror. Remember to add the port to the url you enter in the address bar. For example: http://192.168.0.15:8080 should get you your interface if your IP address is 192.168.0.15.

Anyhow, you should see the mirror interface in your web browser. Now you need to pull up the developer tools, usually by hitting F12 on your keyboard (I know it works in Chrome and Firefox). A section of your browser will open up with the developer tools. There will be a tab labeled console. These are the other logs I mentioned earlier.
Click on the console tab and look for anything that mentions the MMM-SingleStock module. Let us know what it says, especially if it mentions an error.