-
Been trying to call the service automation:trigger to trigger an automation on my HA. Below is the screenshot of the reaction but every time I hit the play button to test it nothing happens. I called the service locally on HA and it worked fine. MSR latest-22203-d7cd6357 and HA 2022.8.3. No errors in HASS logs or Reactor logs. 715cd920-effd-4d31-8ac3-ba34ef29185c-image.png
-
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan -
I have the following rule:
Screenshot 2022-08-09 at 17.33.39.png
Use this to detect errors in Nibe uplink service, and every time updated data is fetched, a timestamp is stored. This triggered already yesterday, but re-triggered as I tried to manually recover this rule with a reset (hence there's no original "true as of xxx" time).
So as a clarification, service works now and timestamps are updated, but this rule does not "recover" (stays triggered / SET). Did also restart MSR during this situation, though it was not related to this.
The condition where there was no change (and rule was working correctly) lasted over 24 hours.
Running MSR 22179 on Synology Docker. Can PM relevant logs if needed.
-
I'd like to extract a specific part of a response to http request, in this case of link https://www.nibeuplink.com/Welcome#service_message. If there's something in "service_message" I'd store it & send using Telegram.
I reckon I'd have to use something similar as in this thread?
-
Deleted some entities from HA and added some new ones but MSR is still showing the old ones and not all of the new ones. I restarted MSR and it hasn't changed, is there anyway to manually discover new entities and delete the old ones? Most of the new entities have shown up but a few haven't, however none of the deleted entities were removed from MSR.
I checked the core.entity_registry in HA and none of the entities that are shown in MSR are there.
Edit: I see the delete option under the entities tab in MSR, is that the only way to delete them?
-
Successfully got MSR to run on a VM running Ubuntu 22.04 but am running into an issue with getting to run MSR as a service. Here is what my reactor.service file looks like below.
However when I go to run the service I see this error: reactor.service: Failed at step CHDIR spawning /usr/bin/node: No such file or directory. Checked and the node file exists in this directory. Kinda stuck at this point, probably a simple fix but I am way in over my head 😰
[Service] Type=simple User=armans2 WorkingDirectory=/home/reactor Environment=/home/reactor ExecStart=/usr/bin/node app -p Restart=on-failure RestartSec=5s -
Hey crew,
I'm running into an issue where MSR's reactions aren't successfully running, and I can't figure out what's gone wrong.Backstory-- we had a big thunderstorm roll through the other day, we lost internet and the storm got bad so I unplugged most items in my homelab, including the Pi that's running MSR.
Now that everything is powered back up, the reactions aren't running correctly. Most of my MSR automations are to use motion sensors to turn lights on/off, and I immediately noticed that even when a motion sensor is tripped, the light doesn't turn on like it's supposed to.
I've tested a bunch of things to see what's broken, here's what I've observed:
-I can successfully flip lights on/off manually within Vera
-I can successfully flip lights on/off manually within MSR's Entities section
-the motion motion sensors are correctly reporting to Vera and MSR (I can see when they're sensing motion)
-the rules within MSR are working correctly, I can see when they flip to 'true' when I walk by a motion sensor
-I can successfully run the Reaction within MSR (by hitting the 'play' button)But for whatever reason, when everything needs to work together, it doesn't successfully run the action. IE: the motion sensor trips, reports it to MSR, I can see MSR going "true" but the light does not turn on. Open to any suggestions, thank you!
SYSTEM
Vera has all my devices
MSR is running bare metal on Rpi "Reactor (Multi-hub) stable-22004-6d6c6b7" -
Apologies in advance, I expect I am going to make a total pig's ear of explaining, so please bear with me....
(and if it's in the manual, just tell me to read the manual)Going back to my heating scenario:
We have an alarm clock that goes off at a variable time.
We want the heating to go off at a time before that (1 hour)
so we have created the rule set as below:
Screenshot 2022-07-28 at 16.40.13.pngSo if current time is >= to the HeatTime, the first condition goes true.
The second condition is to ensure that nothing (tries to) turn(s) the heating off during that 1 hour window
The interval is there because in Reactor there was precisely that to (from memory) 'make sure the variables updated'
In the current state it kind of works. There is no Reset action, so the heat goes on once every 15 minutes during that hour.
In Reactor I didn't have to include the interval in the rule set. It was a stand alone rule as here:
Screenshot 2022-07-28 at 16.47.23.pngIf I move the Interval condition out of the rule set in MSR, things do not update as time changes (and the rule never sets)
So I guess the question I'm trying to ask it 'what causes expressions like
time() >= HeatTimeTo be evaluated, and is there a better way than I've done here?
Apologies again 😞
C
-
I've been running into an issue with a couple APIs wherein they return the error FetchError: network timeout....
A retry resolves but my ask here is around how I can monitor within MSR and trigger (at least) a notification if not a retry after a short delay.
-
Hi All -
I'm currently working through a slow migration from Vera to Home Assistant with MSR being a pivotal piece of the equation.
I have begun the effort of moving some ZWave devices as well (from Vera to HA). Unlike others that use Vera for the ZWave radio, I'm looking to completely remove it from my ecosystem, eventually.
My issue is I have some Vera Scenes that are designed to be manually executed by the Vera Mobile app. Examples: "Go to Sleep", "Panic - Lights On", etc (Wife Acceptance Factor)
I think MSR is the right place for any new "Scene" (including manual scenes); and from my reading, a Global Reaction makes sense.
Question 1: Can anyone recommend a way to execute a Global Reaction from a Vera scene? I've seen some examples of HTTP calls to MSR so I assume this is it (perhaps custom Luup which I know very little about).
Question 2: How can I (manually) execute this Reaction from Home Assistant? I'm slowly building out my custom Dashboard using "Mushroom".
Or, maybe there's a better way. Always open to constructive criticism.
Thanks.
-
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 },` -
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. -
Well the use of expressions in my Idiot Question over there has opened many new and exciting doors which I am itching to run through. This one has slammed in myu face 😞
So in reactor we have an expression:
getstate( 46, "urn:upnp-org:serviceId:VClock1", "AlarmTime" )
which returns
Last result: "05:15:00"
Then we convert this to time one hour earlier:
time(AlarmTime) - 3600
which returns
Last result: 1658373300Cool!
In MSR:
getstate is not supported
getEntity("vera>AlarmClock").attributes.x_vera_svc_upnp_org_VClock1.AlarmTime
Returns:
Last value: (string) "05:15:00"
Marvellous!
time (AlarmTime)
Returns
Last value: (null) nullBoo! Hiss!
OK seriously, is there a reference I've missed or somewhere I can look at this stuff. time() in Lua returns the epoch time which is fab, but what's my equivalent to the time usage in Reactor?
TIA
C -
Starting to (very slowly) migrate and improve some of my automation from Reactor to the fabulous MSR. Couple of questions which are probably really obvious but, well, you know me 😞
Is it possible to repeat an action from a set rule? i.e. if the rule remains triggered for an hour, re-run the set reaction. And to continue re-running that every hour until the rule is reset?
Sorry if it's really stupid.
C
-
Hi, I have a rule that I have been using in the Vera version of Reactor for a number of years and I am trying to recreate it in MSR and need some advice. The rule monitors the state of our garage door and sends a regular alert if the door has been open for a period of time. The alert contains a variable/expression that provides the duration in minutes the door has been open - eg the end notification looks like this: "The door has been open for X minutes"
I have everything working OK in MSR except for constructing the expression to provide the duration the door has been open. In Reactor I was using the 'getstate' function in an expression to get the runtime of the rule and then converting that to minutes and passing it to the notify action.
In MSR I can't work out how to get any info from a rule within an expression.
The trigger is a simple pulse every X minutes so I was hoping it would be possible to just get the duration of either the rule or the time the door has been open. In the documentation there is a lot of info on getting details of entities, but I couldn't find anything on getting the status of the rules within MSR as it doesn't look like they show up as entities? I hope I didn't miss that part of the doco.
I did a bit of searching but couldn't find any discussion on getting this type of info so I'm hoping someone will be able to point me in the right direction.
I'm using build 22179 on Docker and the devices are currently in Vera but I am likely to move them to HASS at some point.
-
EDIT: 2022.07.01
So I will try to remake this thread to some kind of guide for future use, or in worst case a documentation of my failure. At least that could also be useful for letting someone know what didn't work...
I have zero knowledge of programming, so every time I need to edit a config file in HomeAssistant or similar it requires a good portion of googletime and read, re-reading instructions.
Also is english not my native language, so bear with me.Two goals!
1: Get MSR to take notice (and then actions of course) of pressed buttons on remotes.
2: Document what I do in hope I can help someone else in the future.I will use a Fibaro Keyfob as described below, but what I understand from Togglebits answers most type of remotes should work in similar ways.
Original thread:
Fibaro Keyfob support in MSR? (thru Hassio & Z-wave JS)
HiI just bought a Fibaro Keyfob FGKF-601 and plan to give this to my son so he can control some stuff in his own room. Primary some lightning and Sonos, maybe blinds in the future.
As the noob I am it will, of course, not work as I expected.👶🏻
The remote handle 1x, 2x, 3x clicks per button (six of them) and "release button"
I thought that it would appear like some "scene controller" in HA and that I could make Rules in MSR depending on what scene-entety that was triggered.
So is not the case, and if that is because of HA, Z-wave JS or MSR I have no idea.
I found a HA Blueprint that works in HA, but of course I would prefer to keep all automation in MSR.
I guess a workaround could be using HA virtual switches "Helpers" that I suppose will come up as an on/off trigger in MSR, but before going this way I would like to check with the wisdom of your guys if there is a better way of doing this.I am using:
MSR 22168 on windows.
Home Assistant Core 2022.6.7
Home Assistant Supervisor 2022.05.3
Home Assistant OS 7.6
Z-Wave JS version: 0.1.64 -
Need to ask, have thougth about this since the move from Rector to MSR I think.
What is the difference between putting constraints under trigger groups, like this
23b4a249-3292-41cd-9927-7f49c9bf1d07-image.pngCompared to this similar rule, but the time limits is under contraints instead?
ee596c9f-f52b-4a39-9605-f5932f3d9ed5-image.pngI think the Constraints parts in manual is still to be done because I can only find in the chapter menu, but it is not mentioned anywhere else.
-
Did anyone do/start any work on a full integration with The Home Remote application yet?
-
Running MSR 22123 in Docker container and trying to use "condition must occur after" option. Will update to the latest build and log a PR if needed, but wanted to poll first if anyone is using this option successfully?
I have the following rules:
Screenshot 2022-06-28 at 15.18.50.png
Notification activity connected to "Alarm disabled" rule did not trigger. I also did another test with quite simple rules and that didn't work either (FWIIW - when observing that test in "real-time", I didn't see any timer running on the second rule while the first rule was true).
As said, before going further with debug/logs, nice to know if someone is using this option/restriction (successfully).
[Solved] HASS.OS Install
-
Hi,
Am I correct in assuming that MSR cannot be installed on a pi running HASS.OS?
Thanks.
-
@vezinpi probably doable. I haven't tried it myself, but if you can install either nodejs or docker, you're almost done.
-
Hi,
I am just a regular user with good system understanding but I am not a software person by any means. Therefore, take the following with that in mind.
I feel myself trapped between HASS recommanded install for a Raspberry Pi, and MSR recommanded install. They are not compatible...
HASS recommanded install is using the Home Assistant Operating System, a controlled environment where the user do not have control over the OS. The good point, it is simple, very stable and protected against noice user like me. On the other hand it make it difficult to do anything else like installing MSR. Trough the Portainer Add-On, I manage to install the MSR container and to configure it to see my Vera and HASS devices. The problem is that the configuration is within the container and when we upgrade or remove the container, the configuration is lost.
The fact that the standard MSR container is running just fine (beside the config) means that the configuration is compatible with HASS OS. I understand your approach (not being system dependent like Reactor was with Vera) by providing either a generic container or tar ball but it implies having a device on which we have the control over the OS. Your actual container for Pi is so close from being an official add-on I wonder if it would not worth the effort. I even see a benefit for you when trouble shooting. The Hass OS environment being almost lock, it can become somewhat of a referece when chasing down an issue with MSR. How many problem are due to the user changing something it is not supposed to. The other thing is, how many users out there, like me, are using the Pi image or the Home Assistant BLUE platform.
I have been using (and contributed) Reactor and Virtual switches with my Vera and I definitely want to go that route with MSR and HASS. I will re-install HASS with an alternate method if I have to, but it is not my first choice if I can avoid it. Again, being just a regular user, simplicity is paramount and the HASS image was pretty good. If MSR could be an add-on, it would be fantastic.
For your consideration.
Thanks
-
You are blazing new territory by running under the packaged, container HassOS. But it sounds like you're close.
Generically, docker containers allow you to "mount" a point in the OS' filesystem within the container; this is called a bind mount. This is the mechanism by which the configuration and log files are normally preserved outside the container on all other systems in which MSR docker containers run. In this way, replacement of the container and/or underlying image does not cause data loss (configuration, state, logs, etc.), because the data is no longer stored within the container.
What you need to figure out is how to get the
/var/reactordirectory inside the container mounted to an accessible, persistent location outside the container. For example, you may create a directory in your user home directory/home/username/reactor-data, and create a bind mount that mounts that directory over/var/reactorinside the container. Portainer generically allows you to create bind mounts to places in the filesystem, so I assume this is readily possible, but not being familiar with the specifics of how HassOS handles (and more importantly, restricts) its filesystem(s), I can't give you specific guidance. -
Hi again,
Just thought I would provide an update on where I am at. I might also be helpfull to other people.
As you know, I am trying to get the MSR Container work on a Pi-4, configured with the standard HASS operating system (image via balena etcher). Well I finally found a solution to data persistance between reboot. Here is what I did:
-
Installed samba add-on to get accesss to the standard Hass configuration folders
-
Installed Portainer which will be used to install MSR
-
From within Portainer, add an MSR container with the following configuration: image: toggledbits/reactor:latest-raspbian-armv7l, add a TZ variable with the proper region, restart policy define On failure, add a bind volume to map the reactor container /var/reactor to the host /mnt/data/supervisor/homeassistant/reactor. This (reactor) folder will be accessible via the samba addon under the config folder.
-
Restarted the MSR container
The reactor.yaml configuration file is now accessible via samba under homeassistant/config/reactor/config or from a terminal sessison performed from portainer in the var/reactor/config folder.
All seems to work for now. Devices from vera and HASS are being seen by MSR. Configuration persist trough a reboot and I was also able to import (convert using the tool provided) my configuration from Reactor. I am now in the process of making the final adjustment.
Not sure what will the future hold but for now it is working fine.
Many thanks for your work and support.
-
-
In hassos you can install an addon "portainer" and with the needed "settings" you can run your own dockers very easily besides the other containers (of which homeassistant is one).
-
Hi,
That's what I did.See post above. The challenge was to acheive data persistence between reboot, upgrade, etc... Hass OS is pretty tight when it comes to he host file system.
Thanks
-
@vezinpi Have you ran the container and the portainer addon in privileged mode? I have had not trouble in data persistance...
-
- How do I add a TZ-variable? And how do I know how my region (Sweden/Europe) is added?
- My reactions seems to work, but I can't reach the Web UI. The adress in reactor.yaml doesn't work. I also tried the http://127.0.0.1:8111. Can someone point me in the right direction - what adress can it be to reach the Web UI?
Thanks!
-
I don't want to give you bad info, but I believe when you edit a container in Portainer, it actually deletes and publishes the edited one in place.
Check here.
Here are some screen shot from Portainer on my Synology. These are the locations you need to edit for port and TZ.
-
@mikereadington
Thanks!Now it's working!!
-
- SOLVED*
Solved by using Watchtower. Followed this guide:
*OLD POST:
I've been able to update/pull the latest release of MSR a few times within Portainer (running in HA on a HA blue - odroid), but that's not possible anymore.
I only get this message:
I have stopped the MSR as I did before, but nothing seems to help anymore. I have reactor version 21228-05d7497 running, and can't upgrade.
My Portainer version is 2.6.2. Home Assistant is 2021.8.8.
Anyone else having this problem or knows why I can't pull and deploy the latest release?
/Fanan - SOLVED*
-
Your initial problem may have been due to a build error on my part; the build was redone during the course of yesterday and repushed, so that may have had more to do with your success than using WatchTower. You might want to try it the "old" way and see what happens.
-
@Fanan If you are using the HASS.OS then this is a portainer issue in HAAS. See the following link:
Portainer v2.6.2 - unable to start containers
Not sure what the problem could be, but even since the portainer update to v2.6.2 ( integration v2.0.0 ) I’m unable to (re)start any of my previous working containers… The failure I get is : Starting container with non-empty request body was deprecated since API v1.22 and removed in v1.24 Anyone...
Until the problem is resolved in HAAS you will have to install the previous version of the Add-on.
-
@vezinpi Thanks!
I installed alexbelgium repository and his version of Portainer. It was able to update MSR to the latest version (it took a few times with error messages, but then it worked). His version is also 2.6.3. - not 2.6.2. which is the latest available regarding the Portainer add-on i HA. -
Thanks. I will keep that up my sleeve in case HASS fail to address the issue in a timely manner. But for now, the Portainer plugin version 1.5.2 is doing the trick.
-
Locked by toggledbits
Duplicate or Edit a Container - Documentation
How to Update Docker Containers with Watchtower with Portainer
