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. Trouble connecting Vera to MSR
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor

Trouble connecting Vera to MSR

Scheduled Pinned Locked Moved Multi-System Reactor
17 Posts 3 Posters 1.9k Views 3 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 Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #2

    That looks like your Vera reloading...a lot. I doubt this is caused by MSR. I would stop MSR or disable the integration by setting enabled to false in the reactor.yaml config for your Vera, and figure out why your Vera isn't happy.

    Troubleshooting steps would be the usual for a Vera that's reloading a lot: check for ZWave devices (particularly battery-operated) that are having trouble communicating, and if all that's fine, start looking at your plugins.

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

    A 2 Replies Last reply
    0
    • toggledbitsT toggledbits

      That looks like your Vera reloading...a lot. I doubt this is caused by MSR. I would stop MSR or disable the integration by setting enabled to false in the reactor.yaml config for your Vera, and figure out why your Vera isn't happy.

      Troubleshooting steps would be the usual for a Vera that's reloading a lot: check for ZWave devices (particularly battery-operated) that are having trouble communicating, and if all that's fine, start looking at your plugins.

      A Offline
      A Offline
      apocalypsehobby
      wrote on last edited by
      #3

      @toggledbits Oh yikes. I will look into this. Thank you!

      1 Reply Last reply
      0
      • toggledbitsT toggledbits

        That looks like your Vera reloading...a lot. I doubt this is caused by MSR. I would stop MSR or disable the integration by setting enabled to false in the reactor.yaml config for your Vera, and figure out why your Vera isn't happy.

        Troubleshooting steps would be the usual for a Vera that's reloading a lot: check for ZWave devices (particularly battery-operated) that are having trouble communicating, and if all that's fine, start looking at your plugins.

        A Offline
        A Offline
        apocalypsehobby
        wrote on last edited by
        #4

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

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

          The ECONNREFUSED means that your Vera is not accepting connections. This happens during reloads, when the box is up and running but LuaUPnP is not ready to answer requests. It could also mean you have the wrong IP address configured, or the IP is not reachable on the network segment you are on, but I'm assuming you know the correct IP of the box and have configured it correctly, and the other message suggests something is reachable at the IP and port given (and the port is very unusual and specific to Vera).

          The "socket hang up" means that the LuaUPnP engine accepted the connection but the connection was terminated before the request could be sent, or terminated with no response data -- the server/Vera closed the connection without saying anything, or didn't say anything within the connection timeout period, although timeouts are usually more definitive and reported as such.

          I'm assuming you're seeing a lot of these, and that's why you posted.

          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
          • A apocalypsehobby

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

            B Offline
            B Offline
            Buxton
            wrote on last edited by
            #6

            @apocalypsehobby You might also have authentication on. Check in the highlit file below to make sure "auth" is commented out --- like you see in the subsequent screenshot. The file is located in the etc folder on the vera:
            verafiles.png

            veraauth.png

            you also need to make the same adjustment in the same name file stored in the lighttpd folder that is under etc/:
            verafolder.png

            1 Reply Last reply
            0
            • A Offline
              A Offline
              apocalypsehobby
              wrote on last edited by
              #7

              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!

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

                Let's go back to a previous question... are you getting a ton of these, or just occasionally?

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

                A 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Let's go back to a previous question... are you getting a ton of these, or just occasionally?

                  A Offline
                  A Offline
                  apocalypsehobby
                  wrote on last edited by
                  #9

                  @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
                  1 Reply Last reply
                  0
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by toggledbits
                    #10

                    What version of Vera firmware are you running? What are the specs of the Pi?

                    pasted it into my laptop's web browser, and I got a huge output file. So it seems like Vera is working.

                    How long did it take to get the response?

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

                    A 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      What version of Vera firmware are you running? What are the specs of the Pi?

                      pasted it into my laptop's web browser, and I got a huge output file. So it seems like Vera is working.

                      How long did it take to get the response?

                      A Offline
                      A Offline
                      apocalypsehobby
                      wrote on last edited by
                      #11

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

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

                        I have it running on both a 1GB 3B+ and a 4GB 4, but under Raspberry Pi OS/Raspian. I'd suggest trying that next.

                        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
                        • A Offline
                          A Offline
                          apocalypsehobby
                          wrote on last edited by
                          #13

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

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

                            OK. The version of nodejs you've got running isn't the one installed by the install script... did you run the install script? It will still let you use that version, that "should not" be a/the problem, but the script does other things... installs dependencies, certain versions... should not be run as root or under su/sudo... did all that happen?

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

                            A 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              OK. The version of nodejs you've got running isn't the one installed by the install script... did you run the install script? It will still let you use that version, that "should not" be a/the problem, but the script does other things... installs dependencies, certain versions... should not be run as root or under su/sudo... did all that happen?

                              A Offline
                              A Offline
                              apocalypsehobby
                              wrote on last edited by
                              #15

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

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

                                Sounds good. Still leaves me wondering what was going on, because the bare metal steps basically take you in the same direction as the installer (and the reverse is also true — you could run the Pi install script on pretty much any Linux box and probably get a valid install). In the background, I also brought up a 3B+ on RaspiOS and did a bare metal install with node 14.17.6 as you had, and it worked fine. So, not sure what may have gone sideways with your original install, but I'm glad the script straightened it out.

                                Did you let the install script install node 14.15, or did you let it go ahead with the 14.17 previously installed? That would narrow down some variables.

                                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
                                • A Offline
                                  A Offline
                                  apocalypsehobby
                                  wrote on last edited by
                                  #17

                                  I just let it run with the 14.17

                                  1 Reply Last reply
                                  1
                                  • toggledbitsT toggledbits locked this topic on
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes

                                  Recent Topics

                                  • How to upgrade from an old version of MSR?
                                    cw-kidC
                                    cw-kid
                                    0
                                    15
                                    209
                                  • Can you run MSR on Home Assistant OS ?
                                    therealdbT
                                    therealdb
                                    0
                                    2
                                    9
                                  • HA and AI
                                    PablaP
                                    Pabla
                                    0
                                    2
                                    98
                                  • Self test
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    3
                                    86
                                  • Access control - allowing anonymous user to dashboard
                                    toggledbitsT
                                    toggledbits
                                    0
                                    2
                                    111
                                  • VEC Virtual Switch Auto Off
                                    S
                                    SweetGenius
                                    1
                                    1
                                    79
                                  • Upcoming Storage Change -- Got Back-ups?
                                    toggledbitsT
                                    toggledbits
                                    3
                                    1
                                    74
                                  • Oddness in Copy/Move of Reactions
                                    G
                                    gwp1
                                    0
                                    1
                                    91
                                  • [Solved] function isRuleEnabled() issue
                                    CrilleC
                                    Crille
                                    0
                                    4
                                    183
                                  • [Reactor] Problem with Global Reactions and groups
                                    therealdbT
                                    therealdb
                                    0
                                    3
                                    174
                                  • Possible feature request 2?
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    3
                                    147
                                  • Reactor (Multi-System/Multi-Hub) Announcements
                                    toggledbitsT
                                    toggledbits
                                    5
                                    133
                                    84.3k
                                  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