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. [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3
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
[SOLVED]Hass websocket falsely reporting ready on boot??
V
Hi, @toggledbits I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting. Here is the sequence of the test case (All time converted to Zulu to match logs): Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error. Here is what I see from the log: 14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready. Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...). Questions: Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas? Here is the log: OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Multi-System Reactor

[ZwaveJS] Position and cover not working for Roller Shutter 1/2/3

Scheduled Pinned Locked Moved Multi-System Reactor
37 Posts 2 Posters 3.1k 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.
  • therealdbT Offline
    therealdbT Offline
    therealdb
    wrote on last edited by
    #1

    As per @toggledbits request, new topic.

    Position and cover commands not working and position/cover attributes are incorrect. Dimming is OK.

    cover.state=null
    dimming.level=1
    dimming.step=0.1
    energy_sensor.units="kWh"
    energy_sensor.value=0.41
    position.value=null
    power_sensor.units="W"
    power_sensor.value=0
    power_switch.state=true
    x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state"}
    x_zwave_values.Meter_reset=null
    x_zwave_values.Meter_value_65537=0.41
    x_zwave_values.Meter_value_66049=0
    x_zwave_values.Multilevel_Switch_Down=null
    x_zwave_values.Multilevel_Switch_Up=null
    x_zwave_values.Multilevel_Switch_currentValue=99
    x_zwave_values.Multilevel_Switch_duration="unknown"
    x_zwave_values.Multilevel_Switch_restorePrevious=null
    x_zwave_values.Multilevel_Switch_targetValue=99
    x_zwave_values.Notification_Power_Management_Over_current_status=0
    x_zwave_values.Notification_System_Hardware_status=0
    x_zwave_values.Notification_alarmLevel=null
    x_zwave_values.Notification_alarmType=null
    zwave_device.capabilities=[38,50,113]
    zwave_device.endpoint=1
    zwave_device.failed=null
    zwave_device.impl_sig="24225:1:22315:1"
    zwave_device.manufacturer_info=null
    zwave_device.node_id=148
    zwave_device.version_info=null
    

    Thanks!

    --
    On a mission to automate everything.

    My MS Reactor contrib
    My Luup Plug-ins

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

      Did you redact here? Seems like there are some missing attributes.

      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
      • therealdbT Offline
        therealdbT Offline
        therealdb
        wrote on last edited by therealdb
        #3

        no, I posted the first endpoint (that's what I got with 3). Here's the main device:

        cover.state=null
        position.value=null
        x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state"}
        x_zwave_values.Central_Scene_scene_001=null
        x_zwave_values.Central_Scene_scene_002=null
        x_zwave_values.Central_Scene_slowRefresh=null
        x_zwave_values.Configuration_Alarm_1_Action_255=0
        x_zwave_values.Configuration_Alarm_1_Event_State_Parameters_65280=0
        x_zwave_values.Configuration_Alarm_1_Notification_Status_16711680=0
        x_zwave_values.Configuration_Alarm_1_Notification_Type_4278190080=0
        x_zwave_values.Configuration_Alarm_2_Action_255=0
        x_zwave_values.Configuration_Alarm_2_Event_State_Parameters_65280=0
        x_zwave_values.Configuration_Alarm_2_Notification_Status_16711680=255
        x_zwave_values.Configuration_Alarm_2_Notification_Type_4278190080=5
        x_zwave_values.Configuration_Alarm_3_Action_255=0
        x_zwave_values.Configuration_Alarm_3_Event_State_Parameters_65280=0
        x_zwave_values.Configuration_Alarm_3_Notification_Status_16711680=255
        x_zwave_values.Configuration_Alarm_3_Notification_Type_4278190080=1
        x_zwave_values.Configuration_Alarm_4_Action_255=0
        x_zwave_values.Configuration_Alarm_4_Event_State_Parameters_65280=0
        x_zwave_values.Configuration_Alarm_4_Notification_Status_16711680=255
        x_zwave_values.Configuration_Alarm_4_Notification_Type_4278190080=2
        x_zwave_values.Configuration_Alarm_5_Action_255=0
        x_zwave_values.Configuration_Alarm_5_Event_State_Parameters_65280=0
        x_zwave_values.Configuration_Alarm_5_Notification_Status_16711680=255
        x_zwave_values.Configuration_Alarm_5_Notification_Type_4278190080=4
        x_zwave_values.Configuration_Delay_Motor_Stop=10
        x_zwave_values.Configuration_Energy_Reports_On_Change=10
        x_zwave_values.Configuration_Energy_Reports_Periodic=3600
        x_zwave_values.Configuration_Force_Calibration=1
        x_zwave_values.Configuration_Inputs_Orientation=0
        x_zwave_values.Configuration_Measuring_Power_Consumed_by_the_Device_Itself=0
        x_zwave_values.Configuration_Motor_Operation_Detection=10
        x_zwave_values.Configuration_Operating_Mode=1
        x_zwave_values.Configuration_Outputs_Orientation=0
        x_zwave_values.Configuration_Power_Reports_On_Change=15
        x_zwave_values.Configuration_Power_Reports_Periodic=3600
        x_zwave_values.Configuration_S1_Scenes_Hold_Down_Release_8=0
        x_zwave_values.Configuration_S1_Scenes_Pressed_1_Time_1=0
        x_zwave_values.Configuration_S1_Scenes_Pressed_2_Times_2=0
        x_zwave_values.Configuration_S1_Scenes_Pressed_3_Time_4=0
        x_zwave_values.Configuration_S2_Scenes_Hold_Down_Release_8=0
        x_zwave_values.Configuration_S2_Scenes_Pressed_1_Time_1=0
        x_zwave_values.Configuration_S2_Scenes_Pressed_2_Times_2=0
        x_zwave_values.Configuration_S2_Scenes_Pressed_3_Time_4=0
        x_zwave_values.Configuration_Set_Slats_Back_to_Previous_Position=1
        x_zwave_values.Configuration_Switch_Type=0
        x_zwave_values.Configuration_Time_of_Down_Movement=1780
        x_zwave_values.Configuration_Time_of_Up_Movement=1813
        x_zwave_values.Configuration_Venetian_Blind_Time_of_Full_Turn_of_the_Slats=150
        x_zwave_values.Manufacturer_Specific_manufacturerId=271
        x_zwave_values.Manufacturer_Specific_productId=4096
        x_zwave_values.Manufacturer_Specific_productType=771
        x_zwave_values.Protection_exclusiveControlNodeId=null
        x_zwave_values.Protection_local=0
        x_zwave_values.Protection_rf=0
        x_zwave_values.Protection_timeout=null
        x_zwave_values.Supervision_ccSupported_91=false
        x_zwave_values.Version_firmwareVersions=["5.1","5.1"]
        x_zwave_values.Version_hardwareVersion=3
        x_zwave_values.Version_libraryType=3
        x_zwave_values.Version_protocolVersion="6.2"
        zwave_device.capabilities=[91,108,112,114,117,134]
        zwave_device.endpoint=0
        zwave_device.failed=false
        zwave_device.generic_class="Multilevel Switch"
        zwave_device.impl_sig="24225:1:22315:1"
        zwave_device.is_beaming=false
        zwave_device.is_listening=true
        zwave_device.is_routing=true
        zwave_device.is_secure=true
        zwave_device.manufacturer_info=[271,771,4096]
        zwave_device.max_data_rate=null
        zwave_device.node_id=148
        zwave_device.specific_class="Motor Control Class B"
        zwave_device.status=4
        zwave_device.status_text="alive"
        zwave_device.version_info=[null,"5.1"]
        

        But, in this case, I have to send command via the first endpoint. Here's a RS 2 (no endpoints):

        cover.state=null
        dimming.level=0.13
        dimming.step=0.1
        energy_sensor.units="kWh"
        energy_sensor.value=2.59
        position.value=null
        power_sensor.units="W"
        power_sensor.value=0
        power_switch.state=false
        x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state"}
        x_zwave_values.Binary_Switch_currentValue=false
        x_zwave_values.Binary_Switch_targetValue=null
        x_zwave_values.Configuration_Delay_Time_After_S2=10
        x_zwave_values.Configuration_Energy_Reports=10
        x_zwave_values.Configuration_Forced_Roller_Shutter_Calibration=0
        x_zwave_values.Configuration_Lamellas_Positioning_Mode=1
        x_zwave_values.Configuration_Managing_Lamellas_in_Response_to_Alarm=1
        x_zwave_values.Configuration_Motor_Operation_Detection=10
        x_zwave_values.Configuration_Motor_Operation_Time=240
        x_zwave_values.Configuration_Periodic_Power_or_Energy_Reports=3600
        x_zwave_values.Configuration_Power_Reports=null
        x_zwave_values.Configuration_Reports_Type=0
        x_zwave_values.Configuration_Response_to_General_Alarm=2
        x_zwave_values.Configuration_Response_to_Smoke_CO_CO2_Alarm=1
        x_zwave_values.Configuration_Response_to_Temperature_Alarm=1
        x_zwave_values.Configuration_Response_to_Water_Flood_Alarm=0
        x_zwave_values.Configuration_Roller_Shutter_Operating_Modes=1
        x_zwave_values.Configuration_Scenes_Associations_Activation=1
        x_zwave_values.Configuration_Self_Measurement=0
        x_zwave_values.Configuration_Switch_Type=0
        x_zwave_values.Configuration_Turning_Time_Delay_Time=150
        x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=0
        x_zwave_values.Manufacturer_Specific_manufacturerId=271
        x_zwave_values.Manufacturer_Specific_productId=4096
        x_zwave_values.Manufacturer_Specific_productType=770
        x_zwave_values.Meter_reset=null
        x_zwave_values.Meter_value_65537=2.59
        x_zwave_values.Meter_value_66049=0
        x_zwave_values.Multilevel_Sensor_Power=0
        x_zwave_values.Multilevel_Switch_Close=null
        x_zwave_values.Multilevel_Switch_Open=null
        x_zwave_values.Multilevel_Switch_currentValue=13
        x_zwave_values.Multilevel_Switch_duration=null
        x_zwave_values.Multilevel_Switch_restorePrevious=null
        x_zwave_values.Multilevel_Switch_targetValue=0
        x_zwave_values.Protection_exclusiveControlNodeId=null
        x_zwave_values.Protection_local=0
        x_zwave_values.Protection_rf=0
        x_zwave_values.Protection_timeout=null
        x_zwave_values.Version_firmwareVersions=["25.25"]
        x_zwave_values.Version_libraryType=3
        x_zwave_values.Version_protocolVersion="3.52"
        zwave_device.capabilities=[37,38,49,50,112,114,117,134,145]
        zwave_device.endpoint=0
        zwave_device.failed=false
        zwave_device.generic_class="Multilevel Switch"
        zwave_device.impl_sig="24225:1:22315:1"
        zwave_device.is_beaming=false
        zwave_device.is_listening=true
        zwave_device.is_routing=true
        zwave_device.is_secure=false
        zwave_device.manufacturer_info=[271,770,4096]
        zwave_device.max_data_rate=null
        zwave_device.node_id=5
        zwave_device.specific_class="Motor Control Class B"
        zwave_device.status=4
        zwave_device.status_text="alive"
        zwave_device.version_info=[null,"25.25"]
        

        Thanks.

        --
        On a mission to automate everything.

        My MS Reactor contrib
        My Luup Plug-ins

        1 Reply Last reply
        0
        • therealdbT Offline
          therealdbT Offline
          therealdb
          wrote on last edited by
          #4

          Looking at a shutter right now, and power_sensor and energy_sensor seems to be ignored as well. Thanks.

          --
          On a mission to automate everything.

          My MS Reactor contrib
          My Luup Plug-ins

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

            Pull the latest build (new) and try it.

            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
            • therealdbT Offline
              therealdbT Offline
              therealdb
              wrote on last edited by
              #6

              Nope, position isn't working and I lost dimming, so it's basically not working. Cover state is reported correctly. power_sensor is not updating.

              --
              On a mission to automate everything.

              My MS Reactor contrib
              My Luup Plug-ins

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

                "It's not working" isn't actionable. You know what I need.

                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
                • therealdbT Offline
                  therealdbT Offline
                  therealdb
                  wrote on last edited by
                  #8

                  Ok, here we go.
                  In details:

                  • OK: cover.close/open
                  • KO: cover.stop, position.*

                  Taken from zwawejs.log

                  [latest-24212]2024-08-20T14:54:29.867Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>4-0 with [Object]{  }
                  [latest-24212]2024-08-20T14:54:29.869Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.open set node 4 endpoint 0 value 38:targetValue:(undefined) = 99
                  [latest-24212]2024-08-20T14:54:29.871Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 99 }
                  [latest-24212]2024-08-20T14:54:33.806Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.close on Cover#zwavejs>4-0 with [Object]{  }
                  [latest-24212]2024-08-20T14:54:33.808Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.close set node 4 endpoint 0 value 38:targetValue:(undefined) = 0
                  [latest-24212]2024-08-20T14:54:33.809Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 0 }
                  [latest-24212]2024-08-20T14:54:36.322Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>4-0 with [Object]{  }
                  [latest-24212]2024-08-20T14:54:36.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.open set node 4 endpoint 0 value 38:targetValue:(undefined) = 99
                  [latest-24212]2024-08-20T14:54:36.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 99 }
                  [latest-24212]2024-08-20T14:55:02.507Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.increase on Cover#zwavejs>4-0 with [Object]{ "amount": 0.1 }
                  [latest-24212]2024-08-20T14:55:04.523Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.increase on Cover#zwavejs>4-0 with [Object]{ "amount": 0.1 }
                  [latest-24212]2024-08-20T14:55:10.073Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 }
                  [latest-24212]2024-08-20T14:55:13.023Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.set on Cover#zwavejs>4-0 with [Object]{ "value": 0.3 }
                  

                  --
                  On a mission to automate everything.

                  My MS Reactor contrib
                  My Luup Plug-ins

                  1 Reply Last reply
                  0
                  • therealdbT Offline
                    therealdbT Offline
                    therealdb
                    wrote on last edited by
                    #9

                    btw, maybe it's related to the device being a Motor Control Class B and not Motor Control Class C? Looking at zwavejs_devices.yaml, there seems to be a different implementation.

                    --
                    On a mission to automate everything.

                    My MS Reactor contrib
                    My Luup Plug-ins

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

                      Class B doesn't have position, per Z-Wave specs. So that's the manufacturer providing the wrong device class data. Fibaro does a lot of this. Their firmware is trash. Also, this is a different device than previously reported (node 4 vs node 148), so you are moving the goal posts on me. So go back to 148 and tell me what's going on there, then we'll worry about 4 (different version of similar device).

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

                      therealdbT 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        Class B doesn't have position, per Z-Wave specs. So that's the manufacturer providing the wrong device class data. Fibaro does a lot of this. Their firmware is trash. Also, this is a different device than previously reported (node 4 vs node 148), so you are moving the goal posts on me. So go back to 148 and tell me what's going on there, then we'll worry about 4 (different version of similar device).

                        therealdbT Offline
                        therealdbT Offline
                        therealdb
                        wrote on last edited by
                        #11

                        @toggledbits sorry. node 148 is working as expected. this is a RS3. node 4 is a RS2.

                        here's node 4:

                        cover.state=true
                        energy_sensor.units="kWh"
                        energy_sensor.value=6.58
                        position.value=null
                        power_sensor.units="W"
                        power_sensor.value=0
                        power_switch.state=true
                        x_debug.dt={"0":769,"1":4097,"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","manufacturerId":271,"productType":770,"productId":4096}
                        x_zwave_values.Binary_Switch_currentValue=true
                        x_zwave_values.Binary_Switch_targetValue=null
                        x_zwave_values.Configuration_Delay_Time_After_S2=10
                        x_zwave_values.Configuration_Energy_Reports=10
                        x_zwave_values.Configuration_Forced_Roller_Shutter_Calibration=0
                        x_zwave_values.Configuration_Lamellas_Positioning_Mode=1
                        x_zwave_values.Configuration_Managing_Lamellas_in_Response_to_Alarm=0
                        x_zwave_values.Configuration_Motor_Operation_Detection=0
                        x_zwave_values.Configuration_Motor_Operation_Time=240
                        x_zwave_values.Configuration_Periodic_Power_or_Energy_Reports=3600
                        x_zwave_values.Configuration_Power_Reports=10
                        x_zwave_values.Configuration_Reports_Type=0
                        x_zwave_values.Configuration_Response_to_General_Alarm=0
                        x_zwave_values.Configuration_Response_to_Smoke_CO_CO2_Alarm=0
                        x_zwave_values.Configuration_Response_to_Temperature_Alarm=0
                        x_zwave_values.Configuration_Response_to_Water_Flood_Alarm=0
                        x_zwave_values.Configuration_Roller_Shutter_Operating_Modes=1
                        x_zwave_values.Configuration_Scenes_Associations_Activation=1
                        x_zwave_values.Configuration_Self_Measurement=0
                        x_zwave_values.Configuration_Switch_Type=0
                        x_zwave_values.Configuration_Turning_Time_Delay_Time=150
                        x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=99
                        x_zwave_values.Manufacturer_Specific_manufacturerId=271
                        x_zwave_values.Manufacturer_Specific_productId=4096
                        x_zwave_values.Manufacturer_Specific_productType=770
                        x_zwave_values.Meter_reset=null
                        x_zwave_values.Meter_value_65537=6.58
                        x_zwave_values.Meter_value_66049=0
                        x_zwave_values.Multilevel_Sensor_Power=0
                        x_zwave_values.Multilevel_Switch_Close=null
                        x_zwave_values.Multilevel_Switch_Open=null
                        x_zwave_values.Multilevel_Switch_currentValue=99
                        x_zwave_values.Multilevel_Switch_duration=null
                        x_zwave_values.Multilevel_Switch_restorePrevious=null
                        x_zwave_values.Multilevel_Switch_targetValue=99
                        x_zwave_values.Protection_exclusiveControlNodeId=null
                        x_zwave_values.Protection_local=0
                        x_zwave_values.Protection_rf=0
                        x_zwave_values.Protection_timeout=null
                        x_zwave_values.Version_firmwareVersions=["25.25"]
                        x_zwave_values.Version_libraryType=3
                        x_zwave_values.Version_protocolVersion="3.52"
                        zwave_device.capabilities=[37,38,49,50,112,114,117,134,145]
                        zwave_device.endpoint=0
                        zwave_device.failed=false
                        zwave_device.generic_class="Multilevel Switch"
                        zwave_device.impl_sig="24233:1:24233:1"
                        zwave_device.is_beaming=false
                        zwave_device.is_listening=true
                        zwave_device.is_routing=true
                        zwave_device.is_secure=false
                        zwave_device.manufacturer_info=[271,770,4096]
                        zwave_device.max_data_rate=null
                        zwave_device.node_id=4
                        zwave_device.specific_class="Motor Control Class B"
                        zwave_device.status=4
                        zwave_device.status_text="alive"
                        zwave_device.version_info=[null,"25.25"]
                        

                        --
                        On a mission to automate everything.

                        My MS Reactor contrib
                        My Luup Plug-ins

                        1 Reply Last reply
                        0
                        • therealdbT Offline
                          therealdbT Offline
                          therealdb
                          wrote on last edited by
                          #12

                          Here's node 148 for reference:

                          cover.state=true
                          energy_sensor.units="kWh"
                          energy_sensor.value=0.41
                          position.value=0.92
                          power_sensor.units="W"
                          power_sensor.value=0
                          x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Roller Shutter 3","model":"FGR223","default_name":"Roller Shutter 3","values":[{"match":{"endpoint":[1,2],"commandClass":38,"property":"currentValue"},"entity_class":"Cover","primary_attribute":"cover.state","capabilities":{"cover":{"attributes":{"state":{"expr":"value !== 0"}},"actions":{"open":{"valueId":"+targetValue:#","value":99},"close":{"valueId":"+targetValue:#","value":0},"stop":{"valueId":"+Up:","value":false}}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"+targetValue:#","value":{"expr":"entity.attributes.cover.state ? 0 : 99"}}}}}}],"manufacturerId":271,"productType":771,"productId":4096}
                          x_zwave_values.Meter_reset=null
                          x_zwave_values.Meter_value_65537=0.41
                          x_zwave_values.Meter_value_66049=0
                          x_zwave_values.Multilevel_Switch_Down=null
                          x_zwave_values.Multilevel_Switch_Up=null
                          x_zwave_values.Multilevel_Switch_currentValue=91
                          x_zwave_values.Multilevel_Switch_duration="unknown"
                          x_zwave_values.Multilevel_Switch_restorePrevious=null
                          x_zwave_values.Multilevel_Switch_targetValue=91
                          x_zwave_values.Notification_Power_Management_Over_current_status=0
                          x_zwave_values.Notification_System_Hardware_status=0
                          x_zwave_values.Notification_alarmLevel=null
                          x_zwave_values.Notification_alarmType=null
                          zwave_device.capabilities=[38,50,113]
                          zwave_device.endpoint=1
                          zwave_device.failed=null
                          zwave_device.impl_sig="24233:1:24233:1"
                          zwave_device.manufacturer_info=null
                          zwave_device.node_id=148
                          zwave_device.version_info=null
                          

                          --
                          On a mission to automate everything.

                          My MS Reactor contrib
                          My Luup Plug-ins

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

                            OK. That's easy to fix, I think. Pull the updated zwavejs_data.zip file from the server and put in your config directory, restart Reactor, and let's see if 4 behaves better (I just applied the exceptions for the 223 to the 222, adjusted for a single endpoint).

                            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
                            • therealdbT Offline
                              therealdbT Offline
                              therealdb
                              wrote on last edited by
                              #14

                              Still not working. position.value is still null.

                              Logs:

                              [latest-24212]2024-08-20T15:19:14.892Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 }
                              [latest-24212]2024-08-20T15:19:20.349Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 }
                              [latest-24212]2024-08-20T15:19:29.900Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.close on Cover#zwavejs>4-0 with [Object]{  }
                              [latest-24212]2024-08-20T15:19:29.901Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.close set node 4 endpoint 0 value 38:targetValue:(undefined) = 0
                              [latest-24212]2024-08-20T15:19:29.903Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 0 }
                              [latest-24212]2024-08-20T15:19:32.172Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.close on Cover#zwavejs>4-0 with [Object]{  }
                              [latest-24212]2024-08-20T15:19:32.173Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.close set node 4 endpoint 0 value 38:targetValue:(undefined) = 0
                              [latest-24212]2024-08-20T15:19:32.174Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 0 }
                              [latest-24212]2024-08-20T15:19:34.602Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.stop on Cover#zwavejs>4-0 with [Object]{  }
                              [latest-24212]2024-08-20T15:19:36.567Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>4-0 with [Object]{  }
                              [latest-24212]2024-08-20T15:19:36.568Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.open set node 4 endpoint 0 value 38:targetValue:(undefined) = 99
                              [latest-24212]2024-08-20T15:19:36.570Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 99 }
                              [latest-24212]2024-08-20T15:19:45.548Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 }
                              

                              --
                              On a mission to automate everything.

                              My MS Reactor contrib
                              My Luup Plug-ins

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

                                OK. You're talking about an attribute, but showing me actions in a log. On my system, the FGR222 is now showing position.value correctly for any value in range.

                                Here's what my log looks like (position.set to 0.45 on device 4, using your configuration):

                                [###BUILDVERSION###]2024-08-20T15:25:04.586Z <ZWaveJSController#zwstatic:INFO> ZWaveJSController#zwstatic performing position.set on Cover#zwstatic>4-0 with [Object]{ "value": 0.45 }
                                [###BUILDVERSION###]2024-08-20T15:25:04.587Z <ZWaveJSController#zwstatic:5:ZWaveJSController.js:2135> ZWaveJSController#zwstatic def [Object]{ "endpoint": 0, "commandClass": 38, "property": "currentValue", "propertyKey": --undef--, "impl": { "valueId": "+targetValue:#", "value": { "expr": "max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )" } } }
                                [###BUILDVERSION###]2024-08-20T15:25:04.591Z <ZWaveJSController#zwstatic:INFO> ZWaveJSController#zwstatic action position.set set node 4 endpoint 0 value 38:targetValue:(null) = 45
                                [###BUILDVERSION###]2024-08-20T15:25:04.593Z <ZWaveJSController#zwstatic:5:ZWaveJSController.js:1760> ZWaveJSController#zwstatic _set_value(4,0,38,targetValue,(null),45)
                                [###BUILDVERSION###]2024-08-20T15:25:04.594Z <ZWaveJSController#zwstatic:INFO> ZWaveJSController#zwstatic setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 45 }
                                [###BUILDVERSION###]2024-08-20T15:25:04.596Z <ZWaveJSController#zwstatic:5:ZWaveJSController.js:335> ZWaveJSController#zwstatic sending #1724167504595<8/20/2024, 11:25:04 AM>: [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 45, "messageId": 1724167504595 }
                                

                                So both are working for me. I would try deleting the entity in MSR and restarting to recreate it. Then test again.

                                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
                                • therealdbT Offline
                                  therealdbT Offline
                                  therealdb
                                  wrote on last edited by
                                  #16

                                  I don't know what to say. I've deleted all the ZWaveJS entities, restarted and still no luck.

                                  --
                                  On a mission to automate everything.

                                  My MS Reactor contrib
                                  My Luup Plug-ins

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

                                    What is the impl_sig attribute on device 4?

                                    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
                                    • therealdbT Offline
                                      therealdbT Offline
                                      therealdb
                                      wrote on last edited by
                                      #18

                                      zwave_device.impl_sig="24233:1:24233:2"

                                      --
                                      On a mission to automate everything.

                                      My MS Reactor contrib
                                      My Luup Plug-ins

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

                                        Are you using position.set directly, or using the relative actions?

                                        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
                                        • therealdbT Offline
                                          therealdbT Offline
                                          therealdb
                                          wrote on last edited by
                                          #20

                                          position.set.

                                          --
                                          On a mission to automate everything.

                                          My MS Reactor contrib
                                          My Luup Plug-ins

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


                                          Recent Topics

                                          • Limit HA Entity in MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            5
                                            46

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

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            583

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

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

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

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

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

                                          • Deleting widgets
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            440

                                          • MQTT configuration question
                                            tunnusT
                                            tunnus
                                            0
                                            11
                                            592
                                          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