I've repeated these steps 3 times just to make sure that I didn't click "Apps List" or anything like that... Also, no backups were restored either before or during these steps.
I'm not suggesting that your not having this issue just that I can't reproduce it in my system. I wanted to see if it was a bug that impacted all hubs. I'm running 2.1.7.127
Both seem to have a valid state with the name "temperature"...
But: next I'm going to pick different devices for both of these (especially the first one, given that the driver for that one was written by me )
If I start with a different device, say a motion sensor that also reports temperature, THEN edit the trigger and change it to my temperature sensor in question, Actions work properly!
Only if I start right away with this temperature sensor as part of the trigger, then Actions throws that error, and after that the rule becomes "broken" no matter which device I change the trigger to, or even if I delete the entire trigger...
Of course, I wish there was a way to get a response from HTTP GET action in RM and assign it to a variable... Then I wouldn't make some kind of a mistake here
Can't see what's wrong though...