MMM-RMV "Loading data"

CvG

Hi,

it still doesn’t work but I have tried something. I disabled every module but MMM-RMV and when I start npm directly I get an Error.

Error: No connection data recieved. Error code 400

yawns

@CvG
~~Would you mind sharing your api key via chat with me? I still did not receive any feedback from the vendor~~

Update: just received my api key

CvG

Thanks for you support. There ist an solved issue at the github page that might help you. The open one is mine.

https://github.com/Com-Lum/MMM-RMV/issues/6

yawns

Interesting. Using this does show connections for me:

                {       module: 'MMM-RMV',
                        position: 'top_left',
                        config: {
                                apikey: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
                                stationId: '3000001',
                                }
                },

Using your config fails for me, debug console shows an error.

                {       module: 'MMM-RMV',
                        position: 'top_left',
                        config: {
                                apikey: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
                                stationId: '3025547',
                                }
                },

I hope I find some time tomorrow to dig into this.

CvG

Hmmmmmmmmm?

That is strange. I’ll check this when I’m back in my office at monday.

"… shows an error. ", means “loading data” in gui and error 400 or do you get something new?

When I use my browser to querry the information it works fine. So the data is available for this station.
Do you know a way to show the url the magicmirror backend uses? This is where my Linux knowlege ends.

yawns

@CvG
In node_helper.js you find //console.log(some thing with url)
Remove the // and restart your mirror. You will see the url in terminal, not browser

CvG

Hello,

now its working.

My fault was that I misspelled the entry apiKey (I wrote it apikey. With a small k). I found out about this when I displayed the url because the accessId was empty. Now, with a capital letter K it works.

Thanks for this and you help

yawns

bummer. I didn’t notice that o.O

CvG

The “mean” thing is that your relay has the error too, but you wrote that it workes for you.

yawns

@CvG That’s because I tested on one machine and responded on another. I copied your config (and therefore your error) and just modified with my stationID.