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.
T

Talisker

@Talisker
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
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
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
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
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
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
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
About
Posts
47
Topics
9
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • New HA instance
    T Talisker

    @CatmanV2 what device (hub) fo you use to connect your z-wave devices? I'm using my old vera but at some point I need to decide what to replace it with. I agree with your comment about the strengths of HA and MSR.

    Home Assistant

  • Critical Disk Space Warning
    T Talisker

    I updated to the latest version of Reactor this morning. I run reactor (successfully) on a Raspberry PI 4 4GB with SSD 64GB. I also run Home Assistant in Docker. After updating I noticed a disk space critical error warning!

    9f4e1ea1-977a-481b-9806-d3d43a4eff04-image.png

    I have tried purging the docker install (docker image prune -a)

    I have rebooted the Raspberry PI also, and the error messages keep coming.

    I have the following disk space:

    58742ed7-e10d-4572-b380-0abda64f90b4-image.png

    How do I free up space?

    Any help would be appreciated.

    Multi-System Reactor

  • MSR setup for http request (today's date)
    T Talisker

    @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

    Multi-System Reactor

  • MSR setup for http request (today's date)
    T Talisker

    @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?

    Multi-System Reactor

  • MSR setup for http request (today's date)
    T Talisker

    @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.

    Multi-System Reactor

  • MSR setup for http request (today's date)
    T Talisker

    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.

    Multi-System Reactor

  • Reactor not showing full vera device parameters
    T Talisker

    So, I have found my missing parameters! They appeared following a reactor update. Perhaps next time I add new vera devices, I should stop reactor and re-start it after I have added the new devices and things have settled down. Anyhow, thanks again for your assitance Patrick.

    Multi-System Reactor

  • Reactor not showing full vera device parameters
    T Talisker

    I have a number of rules which using entity actions I write values into multistring devices in my vera plus. Below is an example of how I do this in Reactor:

    Untitled.png

    If I add a new multistring device in my vera plus I cannot set the device variables as I can with 'old' multistring devices. The below screen shot shows that the same drop down menu options in reactor for the new multistring device are not present as they are for the old device above:

    Untitled.png

    If I look at the reactor entities for an old multistring entity (device #887) and a newly created multistring entity (device number '1056) I can spot a difference as per the screen shot below. I guess my question is 'why are the available actions not listed for new multistring devices (entities))?

    Capture.JPG

    Multi-System Reactor

  • Reactor not showing full vera device parameters
    T Talisker

    @toggledbits it appears that I used the wrong terminology. I have looked at the two Reactor logs (vera-user_data-initial.json and vera-status-initial.json files) again, comparing the attributes for 1056 and 1057 against other devices, the respective attributes don't seem out of place. All attributes are listed for the two multistring devices (or should I say they appear to be listed). See below for device 1056. Does this confirm that the attributes for the two new entities (devices) are being read correctly by reactor?

    vera-status-initial.json

    {
    "id": 1056,
    "states": [
    {
    "id": 334,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName1",
    "value": "Y'day Gas kWh"
    },
    {
    "id": 335,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable1",
    "value": "99"
    },
    {
    "id": 336,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName2",
    "value": "V2"
    },
    {
    "id": 337,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable2",
    "value": "0"
    },
    {
    "id": 338,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName3",
    "value": "V3"
    },
    {
    "id": 339,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable3",
    "value": "0"
    },
    {
    "id": 340,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName4",
    "value": "V4"
    },
    {
    "id": 341,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable4",
    "value": "0"
    },
    {
    "id": 342,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName5",
    "value": "V5"
    },
    {
    "id": 343,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable5",
    "value": "0"
    },
    {
    "id": 344,
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Options",
    "value": ""
    },
    {
    "id": 345,
    "service": "urn:micasaverde-com:serviceId:HaDevice1",
    "variable": "Configured",
    "value": "0"
    }

    vera-user_data-initial.json:

    {
    "id": 1056,
    "device_type": "urn:schemas-upnp-org:device:VContainer:1",
    "id_parent": 0,
    "embedded": 0,
    "disabled": 0,
    "device_file": "D_MString.xml",
    "manufacturer": "",
    "model": "",
    "altid": "",
    "ip": "",
    "mac": "",
    "time_created": "1662320801",
    "plugin": "8231",
    "states": [
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName1",
    "value": "Y'day Gas kWh",
    "id": 0
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable1",
    "value": "99",
    "id": 1
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName2",
    "value": "V2",
    "id": 2
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable2",
    "value": "0",
    "id": 3
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName3",
    "value": "V3",
    "id": 4
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable3",
    "value": "0",
    "id": 5
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName4",
    "value": "V4",
    "id": 6
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable4",
    "value": "0",
    "id": 7
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "VariableName5",
    "value": "V5",
    "id": 8
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Variable5",
    "value": "0",
    "id": 9
    },
    {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "variable": "Options",
    "value": "",
    "id": 10
    }
    ],
    "impl_file": "I_MString.xml",
    "ControlURLs": {
    "service_514": {
    "service": "urn:upnp-org:serviceId:VContainer1",
    "ControlURL": "/upnp/control/dev_514",
    "EventURL": "/upnp/event/dev_514",
    "serviceType": "urn:schemas-upnp-org:service:VContainer:1"
    }
    },
    "device_json": "D_MString.json",
    "name": "Gas_Params",
    "room": "11",
    "local_udn": "uuid:4d494342-5342-5645-0420-000002fc93e7"
    },

    Multi-System Reactor

  • Reactor not showing full vera device parameters
    T Talisker

    Please find my responses below. I fear you may be frustraited by my lack of knowlege but I have done my best based on your guidance. I am not able to upload the logs. Do you need these?

    Sorry about the thumbnail screen shots - I could not find a better way to capture them!

    'I would look at the attributes listed for the entities in the Entities list.' So the unreadable thumbnail images showed that the expected entities for the two new vera multistring devices are not available in Reactor.

    I have looked at the vera logs (http://192.168.XX.XXX/cgi-bin/cmh/log.sh?Device=LuaUPnP after a luup reload. If I search for the two new multistring devices (1056 & 1057) the entries looked quite normal compared to the log entries for similar devices. So I assume no vera error?

    I have looked at the two Reactor logs (vera-user_data-initial.json and vera-status-initial.json files) again, comparing the entries for 1056 and 1057 against other devices, the respective lines don't seem out of place. All entities are listed for the two multistring devices.

    Multi-System Reactor

  • Reactor not showing full vera device parameters
    T Talisker

    Yes Patrick. I also tried an alternative browser. Tried a hard re-boot also on my Pi4.

    Multi-System Reactor

  • Reactor not showing full vera device parameters
    T Talisker

    I use a number of multistring devices in my vera plus. My 'original' multistring devices work in Reactor i.e.:

    9c5203dd-1993-4b5b-aeee-44377c1ee1c5-image.png

    42b97524-9428-4222-a3fb-ce4e0009c00b-image.png

    However, the new ones I have added do not show the device data sets / parameters (not sure what the correct term is?):

    a54ddf29-ea32-47c9-906e-260a25dcb482-image.png

    3efa1d0a-5466-4220-93d3-0a67da42a5d0-image.png

    Is there something that I am doing wrong?

    Multi-System Reactor

  • MSR setup for http request (today's date)
    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"
    	}]
    }
    
    ===
    Multi-System Reactor

  • MSR setup for http request (today's date)
    T Talisker

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

    Multi-System Reactor

  • MSR setup for http request (today's date)
    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

    Multi-System Reactor

  • MSR setup for http request (today's date)
    T Talisker

    I would like to extract the daily gas price from my fuel supplier's API. The http call is as follows: https://octopus.energy/api/v1/tracker/G-1R-SILVER-2017-1-M/daily/past/90/1/

    I need to pick the current (i.e. today's) gas price. If I search through the text manually I can find today's data, in this case 2022-07-20.

    Can I set MSR up to do a http request and then extract the "unit_rate" into a variable so that I can set another rule up to determine if it would be cheaper to heat my hot water using the immersion heater or gas (FYI my off peak electricity price is £0.075 per kwh). Any help or guidance as always is much appreciated.

    I'm running MSR on raspberry PI 4 in docker version 22168

    Thanks.

    {
    		"date": "2022-07-20",
    		"market_index": 62.8463,
    		"cost": 15.094631164947945,
    		"standing_charge": 15.0885,
    		"unit_rate": 8.211,
    		"usage": 0.0007467013698630137,
    		"unit_charge": 0.0061311649479452055,
    		"breakdown": {
    			"unit_charge": {
    				"Wholesale cost": 6.28463,
    				"Environmental & social obligations": 0.0,
    				"Delivery & networks": 0.9681,
    				"100% green": 0.0,
    				"Administration, financing & margin": 0.56727,
    				"VAT": 0.391
    			},`
    Multi-System Reactor

  • Copying configuraiton and rules from QNAP install to Raspberry PI 4 install
    T Talisker

    Sorry @toggledbits . I tied it again after a good break and it appears to work fine. I honestly don't know what was going wrong but things seem to now be in order:

    pi@raspberrypi:~ $ cd reactor
    pi@raspberrypi:~/reactor $ ls
    config docker-compose.yml logs storage
    pi@raspberrypi:~/reactor $ docker-compose down
    Stopping reactor ... done
    Removing reactor ... done
    Removing network reactor_default
    pi@raspberrypi:~/reactor $ docker-compose pull
    Pulling reactor ... done
    pi@raspberrypi:~/reactor $ docker-compose up -d
    Creating network "reactor_default" with the default driver
    Creating reactor ... done

    docker-compose.yml below FYI:

    Multi-System Reactor template docker-compose.yml (version 22160)

    Change the lines indicated by "DO"...

    version: '3'

    services:
    reactor:
    container_name: reactor
    environment:
    # DO change the TZ: line to set your local time zone.
    # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
    TZ: GB
    #
    # DO NOT change this path. Your directory location is in "source" below.
    REACTOR_DATA_PREFIX: /var/reactor

    # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
    image: toggledbits/reactor:latest-aarch64
    
    restart: "always"
    expose:
      - 8111
    ports:
      - 8111:8111
    volumes:
        # DO change the /home/username/reactor below to the directory you created for
        # your local data; DO NOT change the /var/reactor part
      - /home/pi/reactor:/var/reactor
      - /etc/localtime:/etc/localtime:ro
    tmpfs: /tmp
    
    Multi-System Reactor

  • Copying configuraiton and rules from QNAP install to Raspberry PI 4 install
    T Talisker

    @toggledbits something is not working quite right with my docker install (docker-compose). Not sure where to start!

    815c9e37-4c43-42dc-b343-258a9016cff8-image.png

    Multi-System Reactor

  • Copying configuraiton and rules from QNAP install to Raspberry PI 4 install
    T Talisker

    @toggledbits thanks for the methodology. I manged to copy the files from a usb stick to the relevant folders using the sudo cp command. Feeling pretty pleased as I am now up an running on my raspberry pi.

    Multi-System Reactor

  • Copying configuraiton and rules from QNAP install to Raspberry PI 4 install
    T Talisker

    @catmanv2 I tried that thanks and it works:

    sudo docker stop reactor #stops reactor
    sudo service docker restart #starts reactor

    Cheers!

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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