Limburg.NET possible API issue (or config. not sure anymore)

[jayjayseal]

[The limburg.net API-proxy works as far as i can see. but still the sensors are unavailable.]

(https://limburg.net/api-proxy/public/afval-kalender/gemeenten/search?query=gingelom) gives a nisCode

afvalbeheer:
  wastecollector: Limburg.NET
  resources:
    - restafval
    - gft
    - papier
    - pmd
  postcode: 3890
  streetname: xxx
  cityname: xxx
  streetnumber: x
  upcomingsensor: 1 # (optional)
  dateformat: "%d-%m-%Y" # (optional)
  dateonly: 0 # (optional)
  nameprefix: 1 # (optional)
  builtinicons: 0 # (optional)
  dutch: 1 # (optional)

[pippyn]

Please provide an address in your neighborhood for me to test with

[jayjayseal]

Try Houtstraat 2, Gingelom... they have good Belgian fries there :)

[pippyn]

This config is working fine for me:

afvalbeheer:
  - wastecollector: Limburg.NET
    resources:
      - restafval
      - gft
      - papier
      - pmd
    postcode: 3890
    streetname: Houtstraat
    cityname: Gingelom
    streetnumber: 2
    upcomingsensor: 1 # (optional)
    dateformat: "%d-%m-%Y" # (optional)
    dateonly: 0 # (optional)
    nameprefix: 1 # (optional)
    builtinicons: 0 # (optional)
    dutch: 1 # (optional)

[jayjayseal]

Excuse me, it was HA that changed the entity names to sensor.limburg_netgft2

Sigh

[pippyn]

Delete the old sensors (without _2) after that you can rename the new sensors.

PS. this is not HA's fault, this is a bug for some users in the latest update of this sensor. But i haven't found yet what went wrong. My apologies!

[jayjayseal]

Well.... don't sweat it :-)....

I love your integration and my other half too :-) and it works for a a lot of different companies as well.... (we have moved from an area with the recycle app to limburg.net and could keep using it....

I can only take my hat off and bow for you :1st_place_medal:

[pippyn]

Thanks for the kind words!