Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. MSR setup for http request (today's date)
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

MSR setup for http request (today's date)

Scheduled Pinned Locked Moved Multi-System Reactor
15 Posts 2 Posters 1.0k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT toggledbits

    The HTTP Request action can store the response into a variable (global or rule/local) that you can then use to access the data in other expressions. If the server declares that the response is JSON data, it will automatically be parsed to an object. From there, using your example, you can access the data in the object as usual. For example, in your example data, if we stored that in a variable called "lastquery",. you could access the "unit_rate" data in the response with lastquery.unit_rate.

    T Offline
    T Offline
    Talisker
    wrote on last edited by
    #3

    @toggledbits I am not sure if the returned result is JSON? I can obviously paste the response into a JSON formatter but I guess that is not the same thing? The result is unfortunately not just the 'latest' (today's rate), but a whole history of days which means I'd have to pick out the values under each day or today '2022-07-25'

    https://octopus.energy/api/v1/tracker/G-1R-SILVER-2017-1-M/daily/past/90/1/?format=json

    Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

    toggledbitsT 1 Reply Last reply
    0
    • T Talisker

      @toggledbits I am not sure if the returned result is JSON? I can obviously paste the response into a JSON formatter but I guess that is not the same thing? The result is unfortunately not just the 'latest' (today's rate), but a whole history of days which means I'd have to pick out the values under each day or today '2022-07-25'

      https://octopus.energy/api/v1/tracker/G-1R-SILVER-2017-1-M/daily/past/90/1/?format=json

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by toggledbits
      #4

      @talisker That's JSON. It's doable, but not trivial for the new players.

      I would first set up a Rule to query the server each day at a particular time. That rule would use an HTTP Request action to store the response into a global variable (let's call it energy_data). You need to create the global variable first, just leave the expression blank.

      Then make another global expression to fetch and hold the rate for today from the response by using the first statement to go through energy_data.periods until it finds the entry with date matching today's date... it would look something like this

      first entry in energy_data.periods with entry.date == strftime( "%F" ): entry.unit_rate
      

      (assuming unit_rate is the correct key/field in the entry; if not, just use the correct key name).

      You can then create whatever other rule you need based on the rate fetched.

      I tested this; works fine. Here's the rule that does the fetch every day at midnight:

      f3f53e15-8289-4b02-a399-82f6738640a5-image.png

      And here is what the expressions look like:

      31e9b926-ba4c-4812-a6cd-f4720ba723eb-image.png

      You will also need to set http_request_action_maxresponse in the engine section of your reactor.yaml file to a value large enough to contain the result. I just set it to 256 (units are kilobytes). It appears that the structure of the URL may offer some control over the number of entries returned, so you might consider using that to reduce the overhead.

      Edit: sure enough, if you change the "90" in the URL to a smaller number, it returns that many days of info, so use something like 7 and you'll reduce the query overhead considerably. You really only need today's anyway, right? (so maybe even 1 or 2 would work?)

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      T 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        @talisker That's JSON. It's doable, but not trivial for the new players.

        I would first set up a Rule to query the server each day at a particular time. That rule would use an HTTP Request action to store the response into a global variable (let's call it energy_data). You need to create the global variable first, just leave the expression blank.

        Then make another global expression to fetch and hold the rate for today from the response by using the first statement to go through energy_data.periods until it finds the entry with date matching today's date... it would look something like this

        first entry in energy_data.periods with entry.date == strftime( "%F" ): entry.unit_rate
        

        (assuming unit_rate is the correct key/field in the entry; if not, just use the correct key name).

        You can then create whatever other rule you need based on the rate fetched.

        I tested this; works fine. Here's the rule that does the fetch every day at midnight:

        f3f53e15-8289-4b02-a399-82f6738640a5-image.png

        And here is what the expressions look like:

        31e9b926-ba4c-4812-a6cd-f4720ba723eb-image.png

        You will also need to set http_request_action_maxresponse in the engine section of your reactor.yaml file to a value large enough to contain the result. I just set it to 256 (units are kilobytes). It appears that the structure of the URL may offer some control over the number of entries returned, so you might consider using that to reduce the overhead.

        Edit: sure enough, if you change the "90" in the URL to a smaller number, it returns that many days of info, so use something like 7 and you'll reduce the query overhead considerably. You really only need today's anyway, right? (so maybe even 1 or 2 would work?)

        T Offline
        T Offline
        Talisker
        wrote on last edited by
        #5

        @toggledbits thank you once again! Very clear instructions. I am now up an running and have opened up new opportunites to extend my automation.

        Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

        1 Reply Last reply
        1
        • tunnusT tunnus referenced this topic on
        • T Offline
          T Offline
          Talisker
          wrote on last edited by Talisker
          #6

          I have made an http request and get the following JSON response which I have stored in a global variable gas_consumption (like the example above). See below.

          I have then tried to the following expression to extract the consumption value:

          0818a20e-2700-4a4c-a9be-47a64f452051-image.png

          Clearly the returned data "results" is not published for today (strftime( "%F) i.e. 4/9/2022.

          How do I extract the gas consumption for a particular date?
          How do I extract yesterday's gas consumption (in the case of the response below 3/9/2022)?

          ===group

          {
          	"count": 482,
          	"next": "https://api.octopus.energy/v1/gas-meter-points/xxxxxxxxxxx/meters/xxxxxxxxxxx/consumption/?format=json&group_by=day&page=2&page_size=10",
          	"previous": null,
          	"results": [{
          		"consumption": 0.0,
          		"interval_start": "2022-09-03T00:00:00+01:00",
          		"interval_end": "2022-09-03T01:00:00+01:00"
          	}, {
          		"consumption": 1.077,
          		"interval_start": "2022-09-02T00:00:00+01:00",
          		"interval_end": "2022-09-03T00:00:00+01:00"
          	}, {
          		"consumption": 0.669,
          		"interval_start": "2022-09-01T00:00:00+01:00",
          		"interval_end": "2022-09-02T00:00:00+01:00"
          	}, {
          		"consumption": 0.761,
          		"interval_start": "2022-08-31T00:00:00+01:00",
          		"interval_end": "2022-09-01T00:00:00+01:00"
          	}, {
          		"consumption": 0.614,
          		"interval_start": "2022-08-30T01:00:00+01:00",
          		"interval_end": "2022-08-31T00:00:00+01:00"
          	}, {
          		"consumption": 0.0,
          		"interval_start": "2022-08-29T00:00:00+01:00",
          		"interval_end": "2022-08-29T01:00:00+01:00"
          	}, {
          		"consumption": 0.569,
          		"interval_start": "2022-08-28T00:00:00+01:00",
          		"interval_end": "2022-08-29T00:00:00+01:00"
          	}, {
          		"consumption": 0.0,
          		"interval_start": "2022-08-27T00:00:00+01:00",
          		"interval_end": "2022-08-28T00:00:00+01:00"
          	}, {
          		"consumption": 0.455,
          		"interval_start": "2022-08-26T00:00:00+01:00",
          		"interval_end": "2022-08-27T00:00:00+01:00"
          	}, {
          		"consumption": 0.681,
          		"interval_start": "2022-08-25T00:00:00+01:00",
          		"interval_end": "2022-08-26T00:00:00+01:00"
          	}]
          }
          
          ===

          Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

          T 1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by toggledbits
            #7

            You are on the right track. The problem with what you are doing is:

            1. Your are comparing entry.date in the loop, but date is not a field in those structures. I believe you mean to use interval_start. Also, gas_consumption used to get the result is not the correct name/key either.
            2. If you were to create a separate test variable using strftime("%F") as the entirety of its expression, I think you will quickly see the problem with the value being generated vs what you are trying to compare it to. I've done that below. See the problem? I'll leave it to you for the moment to come up with a fix.

            8985d2ac-5dbc-4088-9f27-f2799bf12a90-image.png

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            1 Reply Last reply
            0
            • T Talisker

              I have made an http request and get the following JSON response which I have stored in a global variable gas_consumption (like the example above). See below.

              I have then tried to the following expression to extract the consumption value:

              0818a20e-2700-4a4c-a9be-47a64f452051-image.png

              Clearly the returned data "results" is not published for today (strftime( "%F) i.e. 4/9/2022.

              How do I extract the gas consumption for a particular date?
              How do I extract yesterday's gas consumption (in the case of the response below 3/9/2022)?

              ===group

              {
              	"count": 482,
              	"next": "https://api.octopus.energy/v1/gas-meter-points/xxxxxxxxxxx/meters/xxxxxxxxxxx/consumption/?format=json&group_by=day&page=2&page_size=10",
              	"previous": null,
              	"results": [{
              		"consumption": 0.0,
              		"interval_start": "2022-09-03T00:00:00+01:00",
              		"interval_end": "2022-09-03T01:00:00+01:00"
              	}, {
              		"consumption": 1.077,
              		"interval_start": "2022-09-02T00:00:00+01:00",
              		"interval_end": "2022-09-03T00:00:00+01:00"
              	}, {
              		"consumption": 0.669,
              		"interval_start": "2022-09-01T00:00:00+01:00",
              		"interval_end": "2022-09-02T00:00:00+01:00"
              	}, {
              		"consumption": 0.761,
              		"interval_start": "2022-08-31T00:00:00+01:00",
              		"interval_end": "2022-09-01T00:00:00+01:00"
              	}, {
              		"consumption": 0.614,
              		"interval_start": "2022-08-30T01:00:00+01:00",
              		"interval_end": "2022-08-31T00:00:00+01:00"
              	}, {
              		"consumption": 0.0,
              		"interval_start": "2022-08-29T00:00:00+01:00",
              		"interval_end": "2022-08-29T01:00:00+01:00"
              	}, {
              		"consumption": 0.569,
              		"interval_start": "2022-08-28T00:00:00+01:00",
              		"interval_end": "2022-08-29T00:00:00+01:00"
              	}, {
              		"consumption": 0.0,
              		"interval_start": "2022-08-27T00:00:00+01:00",
              		"interval_end": "2022-08-28T00:00:00+01:00"
              	}, {
              		"consumption": 0.455,
              		"interval_start": "2022-08-26T00:00:00+01:00",
              		"interval_end": "2022-08-27T00:00:00+01:00"
              	}, {
              		"consumption": 0.681,
              		"interval_start": "2022-08-25T00:00:00+01:00",
              		"interval_end": "2022-08-26T00:00:00+01:00"
              	}]
              }
              
              ===
              T Offline
              T Offline
              Talisker
              wrote on last edited by
              #8

              Background to the question
              I've been experimenting a little and I need help. If I use the following expression:

              03c304e5-fbfb-4895-9147-7ef0ea1d6592-image.png

              I get the correct response (i.e. today's day number '16'th).

              I can use this in a HTTP requst to download some tarrif information via an API from my energy supplier - i.e. today's gas unit rate tariff

              What I'd like to do

              I would like to download tomorrow's gas unit rate tariff. To do this I need to set up and expression with today's date + 1 day (in the case of my example expression above that would be '17' (today being the 16th).

              Question: How do I take today's date and add 1 day - so that I can make the HTTP request for tomorrow's information?

              Any guidance or suggestions would be appreciated.

              Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #9

                Read the docs for Expressions (the Date/Time handling section in particular) and familiarize yourself with the tools available. I'll give you a couple of pointers:

                The time() function can take arguments in several forms to build any reasonable date. The dateparts() function will return any timestamp or the current time/date as its components (hour, minute, year, month, day, etc., and better than using strftime() for the purpose).

                Special hint: if you tell time() to make a timestamp for July 32, 2022, it will give you a timestamp for August 1, 2022 without complaint.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                T 1 Reply Last reply
                1
                • toggledbitsT toggledbits

                  Read the docs for Expressions (the Date/Time handling section in particular) and familiarize yourself with the tools available. I'll give you a couple of pointers:

                  The time() function can take arguments in several forms to build any reasonable date. The dateparts() function will return any timestamp or the current time/date as its components (hour, minute, year, month, day, etc., and better than using strftime() for the purpose).

                  Special hint: if you tell time() to make a timestamp for July 32, 2022, it will give you a timestamp for August 1, 2022 without complaint.

                  T Offline
                  T Offline
                  Talisker
                  wrote on last edited by
                  #10

                  @toggledbits Thanks for the prompts, following which I made some progress:
                  6f968ae5-b0b6-4d54-9b46-6441c90cf73e-image.png

                  I have Test51 which contains tomorrow's date, but I am struggling to get the time in a sting representation. I am trying to represent the day in Test53 expression but I have a syntax error.

                  I would appreciate some more guidance.

                  Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

                  1 Reply Last reply
                  1
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by toggledbits
                    #11

                    THAT is the proper use of strftime(). The time is the (optional) second argument (i.e. you don't write Test53.strftime(...), you write strftime( "%F %T", Test53)). Again, read the docs. strftime() is a Reactor-specific function, documented lower down on the page.

                    Edit: specific correction for clarity.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    T 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      THAT is the proper use of strftime(). The time is the (optional) second argument (i.e. you don't write Test53.strftime(...), you write strftime( "%F %T", Test53)). Again, read the docs. strftime() is a Reactor-specific function, documented lower down on the page.

                      Edit: specific correction for clarity.

                      T Offline
                      T Offline
                      Talisker
                      wrote on last edited by
                      #12

                      @toggledbits Thanks for your pointers. Partial success:
                      6df6b31f-039d-4fd6-9c8d-15784218cbe4-image.png

                      However, the expressions do not update! I use Tomorrow_Date in a Rule (HTTP Request):

                      https://api.octopus.energy/v1/products/SILVER-22-04-25/gas-tariffs/G-1R-SILVER-22-04-25-M/standard-unit-rates/?page_size=10&period_from=https://api.octohttps://api.octopus.energy/v1/products/SILVER-22-04-25/gas-tariffs/G-1R-SILVER-22-04-25-M/standard-unit-rates/?page_size=10&period_from=**${{Tomorrow_Date}}**&order_by=period

                      Is there a way to force an update on selected expressions, say at a set time every day?

                      Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

                      1 Reply Last reply
                      0
                      • toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by
                        #13

                        Can you show your rule?

                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                        T 1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          Can you show your rule?

                          T Offline
                          T Offline
                          Talisker
                          wrote on last edited by
                          #14

                          @toggledbits 2aae465d-b404-43f1-babe-0f12435a73eb-image.png

                          No Reset Reaction or Local Expressions are set.

                          The request URL is:
                          https://api.octopus.energy/v1/products/SILVER-22-04-25/gas-tariffs/G-1R-SILVER-22-04-25-M/standard-unit-rates/?page_size=10&period_from=https://api.octohttps://api.octopus.energy/v1/products/SILVER-22-04-25/gas-tariffs/G-1R-SILVER-22-04-25-M/standard-unit-rates/?page_size=10&period_from=${{Tomorrow_Date}}&order_by=period

                          Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by
                            #15

                            OK. Move your global expressions into your rule so they are rule-based expressions. They will update each time the Interval triggers.

                            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                            1 Reply Last reply
                            0
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            Recent Topics

                            • Gradually turn on lights.
                              G
                              gwp1
                              0
                              4
                              94

                            • Stop the MSR by an external switch on Hubitat.
                              wmarcolinW
                              wmarcolin
                              0
                              1
                              16

                            • Error After Upgrade
                              G
                              gwp1
                              0
                              4
                              86

                            • Reset attribute value of entity in event handler
                              R
                              RHCPNG
                              0
                              5
                              170

                            • Need help figuring out how to delay a reset on reaction
                              G
                              gwp1
                              0
                              22
                              860

                            • Way to search for rules (rule state) in other rules
                              T
                              tamorgen
                              0
                              3
                              92

                            • Links to MSR from HA
                              Tom_DT
                              Tom_D
                              0
                              1
                              78

                            • Set Reaction > Script Action
                              wmarcolinW
                              wmarcolin
                              0
                              11
                              419

                            • Wiring Samotech SM308-S into light fitting
                              akbooerA
                              akbooer
                              0
                              2
                              136

                            • Errors after updating to MQTTController build 25139
                              toggledbitsT
                              toggledbits
                              0
                              6
                              232

                            • 🎉 My very first MSR controller: OpenSprinkler
                              therealdbT
                              therealdb
                              5
                              13
                              898

                            • Advice reqeusted to migrate MSR from Bare Metal to Container
                              T
                              tamorgen
                              0
                              5
                              246
                            Powered by NodeBB | Contributors
                            Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • Unsolved