[RESOLVED] Scene with HTTP request action no longer works

Configuration
1

Hello,

Since yesterday, my scenes with HTTP request actions no longer work:
Here is what I have as an action:
Method: Post
URL: http://MyIP/cm?cmnd=Power1%20off
No Header or Body

If I put this URL in my browser, it correctly controls my Sonoff
But since yesterday, this scene no longer controls the Sonoff (is this related to the switch to V4.0.7?)
I have about ten scenes working this way and none of them work anymore

After the MQTT functionality that failed, now HTTP no longer wants to work, maybe I’m unlucky :sweat_smile:

Do you have any idea where this could come from?
Thank you in advance

2

Hi @Flitch33, oops! It’s indeed due to the last update.

After testing, the issue comes from the empty body, it crashes the action because of the new variable injection, my bad ^^

I’ll fix it tonight, I’ll let you know when it’s corrected :slight_smile:

Thanks for the feedback, and sorry for the regression! I’ll add a test to make sure it doesn’t happen again.

3

Great, thanks for the quick response, it’s awesome

4

You can also add a Tasmota device via HTTP from the Tasmota integration service :slight_smile:

5

Indeed @AlexTrovato, I do use this integration to have the switches available in the Dashboard.
However, as I have Dual modules, Gladys does not yet know how to manage the 2 switches present in a scene, I only have access to the first one… (unless I missed an episode but I double-checked).
This issue is present whether in MQTT or HTTP

==> I therefore use POST requests

6

@Flitch33 PR being built: Fix bug: body can be empty in POST/PATCH request in actions by Pierre-Gilles · Pull Request #1072 · GladysAssistant/Gladys · GitHub

I’ll let you know as soon as it’s deployed to production

7

Hi,

That’s great, thanks

I’ve just done a few tests to find a workaround
If I put any character in the Body, it works (beware a « space Â» doesn’t work…)
Until the fix is deployed in production, if anyone has the same issue as me, this might help.

8

For information, the production deployment is underway. It’s building on GitHub Actions: https://github.com/GladysAssistant/Gladys/actions/runs/552168674

9

It’s done, Gladys v4.0.8 deployed! :slight_smile:

Your instance will update automatically within the next 24 hours

10

Hello @pierre-gilles

My instance did not update. I have the following message in « System Â»:

image
image859Ă—209 9.56 KB

The first time I clicked on it, it downloaded and displayed: « Restart Gladys Â» but nothing happened. When I refresh the page, I go back to: « Download v4.0.8 Â». I also manually restarted Gladys, but nothing works, I’m still on v4.0.7.

Is this normal, should I wait?

Thank you

11

Hello @Flitch33, let Gladys update herself, it’s simpler :slight_smile: I’m going to remove this button because recent changes on the docker hub side mean we’re limited on the number of pulls we can make per day, and I think that’s what’s preventing the update.

Do you have a watchtower container running? (You can see it on the same page, on the right in the list of containers)

12

Ok thanks for the reply, I ran out of patience :slight_smile:

I confirm that the watchtower is indeed in the « started Â» state

13

Ok, remind me if it’s still not the case tomorrow, basically Watchtower performs a check every 24 hours and if there is an update, it applies it :slight_smile: