It would greatly increase the usefulness of the sensor if we could search from a list of stations and sort by cheapest or better still a radius from a postcode like the website/app.
Not sure how difficult this would be to implement.
Thanks
I agree… it’s an utter bastard to get the ID’s and helpfully Caltex changed one of the ID’s today… but which one? Would be nice if you could include a friendly name in the config rather than having to use customize.
Hi @Uskompuf, @DavidFW1960 I am the author of the component, but only just came across this thread.
When I initially build the first component, I actually had intentions to implement the features you’re mentioning, but time got away from me. The particular sensor I wanted to implement was “cheapest fuel in radius of a location”. Hopefully over the next few weeks
I can build such a sensor if there is demand for it? (The underlying library I wrote nsw_fuel_api_client supports this use case).
1 Like
Hi Nick… yeah I saw in the original docs you could include a friendly name in the config and I had that in there even though it wasn’t used . Unfortunately 0.88.x makes the config invalid with that in there. I still use a friendly name in customize but if a station changes name then it’s not easy to work out which one it is and then find the new one and edit it.
I like being able to specify a list of locations around my home and also to specify a brand etc. I’m not sure how useful specifying a radio is would be for me but as an option?
It would be great if you could setup a radius of like 5 - 10 km of where you are, so you can say something like “hey google take me to the cheapest 91 etc…”
Hi, just wondering if there is any progress on this? Or at least ability to add a few different Servo’s into HA? Its a very useful integration!
I have almost 20 servos so you can add as many as you like.
I’m only fairly new to HA - how do I add multiples? If I do the following it shows errors.
sensor:
- platform: nsw_fuel_station
station_id: xxxx
station_id: yyyy
station_id: zzzz
Thanks for replying so quick!
sensor:
- platform: nsw_fuel_station
station_id: xxxx
- platform: nsw_fuel_station
station_id: yyyy
- platform: nsw_fuel_station
station_id: zzzz
See mine here home-assistant/packages/fuel.yaml at 3441c9ed784e54b858044acce9ae2442f09c0aa9 · DavidFW1960/home-assistant · GitHub
Awesome! That worked a treat! I didn’t actually try doing it that way as I tried a similar format for another sensor I have integrated and it didn’t work doing it like that.
How often do the prices update? I added a few more Servo’s into my HA and it seems the prices are out of sync with the Fuel Check site.
Thanks so much for your help - and by the way, from that Servo list I see I see you’re a fellow CC resident, what are the chances!
Whenever they change I think. I have only noticed them being in sync with Fuel Watch.
hahaha… that is pretty low odds eh…
It seems the out of sync prices are actually on the Fuel Watch site itself.
When I do a search and am presented with a list of Servo’s and their prices the price for some of my local Servo’s is actually different to when you go the ‘fuel near me’ route and look at it in map view…
Fuel near me would be pretty great actually!
Does this intgration still work? Asking as I can not get it to work. Manually added the 4 files to the folder in custom components. Added the - platform: nsw_fuel_station and station_id: XXX to my sensor.yaml file.Nothing. Any advice? Thanks.
Still working fine here
Got it working - silly mistake. All good now.
I have found that there are only a few stations near me worth checking, so pinned badges onto a map. Really crude i know, but does the job for me. It would be nice to highlight which is cheapest - I assume it can be done with a script or similar, but I haven’t put the effort.
type: custom:layout-card
layout_type: vertical
layout: {}
cards:
- type: picture-elements
image: http://192.168.1.98:8123/local/wollongong_petrol.jpg
elements:
- type: state-badge
entity: sensor.metro_petroleum_fairy_meadow_u91
style:
top: 25%
left: 60%
- type: state-badge
entity: sensor.speedway_wollongong_u91
style:
top: 46%
left: 40%
- type: state-badge
entity: sensor.metro_wollongong_u91
style:
top: 48%
left: 50%
- type: state-badge
entity: sensor.your_fuel_coniston_u91
style:
top: 60%
left: 51%
- type: state-badge
entity: sensor.7_eleven_unanderra_u91
style:
top: 70%
left: 20%
- type: state-badge
entity: sensor.enhance_24_hour_self_service_u91
style:
top: 85%
left: 60%
- type: state-badge
entity: sensor.enhance_port_kembla_u91
style:
top: 90%
left: 75%
- type: state-badge
entity: sensor.metro_berkeley_u91
style:
top: 90%
left: 15%
- type: entities
entities:
- entity: sensor.enhance_russell_vale_u91
- entity: sensor.independent_towradgi_u91
- entity: sensor.metro_petroleum_fairy_meadow_u91
- entity: sensor.speedway_wollongong_u91
- entity: sensor.metro_wollongong_u91
- entity: sensor.your_fuel_coniston_u91
- entity: sensor.pearl_energy_bomaderry_u91
state_color: true
view_layout: {}
1 Like
So set these up in fuel watch and display on a card sorted by price.
I tried and failed to have the senor return multiple fuel types eg both Premium 98 and diesel. I tried the below and none worked. Can this be done and if so can you point me in the right direction? Thanks.
- P98, DL
- ‘P98’, ‘DL’
- [‘P98’, ‘DL’]
Below is what the integration says.
fuel_types list (optional)
A list of fuel types to track for the station. Must be one of ["E10", "U91", "E85", "P95", "P98", "DL", "PDL", "B20", "LPG", "CNG", "EV"]. Descriptions of fuel types can be found here.
Default:
['E10', 'U91']