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. Custom capabilities in MQTT templates
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
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
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
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor
Custom capabilities in MQTT templates
M
Hi, I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far. But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter. So this is what I have in the local_mqtt_devices.yaml capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int And this is the template: templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json So the speak action should send something like this to topic sonos/cmd/speak { "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" } At startup the MSR seems to be quite unhappy with my configuration: reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction. Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable. br, mgvra MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Multi-System Reactor

Custom capabilities in MQTT templates

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 3 Posters 628 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.
  • M Offline
    M Offline
    mgvra
    wrote on last edited by mgvra
    #1

    Hi,
    I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
    But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.

    So this is what I have in the local_mqtt_devices.yaml

    capabilities:
      x_sonos_announcement:
        attributes:
        actions:
          speak:
            arguments:
              text:
                type: string
              volume:
                type: int
              delay:
                type: int
    

    And this is the template:

    templates:
      sonos-announcement: 
        capabilities: 
          - x_sonos_announcement
        actions:
          x_sonos_announcement:
            speak:
              topic: "sonos/cmd/speak"
              payload:
                expr: >
                  { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" }
                type: json
    

    So the speak action should send something like this to topic sonos/cmd/speak

    {
      "text": "message goes here",
      "volume": 50,
      "delayMs": 100,
      "onlyWhenPlaying": false,
      "engine": "neural"
    }
    

    At startup the MSR seems to be quite unhappy with my configuration:

    reactor  | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ]
    reactor  | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1}
    reactor  | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions
    reactor  | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1}
    reactor  |     at _T (/opt/reactor/server/lib/i18n.js:611:28)
    reactor  |     at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25)
    reactor  |     at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30)
    reactor  |     at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26)
    reactor  |     at async Promise.allSettled (index 0)
    
    Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions
    Controller: MQTTController#mqtt
    Last 10:21:37 AM
    
    Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement
    Controller: MQTTController#mqtt
    Last 10:21:37 AM
    

    This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
    Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.

    br,
    mgvra

    MSR latest-25016-d47fea38 / MQTTController [0.2.24293]

    1 Reply Last reply
    1
    • therealdbT Online
      therealdbT Online
      therealdb
      wrote on last edited by
      #2

      As you can see from

      reactor-mqtt-contrib/shelly_gen1.yaml at a05d77b468d0a09fab72d2a23bee683ba2e47c82 · dbochicchio/reactor-mqtt-contrib

      reactor-mqtt-contrib/shelly_gen1.yaml at a05d77b468d0a09fab72d2a23bee683ba2e47c82 · dbochicchio/reactor-mqtt-contrib

      Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

      this should be:

        capabilities:
          x_sonos_announcement:
            actions:
      

      and the way you nest and indent is very important.

      --
      On a mission to automate everything.

      My MS Reactor contrib
      My Luup Plug-ins

      M 1 Reply Last reply
      0
      • therealdbT therealdb

        As you can see from

        reactor-mqtt-contrib/shelly_gen1.yaml at a05d77b468d0a09fab72d2a23bee683ba2e47c82 · dbochicchio/reactor-mqtt-contrib

        reactor-mqtt-contrib/shelly_gen1.yaml at a05d77b468d0a09fab72d2a23bee683ba2e47c82 · dbochicchio/reactor-mqtt-contrib

        Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

        this should be:

          capabilities:
            x_sonos_announcement:
              actions:
        

        and the way you nest and indent is very important.

        M Offline
        M Offline
        mgvra
        wrote on last edited by
        #3

        @therealdb

        Well thanks for your reply, but didn't get it working.
        This is my config now:

        capabilities:
          x_sonos_announcement:
            actions:
              speak:         
                arguments:
                  text:
                    type: string
                  volume:
                    type: int
                  delay:
                    type: int
        templates:
        
          sonos-announcement: 
            capabilities:
             - x_sonos_announcement
            actions:
              x_sonos_announcement:
                speak:          
                  topic: "sonos/cmd/speak"
                  payload:
                    expr: >
                      { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" }
                    type: json
        

        I just fail to see what is the problem here.

        br,
        mgvra

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

          Start by moving your capability definition into local_mqtt_capabilities.yaml and seeing how far that gets you.

          Also, you'll get complaints because your capability name doesn't start with x_mqtt, which you can either ignore, or switch to something like x_mqtt_sonos_....

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

          M 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Start by moving your capability definition into local_mqtt_capabilities.yaml and seeing how far that gets you.

            Also, you'll get complaints because your capability name doesn't start with x_mqtt, which you can either ignore, or switch to something like x_mqtt_sonos_....

            M Offline
            M Offline
            mgvra
            wrote on last edited by
            #5

            @toggledbits

            Thank you for your reply! Well this is what I mean, the answer is right in your face (local_mqtt_capabilities.yaml) and you just can't see it.
            Now it works like charm and I can even refactor my existing KNX templates using the custom capabilities.

            For anyone else who might be struggling with the same problem, here's my config:

            local_mqtt_capabilities.yaml

            capabilities:
              x_mqtt_sonos_announcement:
                actions:
                  speak:         
                    arguments:
                      text:
                        type: string
                      volume:
                        type: int
                        default: 50
                      delay:
                        type: int
                        default: 500
            

            local_mqtt_devices.yaml

            templates:
              sonos-announcement: 
                capabilities:
                 - x_mqtt_sonos_announcement
                actions:
                  x_mqtt_sonos_announcement:
                    speak:          
                      topic: "sonos/cmd/speak"
                      payload:
                        expr: >
                          { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" }
                        type: json
            
            

            UI looks like this:
            d88d6c9d-8a4f-4b0f-a4ac-3903d9c41348-image.png

            FYI there's a subtle layout issue with the login screen background image when using ultra wide monitors, just to let you know.

            beffa9e7-a4de-4969-85e1-4c6ef8d2f6b0-image.png

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

              Showing off all your cool toys, eh?

              Thanks for letting me know. I'll see what I can do to make it look more presentable.

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

              M 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Showing off all your cool toys, eh?

                Thanks for letting me know. I'll see what I can do to make it look more presentable.

                M Offline
                M Offline
                mgvra
                wrote on last edited by
                #7

                @toggledbits

                @toggledbits said in Custom capabilities in MQTT templates:

                Showing off all your cool toys, eh?

                Well I wouldn't boast with employer provided montitor, and definitely wouldn't call it cool, just damn wide. 🙂

                But speaking of showing off cool toys, this is something I bet you've never seen before, one of my weird projects:
                A custom made flow through heater for my summer cottage's outdoor shower. Based on old used Webasto ThermoTop EVO 5kW car engine diesel
                heater and controlled by ESP32 which provides WiFi AP and web UI. Fully modular, so that the heating unit can be removed before the winter.
                Wouldn't call this cool either (no pun intented) but unique. Works pretty well, at least @tunnus agrees.

                Old WIP photo

                ec26e87f-a937-47b5-a30c-0bbeafc63695-image.png

                Thanks for letting me know. I'll see what I can do to make it look more presentable.

                np

                br,
                mgvra

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

                  That is cool. I really love stuff that combines simple, available IoT bits with the old greasy bits to solve problems. It appeals to my libertarian steampunk fantasy of how I'd run my home, which unfortunately far exceeds my wife's tolerance for the lower limits of luxury over sustainability. 😆

                  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
                  1
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  Recent Topics

                  • Can´t restart or upgrade/deploy MSR
                    toggledbitsT
                    toggledbits
                    0
                    4
                    45

                  • Z-Wave Future....
                    toggledbitsT
                    toggledbits
                    0
                    4
                    82

                  • [Solved] Limit HA Entity in MSR
                    wmarcolinW
                    wmarcolin
                    0
                    7
                    153

                  • Reactor (Multi-System/Multi-Hub) Announcements
                    toggledbitsT
                    toggledbits
                    5
                    121
                    35.3k

                  • Disaster recovery and virtualisation
                    CatmanV2C
                    CatmanV2
                    0
                    5
                    636

                  • Remote access of Zwave stick from Z-wave server
                    CatmanV2C
                    CatmanV2
                    0
                    3
                    361

                  • Organizing/ structuring rule sets and rules
                    G
                    gwp1
                    0
                    5
                    365

                  • Moving MSR from a QNAP container to RP 5 - some issues
                    G
                    gwp1
                    0
                    5
                    328

                  • Widget deletion does not work and landing page (status) is empy
                    G
                    gwp1
                    0
                    4
                    320

                  • Need help reducing false positive notifications
                    T
                    tamorgen
                    0
                    7
                    495

                  • Deleting widgets
                    toggledbitsT
                    toggledbits
                    0
                    4
                    458
                  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