Domoticz

It seems ANWB traffic info is not working anymore. ANWB currently is not providing traffic info anymore via the API that was used by Dashticz.

Let's wait a few days: maybe it returns.

Otherwise we could switch for instance to the RSS feed of verkeerplaza.nl.

Other suggestions are welcome as well.

As I did the ANWB trafficinfo part I've looked into why its not working anymore. Seems ANWB switched to an other API.
Not so difficult to change to the new API but there are no trafficjams to test on

@BoelShit How to change to the new API?

It is being worked on atm. It's not just changing the url of the API, they've changed the structure of the data a bit.

BoelShit wrote: ↑Tuesday 28 April 2020 19:58 It is being worked on atm. It's not just changing the url of the API, they've changed the structure of the data a bit.

Top!!

The ANWB traffic info has been fixed in latest beta. (thanks to @BoelShit!)

I still have an issue with ANWB traffic. Even on the latest beta version V3.4.5.

cors-anywhere.herokuapp.com/https://api.anwb.nl/v1/incidents?apikey=xxxx Failed to load resource: the server responded with a status of 400 (Bad Request)

When i run it on the demo site of cors-anywhere i get the following message:

GET https://cors-anywhere.herokuapp.com/htt ... pikey=xxxx
400 Bad Request

{"errors": [{"title":"Bad Request","message":"Invalid origin.", "code":9}]}

Try to use the Dashticz internal CORS proxy.

Lokonli wrote: ↑Wednesday 29 April 2020 18:46 Try to use the Dashticz internal CORS proxy.

I do use the internal CORS proxy.
config['default_cors_url'] = 'http://cors-anywhere.herokuapp.com/';

or should it be different?

Brinkie wrote: ↑Thursday 30 April 2020 14:08

Lokonli wrote: ↑Wednesday 29 April 2020 18:46 Try to use the Dashticz internal CORS proxy.

I do use the internal CORS proxy.
config['default_cors_url'] = 'http://cors-anywhere.herokuapp.com/';

or should it be different?

That is the external CORS proxy.

You can remove the default_cors_url setting from CONFIG.js. The default CORS url will then be used automatically.
If you've installed PHP according the installation instructions, the internal PHP based CORS proxy will be used.

Lokonli wrote: ↑Thursday 30 April 2020 15:53

Brinkie wrote: ↑Thursday 30 April 2020 14:08

Lokonli wrote: ↑Wednesday 29 April 2020 18:46 Try to use the Dashticz internal CORS proxy.

I do use the internal CORS proxy.
config['default_cors_url'] = 'http://cors-anywhere.herokuapp.com/';

or should it be different?

That is the external CORS proxy.

You can remove the default_cors_url setting from CONFIG.js. The default CORS url will then be used automatically.
If you've installed PHP according the installation instructions, the internal PHP based CORS proxy will be used.

Thanks! I had PHP installed, but did’t set the option OpenSSL. It works now.

The anwb traffic info works fine, but the predefined block 'traffic' doesn't show any information either. Has this the same cause?

JanvdW wrote: ↑Friday 01 May 2020 17:57 The anwb traffic info works fine, but the predefined block 'traffic' doesn't show any information either. Has this the same cause?

What do you mean with predefined block traffic. I use this in my config.js file

var trafficinfo = {}
trafficinfo.anwba1 = {
key:'anwba28',
provider: 'anwb',
road:'A1',
trafficJams: true,
roadWorks: true,
radars: true,
show_lastupdate:true,
icon: 'fas fa-car',
width:12,
results: 10 };

Spoiler: show

Brinkie wrote: ↑Saturday 02 May 2020 15:02

JanvdW wrote: ↑Friday 01 May 2020 17:57 The anwb traffic info works fine, but the predefined block 'traffic' doesn't show any information either. Has this the same cause?

What do you mean with predefined block traffic. I use this in my config.js file

var trafficinfo = {}
trafficinfo.anwba1 = {
key:'anwba28',
provider: 'anwb',
road:'A1',
trafficJams: true,
roadWorks: true,
radars: true,
show_lastupdate:true,
icon: 'fas fa-car',
width:12,
results: 10 };

I think he means this block: 'traffic'. Traffic info from Rijkswaterstaat Verkeersinfo (Netherlands).

Yes, that's right. As far as I know you can't configure anything for the 'traffic' block, so it hardly can't be a configuration issue

Lokonli wrote: ↑Wednesday 29 April 2020 10:05 The ANWB traffic info has been fixed in latest beta. (thanks to @BoelShit!)

Do you know if this problem is applicable for the predefined block 'traffic' as well? If so,who is able to fix that?

I've looked at the traffic block for you and the whole source (http://www.vid.nl/VI/_rss) of information isn't available anymore. So if there is no other similar source I think it will be hard to fix. Can't recall what it showed when it did work.

BoelShit wrote: ↑Wednesday 13 May 2020 16:45 I've looked at the traffic block for you and the whole source (http://www.vid.nl/VI/_rss) of information isn't available anymore. So if there is no other similar source I think it will be hard to fix. Can't recall what it showed when it did work.

It showed this:

The first block is the traffic block, the second one the train block.

It was just one line of text, and a clickable button, which opens the Rijkswaterstaat traffic info.
For instance this link:
https://rwsverkeersinfo.nl/actuele-verkeersinfo

I see no update on this topic. If it can't be fixed I suppose that the documentation should be updated (https://dashticz.readthedocs.io/_/downl ... /beta/pdf/)

@BoelShit Can we use the following url for traffic block: https://api.rwsverkeersinfo.nl/api/traffic/