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

apocalypsehobby

@apocalypsehobby
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
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
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
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
About
Posts
24
Topics
4
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • MSR's "rgb_color.set" isn't correctly sending RGB values to bulb in Home Assistant
    A apocalypsehobby

    Good call

    From MSR's reactor.log file:

    [stable-23242]2024-03-10T21:17:49.485Z <HassController:INFO> HassController#hass action rgb_color.set([Object]{ "value": "75,0,255" }) on Light#hass>light_garage_light_l succeeded
    

    I need to grab logs from HA as well

    Also - I noticed that when I save the rule in MSR, it doesn't save everything. Instead of saving as '75, 0, 255' it just saves as '75'.
    f16d6c16-f48e-4ee2-9c58-cde903f9732a-image.png

    Multi-System Reactor

  • MSR's "rgb_color.set" isn't correctly sending RGB values to bulb in Home Assistant
    A apocalypsehobby

    Hey crew, I'm trying to use MSR to control the RGB values of a Z-Wave bulb in Home Assistant.

    Problem I'm running into - I would like to use 'rgb_color.set' to control this, but it doesn't work, instead it always passes the values '255,255,255' to HA no matter what values I enter within MSR.

    More notes and examples below - I'm wondering if this is a formatting issue that I'm missing? Thanks for any help!

    NOTES FROM TROUBLESHOOTING:

    • 'rgb_color.set_rgb' works successfully, which seems strange. You'd think they would both be affected
    • I've tried a couple different formats, like adding quotes, adding/removing spaces between the RGB values, nothing has fixed it.

    EXAMPLES:
    When I use 'rgb_color.set_rgb', the values successfully carry over to Home Assistant:
    f0f4befc-a642-428e-8923-e5f856ca7e2b-image.png 0af0a4f8-50b9-4100-b1e8-52a0de4cbcbb-image.png

    But when I use 'rgb_color.set', the values DO NOT successfully carry over to Home Assistant:

    9e2d7004-8085-4b70-bb3e-45614b7260a0-image.png 0d630228-c74b-4db8-89bd-2572a08608a3-image.png

    DETAILS:

    • Bulb is LZW42 by Inovelli
    • MSR version: stable-23242-5ee8e1d4

    HA DETAILS

    • Core 2024.2.5
    • Supervisor 2024.02.1
    • Operating System 12.0
    Multi-System Reactor

  • Adding remotes, scene controllers as entities to MSR
    A apocalypsehobby

    @toggledbits Thank you for helping, and that's more than fair.

    I was pressing a button on the remote while viewing the Entity section of MSR, and the virtual device showed no change (the values stayed at "null"). I was expecting them to report on/off and to report the time change.


    For others' reference, it is now working with the following code:

          event_targets: 
            "RGBG-Remote-Button-1": 
              name: "RGBG Remote Button 1"
              capabilities: 
                - button
              events: 
                - event: 
                    event_type: zha_event
                    data: 
                      unique_id: "60:a4:23:ff:fe:65:a3:fb:1:0x0006"
                  response: 
                    button.since: 
                      expr: time()
                    button.state: 
                      from: event.data.command
                      map: 
                        "on": true
                        "off": false
    

    Same goes for buttons 2-5, just tweak the value of "unique_id". Button 1 it ends with "1:0x0006" and button 2 would end with "2:0x0006", etc.

    A caveat to this device is the on/off buttons at the very top send the same signal to HA as the "device 1 on/off" buttons (1:0x0006).

    Here's a link to the device: https://rgbgenie.com/?product=rgbgenie-5-zone-remote-and-dimmer-zigbee

    Multi-System Reactor

  • Adding remotes, scene controllers as entities to MSR
    A apocalypsehobby

    Hey friends - I'm trying this again with another remote, this time the ZB-5001 from RGB Genie.

    It's not working yet, but I feel like I'm close. The device is successfully populating into MSR as an Entity, but when I press a button on the remote it does not report any changes to MSR.

    Could you help me check my work?


    DATA FROM HASSIO_EVENTS.LOG

    • "endpoint_id" tells which button has been pressed (1-5)
    • "cluster_id" seems to always stay at 6
    • "command" shows whether you've pressed the "on" or "off" side of buttons 1-5
    zha_event {
    	"id": 1676585189844,
    	"type": "event",
    	"event": {
    		"event_type": "zha_event",
    		"data": {
    			"device_ieee": "60:a4:23:ff:fe:65:a3:fb",
    			"unique_id": "60:a4:23:ff:fe:65:a3:fb:2:0x0006",
    			"device_id": "516aaf4459a4f4f319a178de36a28dfd",
    			"endpoint_id": 1,
    			"cluster_id": 6,
    			"command": "on",
    			"args": [],
    			"params": {}
    		},
    		"origin": "LOCAL",
    		"time_fired": "2023-02-16T22:07:24.518489+00:00",
    		"context": {
    			"id": "01GSE495V6J686X0RGXYZ046CG",
    			"parent_id": null,
    			"user_id": null
    		}
    	}
    

    MY BEST ATTEMPT AT THE CODE FOR REACTOR.YAML

          event_targets: 
            "RGBG-Remote-Button-1": 
              name: "RGBG Remote Button 1"
              capabilities: 
                - button
              events: 
                - event: 
                    event_type: zha_event
                    data: 
                      device_id: "516aaf4459a4f4f319a178de36a28dfd"
                      endpoint_id: "1"
                  response: 
                    button.since: 
                      from: event.data.time_fired
                    button.state: 
                      from: event.data.command
                      map: 
                        on: on
                        off: off
    
    Multi-System Reactor

  • Adding remotes, scene controllers as entities to MSR
    A apocalypsehobby

    @toggledbits wow, thank you.

    I've successfully added the Hank devices to the reactor.yaml file, along with a couple other remotes. Here are my notes for anyone else on this endeavor.

    • Hank HKZW-SCN04 has 4 buttons, and from my tests they do not support 2x or 3x clicks/presses.

    • Minoston MR40Z V1.0 has 4 buttons, and supports all of the presses that you mapped.

    • Zooz ZEN34 Ver. 1.0 has 2 buttons and supports all the presses that you mapped PLUS it has 4x and 5x presses as well.

    Multi-System Reactor

  • Adding remotes, scene controllers as entities to MSR
    A apocalypsehobby

    @christian_fabre said in Adding remotes, scene controllers as entities to MSR:

    Thanks ...
    I followed this post and managed to successfully use my HANK SCN04 remote with Reactor and Home Assistant.

    @christian_fabre Do you mind sharing the code you used? I have two of the HANK SCN04 as well, and am trying to do the same thing

    Multi-System Reactor

  • MSR actions aren't running anymore-- can't find what's broken
    A apocalypsehobby

    Of course, that fixed it. Thank you both!

    Multi-System Reactor

  • MSR actions aren't running anymore-- can't find what's broken
    A apocalypsehobby

    @sweetgenius yeah I should— I can probably do that tomorrow.

    Multi-System Reactor

  • MSR actions aren't running anymore-- can't find what's broken
    A apocalypsehobby

    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"

    Multi-System Reactor

  • Who are my Home Assistant + ZWave-JS users?
    A apocalypsehobby

    @vezinpi said in Who are my Home Assistant + ZWave-JS users?:

    I don't, but I could if that's the way you want to communicate.

    Same

    Multi-System Reactor zwavejs

  • [SOLVED] Trying to nest logic within Expression
    A apocalypsehobby

    @toggledbits & @tunnus thank you both, your suggestions both worked beautifully. I especially like the spacing & newlines... much clearer

    Pat, I will say on a side note, I thought the transition from Vera/Reactor to HA/MSR would take FOREVER but it's been moving along pretty quickly so far, partially due to the Import tool. Thanks for making that. I still have a long way to go, but I'm making good progress.

    Multi-System Reactor expressions solved

  • [SOLVED] Trying to nest logic within Expression
    A apocalypsehobby

    I'm working on moving from Reactor to MSR, but I'm having a hard time converting this expression.

    (For context, this expression is a part of my thermostat automation, and is designed to convert the outdoor temperature into a standard value from 1-6, which in turn tells the thermostat if we should be heating or cooling and to what degree)

    Within Vera, this is my expression that's working perfectly:

    if(TodayAvg<=33, 1, if(TodayAvg>33 and TodayAvg<=55, 2, if(TodayAvg>55 and TodayAvg<=65, 3, if(TodayAvg>65 and TodayAvg<=74, 4, if(TodayAvg>74 and TodayAvg<=80, 5, if(TodayAvg>80, 6, null))))))
    

    I've successfully converted the first piece of that expression within MSR, with both of these configurations running successfully:

    if TodayAvg <= 33 then 1 endif
    
    TodayAvg <= 33 ? 1 : null
    

    But as soon as I try to nest the logic, it breaks. (This code is not successful)

    if TodayAvg <= 33 then 1 else if TodayAvg > 33 and TodayAvg <= 55 then 2 endif
    

    Would love some advice on how to successfully convert this into a format that MSR accepts.

    Thanks all!

    Multi-System Reactor expressions solved

  • Who are my Home Assistant + ZWave-JS users?
    A apocalypsehobby

    Sign me up 👍

    Multi-System Reactor zwavejs

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    I just let it run with the 14.17

    Multi-System Reactor

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits Oh jeez, I followed the wrong set of instructions from the get-go. When you asked about the install script, I retraced my steps and realized what happened.

    I followed the "Linux (various) Bare Metal" instructions because I did not read that the 4B instructions also worked for the 3B+.

    So I just started fresh and followed the correct instructions, and everything seems to be working. Thank you for your help!

    Multi-System Reactor

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits Sorry, I should have been more specific, it’s running Raspberry Pi OS Lite. Are you saying it should be the regular Raspberry Pi OS?

    Multi-System Reactor

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits
    Vera Firmware: 1.7.5186 (7.31)
    Pi: Raspberry Pi 3 Model B Plus Rev 1.3, and the Debian version is 10.10

    The response was immediate from the web browser, and from when I used wget within the Pi.

    Multi-System Reactor

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits A ton 😕

    pi@MSR-raspberrypi:~/reactor $ node app.js
    basedir /home/pi/reactor
    confdir /home/pi/reactor/config
    datadir /home/pi/reactor/storage
    logsdir /home/pi/reactor/logs
    plugindir /home/pi/reactor/ext
    module.paths [
      '/home/pi/reactor/node_modules',
      '/home/pi/node_modules',
      '/home/node_modules',
      '/node_modules'
    ]
    NODE_PATH undefined
    2021-09-25T18:29:17.047Z <app:null> Reactor "1.0.1-21243-83a87ba" starting on v14.17.6
    2021-09-25T18:29:17.051Z <app:INFO> Process ID 3194; platform linux/arm #1449 SMP Wed Aug 25 15:00:01 BST 2021; locale [ "en-GB", "UTF-8" ]
    2021-09-25T18:29:17.053Z <app:INFO> Basedir /home/pi/reactor; data in /home/pi/reactor/storage
    2021-09-25T18:29:17.054Z <app:INFO> NODE_PATH (undefined); module paths [ "/home/pi/reactor/node_modules", "/home/pi/node_modules", "/home/node_modules", "/node_modules" ]
    2021-09-25T18:29:17.245Z <Plugin:null> Module Plugin v21173
    2021-09-25T18:29:17.270Z <default:INFO> Module Entity v21177
    2021-09-25T18:29:17.280Z <Controller:null> Module Controller v21226
    2021-09-25T18:29:17.281Z <default:null> Module Structure v21229
    2021-09-25T18:29:17.303Z <default:null> Module Ruleset v21096
    2021-09-25T18:29:17.304Z <default:null> Module Rulesets v21096
    2021-09-25T18:29:17.373Z <default:null> Module Rule v21224
    2021-09-25T18:29:17.388Z <default:null> Module Engine v21213
    2021-09-25T18:29:17.390Z <default:null> Module httpapi v21238
    2021-09-25T18:29:17.396Z <default:null> Module httpproxy v21054
    2021-09-25T18:29:17.443Z <default:null> Module wsapi v21196
    2021-09-25T18:29:17.447Z <app:NOTICE> Starting Structure...
    2021-09-25T18:29:17.455Z <default:NOTICE> Structure#1 plugin ID influx disabled; skipping
    2021-09-25T18:29:17.459Z <default:INFO> Structure#1 starting controller interface vera (VeraController)
    2021-09-25T18:29:17.470Z <default:INFO> Structure#1 starting controller interface hass (HassController)
    2021-09-25T18:29:17.473Z <default:INFO> Structure#1 starting controller interface reactor_system (SystemController)
    2021-09-25T18:29:17.614Z <default:null> Module VeraController v21236
    2021-09-25T18:29:17.625Z <default:null> Module HassController v21243
    2021-09-25T18:29:17.630Z <default:null> Module SystemController v21102
    2021-09-25T18:29:17.641Z <VeraController:NOTICE> VeraController#vera starting
    2021-09-25T18:29:17.809Z <VeraController:INFO> VeraController#vera loaded mapping ver 21236 rev 1 format 1 notice
    2021-09-25T18:29:17.812Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state
    2021-09-25T18:29:17.926Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
    2021-09-25T18:29:17.997Z <HassController:NOTICE> HassController#hass attempting reconnection to ws://10.0.0.108:8123/api/websocket
    2021-09-25T18:29:18.002Z <HassController:NOTICE> HassController#hass connecting via WS to ws://10.0.0.108:8123/api/websocket
    2021-09-25T18:29:18.018Z <default:NOTICE> Controller SystemController#reactor_system is now online.
    2021-09-25T18:29:18.192Z <app:INFO> Structure running; pausing for controllers' initial ready
    2021-09-25T18:29:18.261Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594557823 failed, reason: socket hang up
    2021-09-25T18:29:18.285Z <HassController:NOTICE> HassController#hass connected, starting protocol
    2021-09-25T18:29:18.304Z <HassController:INFO> HassController#hass successful authentication with ws://10.0.0.108:8123; fetching initial data...
    2021-09-25T18:29:18.317Z <HassController:INFO> HassController#hass Hass reports version "2021.8.6" location Home timezone America/Detroit state RUNNING safe_mode false
    2021-09-25T18:29:18.553Z <HassController:NOTICE> Controller HassController#hass is now online.
    2021-09-25T18:29:23.290Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594563265 failed, reason: socket hang up
    2021-09-25T18:29:28.312Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594568291 failed, reason: socket hang up
    2021-09-25T18:29:33.339Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594573317 failed, reason: socket hang up
    2021-09-25T18:29:39.363Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594579344 failed, reason: socket hang up
    2021-09-25T18:29:46.392Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594586368 failed, reason: socket hang up
    2021-09-25T18:29:54.420Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594594399 failed, reason: socket hang up
    2021-09-25T18:30:03.448Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594603429 failed, reason: socket hang up
    2021-09-25T18:30:13.468Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594613450 failed, reason: socket hang up
    2021-09-25T18:30:18.265Z <app:NOTICE> Starting Reaction Engine...
    2021-09-25T18:30:18.269Z <Engine:INFO> Reaction Engine starting
    2021-09-25T18:30:18.273Z <Engine:INFO> Checking rule sets...
    2021-09-25T18:30:18.285Z <Engine:INFO> Checking rules...
    2021-09-25T18:30:18.287Z <Engine:INFO> Data check complete; no corrections.
    2021-09-25T18:30:18.296Z <Engine:NOTICE> Reaction Engine running!
    2021-09-25T18:30:18.297Z <app:NOTICE> Starting HTTP server and API...
    2021-09-25T18:30:18.314Z <app:NOTICE> Startup complete
    2021-09-25T18:30:18.323Z <app:NOTICE> HTTP API v1 21238 base URL http://10.0.0.5:8111; listening
    2021-09-25T18:30:18.362Z <app:NOTICE> HTTP server running; registering proxy endpoints.
    2021-09-25T18:30:18.365Z <app:NOTICE> Starting WSAPI...
    2021-09-25T18:30:18.368Z <app:NOTICE> wsapi: starting version 21196
    2021-09-25T18:30:18.405Z <Engine:INFO> Engine#1 master timer tick, local time "25/09/2021, 14:30:18" (TZ offset -240 mins from UTC)
    2021-09-25T18:30:18.687Z <app:INFO> wsapi: connection from ::ffff:10.0.0.91
    2021-09-25T18:30:24.490Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594624469 failed, reason: socket hang up
    2021-09-25T18:30:36.518Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594636500 failed, reason: socket hang up
    2021-09-25T18:30:49.536Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594649518 failed, reason: socket hang up
    2021-09-25T18:31:03.567Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594663549 failed, reason: socket hang up
    2021-09-25T18:31:18.580Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594678567 failed, reason: socket hang up
    2021-09-25T18:31:34.607Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594694590 failed, reason: socket hang up
    
    Multi-System Reactor

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    Thank you both. @Buxton I followed these directions and commented out "auth" in both files, restarted Vera, still got the same error messages.

    What's strange is-- I took one of the request URLs (like http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187568275) and pasted it into my laptop's web browser, and I got a huge output file. So it seems like Vera is working.

    Maybe it's a network configuration problem like you suggested, @toggledbits ? So I went to my Raspberry Pi that's running MSR, and I used wget then it successfully downloaded the output file to the pi as well. So I'm not sure why it's not working within MSR!

    Multi-System Reactor

  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits Do you mind helping me understand why the "socket hang up" & "ECONNREFUSED" messages mean that Vera is reloading a lot?

    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