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. OW-SERVER: 1-Wire to Ethernet Server - MSR Functionality
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
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
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
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor

OW-SERVER: 1-Wire to Ethernet Server - MSR Functionality

Scheduled Pinned Locked Moved Multi-System Reactor
33 Posts 5 Posters 7.5k Views 4 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.
  • T Talisker

    @a-lurker said in OW-SERVER: 1-Wire to Ethernet Server - MSR Functionality:

    Pretty sure you can get it to work. Use the most recent version of the plugin here. The plugin in the MIOS App Store is well out of date.

    Noted. I rolled back to my vera backup prior to my attempts yesterday. I then downloaded the files from the github link and loaded into my vera.
    I had to set up the OW Server device manually (troubles with ALTUI - see below).

    Your screen capture can be interpreted as the following - how many devices to you have attached?

    Devices: 14
    Chn 1 error count: 0
    Chn 2 error count: 0
    Chn 3 error count: 0
    EDS OW server web page
    

    I get the following now:

    d35915de-0bbe-48bb-ad93-3d22d213ccbc-image.png

    You can see that it does not show the three channels now, but it confirms that I have fourteen devices (which is correct).

    You need to do a few luup engine restarts to get the child devices to show up.

    I have done numerous Luup engine restarts, but the devices still do not show up in 'Add Devices'.

    You can use AltUi to install the plugin from the Alt App Store: see More->AppStore. Not using AltUI? It's highly recommended.

    I did install ALTUI, but I was not able to install OW-Server using it. The first time I pressed the install button it thought about it for a few seconds but did not install the OW Server device. Now when I press it I get an error:

    ffab187b-27f0-479b-aa2b-d3f21c0919cd-image.png

    If I remember correctly, all the one wire devices are created automatically on first run of the plugin. So on my dashboard it says "No new devices to add" as they have already been added.

    The have not been created, possibly because there is an error.....

    "J_OWServer.js file as @dbemowsk suggested" - this bug has already been resolved in the plugin at the link above, so please use the J_OWServer.js file that comes with the Alt App store plugin.

    Many of the plugins in the MIOS App Store are hopelessly out of date - refer to the Alt App store list. for updated versions.

    All else fails; check the log - once again this can be seen using AltUi -> Misc -> OS Command --> Tail Logs

    I get the following error in the Alturi app (similar in the vera UI) and Vera log:

    f68f5954-bc1b-4e8f-98e7-198946248735-image.png

    4b45b478-b6a8-43aa-8ef9-b2a1875cda7b-image.png

    You can see from the vera log (http://192.168.68.103/cgi-bin/cmh/log.sh?Device=LuaUPnP) the requisite jasn.lua library file cannot be found. Now I am hoping this is all I need (deposited in the right place in vera) to get the OW Server device up an running. So, where do I get this file and where do I put it (please be polite!!).![768cd707-8727-4ce9-a06e-717661411e31-image.png]

    A Offline
    A Offline
    a-lurker
    wrote on last edited by
    #20

    Looking at the log it says its missing json.lua. This message tells me you are still running the old plugin from the MIOS store.

    Not sure what hardware you are using? The old Vera 3 can't access the Alt App store as the comms library is too antiquated. Regardless you can just download the files from GitHub and overwrite the mios ones. Use the Vera user interface (ie not directly with SSH) as Vera compresses the files when you upload them via the UI. In Vera 3 they end up in etc\cmh-ludl as "lzo" files

    The latest version of the plugin looks for ten different possibly available json libraries - see this GitHub link.

    If you look in (a Vera 3) /usr/lib/lua you may find dkjson.lua, which in this case is a sym link to /mios/usr/lib/lua/dkjson.lua

    You can use the command in AltUI --> Misc --> OsCommand -->Find Json to see what might be available to you. Note that this search doesn't always find what's available. But I would expect dkjson.lua is available and will be found and used by the latest version of the plugin.

    T 1 Reply Last reply
    0
    • A a-lurker

      Looking at the log it says its missing json.lua. This message tells me you are still running the old plugin from the MIOS store.

      Not sure what hardware you are using? The old Vera 3 can't access the Alt App store as the comms library is too antiquated. Regardless you can just download the files from GitHub and overwrite the mios ones. Use the Vera user interface (ie not directly with SSH) as Vera compresses the files when you upload them via the UI. In Vera 3 they end up in etc\cmh-ludl as "lzo" files

      The latest version of the plugin looks for ten different possibly available json libraries - see this GitHub link.

      If you look in (a Vera 3) /usr/lib/lua you may find dkjson.lua, which in this case is a sym link to /mios/usr/lib/lua/dkjson.lua

      You can use the command in AltUI --> Misc --> OsCommand -->Find Json to see what might be available to you. Note that this search doesn't always find what's available. But I would expect dkjson.lua is available and will be found and used by the latest version of the plugin.

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

      @a-lurker Next instalment (sorry!). I re-downloaded the files from Github following the link you kindly provided in your previous post. There were three files plus a number of other files in a separate folder. I copied all the files from the .zip file into a folder on my desktop and uploaded them to my vera plus and tried a number of luup reloads. Was that correct - i.e. should I have uploaded all files (including the ones in the folder) as separate files and not in the actual folder?

      Anyhow, something happened because now I get the following (note I have 14 devices:
      9f77c477-648d-47f9-a045-6b224fd43398-image.png

      and in 'Add Devices'

      7a749d3a-607e-4f12-a10b-490b2cbb7ed9-image.png

      So I did not see the previous result before. But you can see that my devices are not being found. I have looked in the luup logs and there are no errors I can see. I also cannot see the device number listed in the log. I don't know if that means that anything.

      Thanks.

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

      A 1 Reply Last reply
      0
      • T Talisker

        @a-lurker Next instalment (sorry!). I re-downloaded the files from Github following the link you kindly provided in your previous post. There were three files plus a number of other files in a separate folder. I copied all the files from the .zip file into a folder on my desktop and uploaded them to my vera plus and tried a number of luup reloads. Was that correct - i.e. should I have uploaded all files (including the ones in the folder) as separate files and not in the actual folder?

        Anyhow, something happened because now I get the following (note I have 14 devices:
        9f77c477-648d-47f9-a045-6b224fd43398-image.png

        and in 'Add Devices'

        7a749d3a-607e-4f12-a10b-490b2cbb7ed9-image.png

        So I did not see the previous result before. But you can see that my devices are not being found. I have looked in the luup logs and there are no errors I can see. I also cannot see the device number listed in the log. I don't know if that means that anything.

        Thanks.

        A Offline
        A Offline
        a-lurker
        wrote on last edited by
        #22

        Not quite right. You only need the files in the folder called "Luup_device". When uploaded they should not be uploaded as a folder. Here is the list of files that need to be directly uploaded:

        S_OWServer.xml
        D_OWPressureSensor.json
        D_OWPressureSensor.xml
        D_OWServer.json
        D_OWServer.xml
        I_OWServer.xml
        J_OWServer.js
        L_OWServer.lua
        S_OWPressureSensor.xml
        

        Did you check for a json library using AltUI? Because you will need one of some description.

        T 1 Reply Last reply
        0
        • A a-lurker

          Not quite right. You only need the files in the folder called "Luup_device". When uploaded they should not be uploaded as a folder. Here is the list of files that need to be directly uploaded:

          S_OWServer.xml
          D_OWPressureSensor.json
          D_OWPressureSensor.xml
          D_OWServer.json
          D_OWServer.xml
          I_OWServer.xml
          J_OWServer.js
          L_OWServer.lua
          S_OWPressureSensor.xml
          

          Did you check for a json library using AltUI? Because you will need one of some description.

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

          @a-lurker I meticulously installed all the files in the folder only as you stated. I trawled the luup log and found the following. It appears that the plugin does see my 14 one wire temperature devices, but for some reason will not let me set them up as devices:

          cfb6105f-fafe-41bf-be7c-a4760ba7e2a4-image.png

          9c16f8a8-a5dd-4108-bc38-9119a16b52f1-image.png

          4e221ba6-bef4-47ba-ba24-d97b56667db0-image.png

          Could this be a fundamental problem with my particular vera plus, because I have to install the device manually. It will not install via ALTUI?

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

          1 Reply Last reply
          0
          • A Offline
            A Offline
            a-lurker
            wrote on last edited by
            #24

            Looks promising - hopefully you should see under the AltUI variables tab "DebugEnabled". You can set it to one and restart the Luup engine and get more log info. You should also see "PluginVersion", which should probably be 0.52? No mention on whether AltUI detected a json library?

            "Could this be a fundamental problem with my particular vera plus, because I have to install the device manually. It will not install via ALTUI?" No don't think so.

            T 1 Reply Last reply
            0
            • A a-lurker

              Looks promising - hopefully you should see under the AltUI variables tab "DebugEnabled". You can set it to one and restart the Luup engine and get more log info. You should also see "PluginVersion", which should probably be 0.52? No mention on whether AltUI detected a json library?

              "Could this be a fundamental problem with my particular vera plus, because I have to install the device manually. It will not install via ALTUI?" No don't think so.

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

              @a-lurker Sorry, yes the AltUI did detect a json library (or at least I think so):

              e69ce95d-a4f6-4c8f-ac39-ecab38fc6e1a-image.png

              Yes, it looks like the PluginVersion os 0.52:

              d7b32323-2c3e-47d7-a7c9-8737904a40ca-image.png

              One Log:

              50 01/22/22 13:06:03.101 luup_log:1028: OWServer debug: OWserver poll start: device: 1028 <0x7155a520>
              50 01/22/22 13:06:03.399 luup_log:1028: OWServer debug: 14 --> Devices <0x7155a520>
              50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel1 <0x7155a520>
              50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel2 <0x7155a520>
              50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel3 <0x7155a520>
              50 01/22/22 13:06:03.400 luup_log:1028: OWServer debug: New device found F0000801B4209010 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.401 luup_log:1028: OWServer debug: New device found A7000801B4562810 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.401 luup_log:1028: OWServer debug: New device found 88000801B4467410 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.401 luup_log:1028: OWServer debug: New device found 2E000801B423AC10 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 03000801B43A3210 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 84000801B4368A10 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 2E000801B44B7910 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found C8000801B45C5510 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.402 luup_log:1028: OWServer debug: New device found 12000801B43A2F10 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found 33000801B442DF10 DS18S20 <0x7155a520>
              50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found B50000021D3DE028 DS18B20 <0x7155a520>
              50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found 3E0000021D47F028 DS18B20 <0x7155a520>
              50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found FB0000021D4C4628 DS18B20 <0x7155a520>
              50 01/22/22 13:06:03.403 luup_log:1028: OWServer debug: New device found 080000021D6EAE28 DS18B20 <0x7155a520>
              50 01/22/22 13:06:03.404 luup_log:1028: OWServer debug: Set timer 3 <0x7155a520>
              50 01/22/22 13:06:03.404 luup_log:1028: OWServer debug: OWserver poll end: device: 1028 <0x7155a520>
              06 01/22/22 13:06:04.100 Device_Variable::m_szValue_set device: 911 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1642856762 now: 1642856764 #hooks: 0 upnp: 0 skip: 0 v:0x154d730/NONE duplicate:0 <0x7695a520>
              06 01/22/22 13:06:04.101 Device_Variable::m_szValue_set device: 911 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 1 upnp: 0 skip: 0 v:0x154d600/NONE duplicate:0 <0x7695a520>
              50 01/22/22 13:06:06.100 luup_log:1028: OWServer debug: OWserver poll start: device: 1028 <0x7155a520>
              01 01/22/22 13:06:06.342 IOPort::Connect connect -1 192.168.68.111:60128 <0x6de60520>
              50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 14 --> Devices <0x7155a520>
              50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel1 <0x7155a520>
              50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel2 <0x7155a520>
              50 01/22/22 13:06:06.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel3 <0x7155a520>
              50 01/22/22 13:06:06.400 luup_log:1028: OWServer debug: Set timer 3 <0x7155a520>
              50 01/22/22 13:06:06.400 luup_log:1028: OWServer debug: OWserver poll end: device: 1028 <0x7155a520>
              50 01/22/22 13:06:09.100 luup_log:1028: OWServer debug: OWserver poll start: device: 1028 <0x7155a520>
              50 01/22/22 13:06:09.398 luup_log:1028: OWServer debug: 14 --> Devices <0x7155a520>
              50 01/22/22 13:06:09.398 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel1 <0x7155a520>
              50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel2 <0x7155a520>
              50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: 0 --> DataErrorsChannel3 <0x7155a520>
              50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: Set timer 3 <0x7155a520>
              50 01/22/22 13:06:09.399 luup_log:1028: OWServer debug: OWserver poll end: device: 1028 <0x7155a520

              Any clues there?

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

              1 Reply Last reply
              0
              • A Offline
                A Offline
                a-lurker
                wrote on last edited by
                #26

                All looks fine to me. It's now got a json library and it's reading from the one wire server and finding all the devices. It's also the correct plugin version number. Have you checked the "No room" for see if the child temperature sensors have turned up. If none - need to do a luup engine restart. It can take a while before actual temperatures are displayed ( I think it works out to 45 seconds). They then update at the default rate of every 20 seconds.

                T 1 Reply Last reply
                0
                • A a-lurker

                  All looks fine to me. It's now got a json library and it's reading from the one wire server and finding all the devices. It's also the correct plugin version number. Have you checked the "No room" for see if the child temperature sensors have turned up. If none - need to do a luup engine restart. It can take a while before actual temperatures are displayed ( I think it works out to 45 seconds). They then update at the default rate of every 20 seconds.

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

                  @a-lurker So I think we proved that I have the correct plugin version, the plugin is correctly set up as the one wire devices IDs are listed in the logs. What is not happening is the devices (14 No. in my case) are not showing up in add devices (similar in ALTUI):
                  c7a0ac1d-07f0-480d-966d-5ca4c9de1505-image.png

                  I have tried multiple luup re-loads and vera restarts, but the devices just aren't showing. I feel I am so close, yet not quite at the finish line! Is there anything else I can do or try? Thanks.

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

                  A 1 Reply Last reply
                  0
                  • T Talisker

                    @a-lurker So I think we proved that I have the correct plugin version, the plugin is correctly set up as the one wire devices IDs are listed in the logs. What is not happening is the devices (14 No. in my case) are not showing up in add devices (similar in ALTUI):
                    c7a0ac1d-07f0-480d-966d-5ca4c9de1505-image.png

                    I have tried multiple luup re-loads and vera restarts, but the devices just aren't showing. I feel I am so close, yet not quite at the finish line! Is there anything else I can do or try? Thanks.

                    A Offline
                    A Offline
                    a-lurker
                    wrote on last edited by a-lurker
                    #28
                    This post is deleted!
                    A 1 Reply Last reply
                    0
                    • A a-lurker

                      This post is deleted!

                      A Offline
                      A Offline
                      a-lurker
                      wrote on last edited by
                      #29
                      This post is deleted!
                      1 Reply Last reply
                      0
                      • A Offline
                        A Offline
                        a-lurker
                        wrote on last edited by
                        #30

                        OK I've figured out what's going wrong (till proved otherwise!). I need to rehash some code, test and post to GitHub - give it a day or so.

                        A 1 Reply Last reply
                        0
                        • A a-lurker

                          OK I've figured out what's going wrong (till proved otherwise!). I need to rehash some code, test and post to GitHub - give it a day or so.

                          A Offline
                          A Offline
                          a-lurker
                          wrote on last edited by a-lurker
                          #31

                          I have done the mods and retested. Hopefully they will work. When the plugin is updated it will show the "PluginVersion" as 0.53 rather than the current 0.52

                          The github page has been updated to improve upon the previous paltry documentation - have a read of it. You only need to upload two files to Vera, as all the others are unchanged:

                          J_OWServer.js
                          L_OWServer.lua

                          Make sure both are uploaded via the Vera UI. Be careful to uncheck the "Restart Luup after upload" checkbox situated below the "Upload" button - so you don't go through two loads. ie uncheck for the first file you upload and then recheck before you upload the second.

                          There were a few changes needed - the plugin was originally written over ten years ago and things have moved on a little since then.

                          Note that there is no "Automatic" creation of the child devices. You select which sensors you want in the Vera UI and then hit the "Add" button. The system then restarts and the child devices will became available.

                          Let me know how it goes.

                          T 2 Replies Last reply
                          0
                          • A a-lurker

                            I have done the mods and retested. Hopefully they will work. When the plugin is updated it will show the "PluginVersion" as 0.53 rather than the current 0.52

                            The github page has been updated to improve upon the previous paltry documentation - have a read of it. You only need to upload two files to Vera, as all the others are unchanged:

                            J_OWServer.js
                            L_OWServer.lua

                            Make sure both are uploaded via the Vera UI. Be careful to uncheck the "Restart Luup after upload" checkbox situated below the "Upload" button - so you don't go through two loads. ie uncheck for the first file you upload and then recheck before you upload the second.

                            There were a few changes needed - the plugin was originally written over ten years ago and things have moved on a little since then.

                            Note that there is no "Automatic" creation of the child devices. You select which sensors you want in the Vera UI and then hit the "Add" button. The system then restarts and the child devices will became available.

                            Let me know how it goes.

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

                            @a-lurker Great! I am away for a couple of days with work. I'll follow your instructions and give it a try when I get home on Friday. Standby.

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

                            1 Reply Last reply
                            0
                            • A a-lurker

                              I have done the mods and retested. Hopefully they will work. When the plugin is updated it will show the "PluginVersion" as 0.53 rather than the current 0.52

                              The github page has been updated to improve upon the previous paltry documentation - have a read of it. You only need to upload two files to Vera, as all the others are unchanged:

                              J_OWServer.js
                              L_OWServer.lua

                              Make sure both are uploaded via the Vera UI. Be careful to uncheck the "Restart Luup after upload" checkbox situated below the "Upload" button - so you don't go through two loads. ie uncheck for the first file you upload and then recheck before you upload the second.

                              There were a few changes needed - the plugin was originally written over ten years ago and things have moved on a little since then.

                              Note that there is no "Automatic" creation of the child devices. You select which sensors you want in the Vera UI and then hit the "Add" button. The system then restarts and the child devices will became available.

                              Let me know how it goes.

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

                              @a-lurker Everything is working as expected now. Thank you once again for all the support and for updating the plugin. Next step...... database and graphing.

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

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


                              Recent Topics

                              • VEC Virtual Switch Auto Off
                                S
                                SweetGenius
                                0
                                1
                                3

                              • Access control - allowing anonymous user to dashboard
                                tunnusT
                                tunnus
                                0
                                1
                                10

                              • Upcoming Storage Change -- Got Back-ups?
                                toggledbitsT
                                toggledbits
                                0
                                1
                                12

                              • Oddness in Copy/Move of Reactions
                                G
                                gwp1
                                0
                                1
                                47

                              • [Solved] function isRuleEnabled() issue
                                CrilleC
                                Crille
                                0
                                4
                                60

                              • [Reactor] Problem with Global Reactions and groups
                                therealdbT
                                therealdb
                                0
                                3
                                84

                              • Possible feature request 2?
                                CatmanV2C
                                CatmanV2
                                0
                                3
                                61

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                133
                                79.8k

                              • Genuinely impressed with Zigbee and HA / Reactor
                                CatmanV2C
                                CatmanV2
                                1
                                9
                                369

                              • Copying a global reaction
                                toggledbitsT
                                toggledbits
                                0
                                3
                                111

                              • [HowTo] Using HABridge with Reactor
                                CatmanV2C
                                CatmanV2
                                0
                                9
                                439

                              • [Reactor] Bug when sending MQTT boolean payloads
                                toggledbitsT
                                toggledbits
                                0
                                4
                                163
                              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