GasBuddy

dherl0623

@doubleT I would be very interested in this! I do frequent usually three different gas stations.

doubleT

I did some digging but wasn’t able to find a usable alternative.

Company Website (& API)
I don’t know if the website is down or geo-blocked for me, I can’t reach www.speedway.com
If I could, I’d check if they have pages for each station with live prices available and if they have an API.

Google Knowledge Graph
I searched that station on Google and found the result page had a right hand sidebar (Google Knowledge Graph) with live prices. So I thought I could get it via the Knowledge Graph API (if you have a Google Dev API key (and activated KG), you can try it with this link) but the itemList is empty, or maybe I did something wrong. Wrong queries?

Google Maps – or Places?
Then I found out that when you search that station on Google Maps, it’ll also show the live prices in the sidebar on the left. But the latest info I found (some months old) say that there’s no way to access these as they’re not in the Google Maps API (or was it Places?).

Getting the live price from the actual gas station itself, or at least from Google, would be the best solution, as the GasBuddy price is not really live, it’s only updated when a user shares the newest price.

doubleT

@dherl0623

Here are some mockups how such a module might look:

All/selected prices from one station:

(Note: The boxes have classes that identify the fuel and can be highlighted, if wanted.)
Prices from several stations:

The reason behind this differentiation: Instead of four calls, like in the second mode, there’s only one call in the first mode. Why is this important? Load time, traffic, …

At the bottom of each box we see the last time the price was updated. I’m not quite satisfied with the mockup, yet.

One thing I’m trying to work out in the design at the moment is adding some sort of “advice” that lets you know if the price is good. What I had in mind was an arrow element that would show if the current price is higher or lower (or same) than the last one.
And similar to that how about adding the highest and the lowest price of the last 7 days so you can make a decission based on that? That’d mean a redesign of the whole thing.

Is there anything you’d like to see in a module like that, that I didn’t mention? Would you like the address/place of the station somewhere? Let me know what you think.

Mykle1

@doubleT said in GasBuddy:

Let me know what you think.

I think . . . that is one good looking module. Now you’re MY GasBuddy. :-) Well done!

Edit: Is there a link to the repo? :-)

dherl0623

@doubleT I think this looks great! I really like how simple and sleek it looks. Really all I was looking for was a simple gas price display. The price history functionality sounds interesting, and I’m not sure what more could be added beyond that.

Genie

Hi

i know this topic is old but im curious if someone had manages to succesfully to add module to Magic Mirror to see gas prices like from Gasbuddy.com or from Speedway.com

/
Genie

Mykle1

@Genie

I wrote a request to Speedway to see if they have an API that I could make use of. I didn’t write to Gasbuddy as their site didn’t make it easy to contact them.

In the meantime, I’ll look about for a free API that has accurate results

dherl0623

@doubleT Did send me his Repo for the GasBuddy module. He didn’t want it published as he did not get permission to pull from their API. I can not get it to work unfortunately. I sent a message to doubleT, but he hasn’t been active in a while. @Mykle1 Maybe I can send you the repo and take a look at it? I can’t seem to figure out what I’m doing wrong!

dherl0623

@Mykle1 Maybe you can help me decipher this error:

/home/pi/.pm2/logs/mm-error-0.log last 10 lines:
0|mm       | SyntaxError: Unexpected end of JSON input
0|mm       |     at /home/pi/MagicMirror/modules/GasStation/node_helper.js:44:22
0|mm       |     at ChildProcess.exithandler (child_process.js:225:5)
0|mm       |     at emitTwo (events.js:106:13)
0|mm       |     at ChildProcess.emit (events.js:191:7)
0|mm       |     at maybeClose (internal/child_process.js:877:16)
0|mm       |     at Socket. (internal/child_process.js:334:11)
0|mm       |     at emitOne (events.js:96:13)
0|mm       |     at Socket.emit (events.js:188:7)
0|mm       |     at Pipe._handle.close [as _onclose] (net.js:493:12)

[STREAMING] Now streaming realtime logs for [mm] process

Should I be looking at line 44 char 22 for something ?

Mykle1

@dherl0623 said in GasBuddy:

Unexpected end of JSON input

The problem seems to be with line 44 of the node_helper, not necessarily character 22 itself. I think you should concentrate on the explanation of the error.