Intermittent [403:setup] errors as of a few days

[CarloDeSutter]

Hi,

Has anyone come across a response body containing [403:setup] when doing the {"action":"setup"} request? I've seen this only since this week and it seems to go away after at least a few hours.

kr Carlo

[CarloDeSutter]

This morning it worked and then it didn't anymore. Before this morning, I did make a flush request but this didn't help.

It might be worth knowing that I start and stop sessions, and for each of those actions (start, stop) I perform the following:

• setup
• start/stop
• expire

for security reasons I like to expire the token immediatelly. This worked fine for over a month.

I also noticed the 403 comes back regardless of the username and password when it does, so seems like either a global issue or some form of throttling (didn't check this last one yet).

Any ideas or experiences ? kr Carlo

[dgthomson]

OK, I get this too. I'm not at home so haven't spotted this until now. I will have a look.

[dgthomson]

Can you test this new version (2.5) for me?

[CarloDeSutter]

Hmm I replaced the subflow with the 2.5 version, then I get Error! No token. 😞

[CarloDeSutter]

Did you change something of these? shellrecharge.auth.pw

When I manually set the credentials in the node-red node it works. (I normally put the credentials in the request to a node-red http node and map it like so)

[dgthomson]

The only change is having the flow identify as a Chrome browser rather than NodeRED at one particular point in the transaction. Although I can't test starting/stopping at the moment, if I do a 'poll' then I get a result, suggesting I have managed to get an API token.

[CarloDeSutter]

Wild guess is it possible this was unintended?

[CarloDeSutter]

It's not a big issue, I've hardwired the password on the subflow node itself, for now. Just that in the past I could just transmit the credential (I don't like to put it hard in the node-red flows) and then it mapped to shellrecharge.auth.pw which now it seems broken (I am guessing due to that loginPW var missing above).

Thanks for your quick and hard work

[dgthomson]

if you want to hard-wire the password then add it here inside the subflow...

[jdeluyck]

This new version seems to do the trick!

[SupercowsNL]

After importing the 2.5 flow it start working again here :) thx! I also had the 403 error.

[dgthomson]

Fixed and packaged version is here.

[DdenBraver]

I can confirm. I was running into the same issues after the firmware update on the charger. With the 2.5 workflow all the issues are resolved.

[bigbenFE]

I had the same error with the flow, a few weeks ago after the announced update of the wallbox, the wallbox no longer loaded at all, not even with the RFID card. After Shell found the error in the new firmware, it was restored to my wallbox and informed me that I would no longer receive any updates. Since I now have the same error in the flow as everyone here, at least something new seems to have been done on the homepage ;) but thanks that it works again with 2.50 =)

[kokkie-d]

It works for me again as well.