UK Fuel Finder

Share your Projects!
21

I got a reply to say:

“We rely on a third-party postcode lookup service, and currently, this postcode (PE12 6JP) is not returning any results through that service.
The postcode you see in the database was manually entered, which is why it exists in our records but cannot be retrieved via the postcode search functionality.
We understand this can be confusing, and we will raise this with the third-party provider to investigate further.”

I’ve told them that I have yet to get their system to accept any postcode and sent them a list of the ones I have tried (all of which are valid postcodes for fuel stations in their database).

22

I’ve still not had any reply other than the log.

I can’t seem to get any data today with error “No access_token in OAuth response”

’ Report an error in fuel prices or forecourt details’ now just says it can’t find anything on either postcode or advanced input.

23

I’m running this in node red on a rasp Pi and I’m finding every couple of days it stops getting the data with the error “No access_token in OAuth response”. If i copy the flow into a new flow all works again for a couple of days.
I’m not sure how to find the error or where the token is kept in node red.

24

I’ve found the location but surprised to see the “expires at” is the date/time I recreated the flow.

"ff:oauth": {
        "access_token": "5cCI6IkpXVCJ9.eyJraW5kIjoicHVibGljIiwiY2xpZW50X2lkIjoiYTJ1ZEZBZHBqWkJ1aHJEaGlZVGpRbHByY3dsc21jRzciLCJpbmZvX3JlY2lwaWVudF9pZCI6IjNhY2Q3NGMyLWJiYzUtNGQ0NS1hYjg0LTlkYmYyNWUxZTUzMSIsInN1YiI6ImEydWRGQWRwalpCdWhyRGhpWVRqUWxwcmN3bHNtY0c3IiwiYXVkIjoib2F1dGgiLCJpYXQiOjE3NzYxNTczNzcsImV4cCI6MTc3NjE2MDk3N30.7eog5vTDdOX-F_cC0F-b1wQ2-bLhFZktdAXMVgZlMYE",
        "expires_at": 1776161010,
        "refresh_token": "5cCI6IkpXVCJ9.eyJraW5kIjoicHVibGljIiwiY2xpZW50X2lkIjoiYTJ1ZEZBZHBqWkJ1aHJEaGlZVGpRbHByY3dsc21jRzciLCJpbmZvX3JlY2lwaWVudF9pZCI6IjNhY2Q3NGMyLWJiYzUtNGQ0NS1hYjg0LTlkYmYyNWUxZTUzMSIsInRva2VuX3VzZSI6InJlZnJlc2giLCJzdWIiOiJhMnVkRkFkcGpaQnVockRoaVlUalFscHJjd2xzbWNHNyIsImF1ZCI6Im9hdXRoIiwiaWF0IjoxNzc2MTU3Mzc3LCJleHAiOjE3NzYzMzAxNzd9.NEhIpodfYD508S1Zx5sv7px-TZpn1JELDTn0P1lOMY0"
    },

EDIT
Fuel finder error reporting website is now working.

25

Sorry, I can’t help with the token problem but thank you for noting that the error reporting website is now working. I have submitted a location correction and two brand corrections for stations near me, it will be interesting to see if/when the corrected data appears in the database.

26

Bump;
Does anyone know what causes the error?

“No access_token in OAuth response”

@Rozak

27

Got round it with;

[
    {
        "id": "fb5044a4165696e6",
        "type": "inject",
        "z": "1d76d41bedf3be7b",
        "name": "",
        "props": [
            {
                "p": "payload"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "str",
        "x": 290,
        "y": 400,
        "wires": [
            [
                "89cf6193815ee167"
            ]
        ]
    },
    {
        "id": "89cf6193815ee167",
        "type": "change",
        "z": "1d76d41bedf3be7b",
        "name": "",
        "rules": [
            {
                "t": "delete",
                "p": "ff:oauth",
                "pt": "flow"
            }
        ],
        "action": "",
        "property": "",
        "from": "",
        "to": "",
        "reg": false,
        "x": 450,
        "y": 400,
        "wires": [
            []
        ]
    }
]
28

Sorry! been working on other things!
I've stopped using the Node Red flow as I use the python script now - the oath endpoint should work though - I don't remember any changes to the API from that respect from when I put the Node Red flows together - the token will be stored away in the context on your Node Red platform (however you have set that up).

One thing to remember is you can't run more than one flow wth the same API key - the government end will get all confused and start expiring tokens.

Looking quickly at your tweak (and from memory!) you're deleting the token so essentially a new token is fetched every pull - that will work but not a great fix - if I get time I'll try and reload the Node Red flow and update it (it's probably got bugs in it now from the changes they've made to the API) and see if I can see what might be wrong with the oAuth.