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
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
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
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

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

Scheduled Pinned Locked Moved Multi-System Reactor
37 Posts 2 Posters 4.6k 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
    #21

    That's wonderful. I have a FGR222 (previous fw) that's working. Here's node 3:

    cover.state=false
    energy_sensor.units="kWh"
    energy_sensor.value=0
    position.value=0
    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","description":"Roller Shutter","model":"FGRM222","default_name":"Roller Shutter","values":[{"match":{"commandClass":38,"property":"currentValue"},"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":769,"productId":4097}
    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=1
    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=0
    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=4097
    x_zwave_values.Manufacturer_Specific_productType=769
    x_zwave_values.Meter_reset=null
    x_zwave_values.Meter_value_65537=0
    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=0
    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=["24.24"]
    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:2"
    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,769,4097]
    zwave_device.max_data_rate=null
    zwave_device.node_id=3
    zwave_device.specific_class="Motor Control Class B"
    zwave_device.status=4
    zwave_device.status_text="alive"
    zwave_device.version_info=[null,"24.24"]
    

    --
    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
      #22

      OK. I think I see it. #4 has a different type and ID, and the alias has an error. Pull the new data ZIP and try 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
        #23

        That did the trick. Two things. position.value is now incosistent, whereas dimming.level was ok before. I tried to set node 4 to .9, and it's now reporting .31. A refresh is updating the position (to .91), but now power_switch.state=null.

        power_sensor.value is still 0.

        --
        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
          #24

          What are you comparing it to? For node 4, the last data you show have the Meter class value (meterType 1, property value, propertyKey 66049) at 0, and the Multilevel Sensor with sensorType=4 (Power) also 0. What are you expecting the value to be? Again, can you show more context, too? Post all the attributes? These things are moving targets, so more data is better than less.

          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
            #25

            I'm getting the values from ZWaveJS UI and checking on the reported values from MSR:

            Position
            image.png f31be680-d42d-4308-a81c-0c88f7372517-image.png

            Watts reading seems to be more related to the device not refreshing itself (or refreshing randomly), as it was doing on Vera. I'll keep debugging the ZWaveJS part, since it seems that if I refresh the device, the values is passed onto Reactor.

            Thanks for the help!

            --
            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
              #26

              Sorry, but the image looks like you're showing position, not watts. I would like to understand which of the two power values provided by the device you are trying to reconcile.

              That said, a position of 0.91 would be correct, as the scale of the position.value attribute in Reactor is 0.0 to 1.0, computed from the device range of 0 to 99 (90/99 = 0.91 rounded to two digits).

              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

                Sorry, but the image looks like you're showing position, not watts. I would like to understand which of the two power values provided by the device you are trying to reconcile.

                That said, a position of 0.91 would be correct, as the scale of the position.value attribute in Reactor is 0.0 to 1.0, computed from the device range of 0 to 99 (90/99 = 0.91 rounded to two digits).

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

                @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                Sorry, but the image looks like you're showing position, not watts. I would like to understand which of the two power values provided by the device you are trying to reconcile.

                no screenshot. As I've said, I'm finding that the device is not reporting that well. I'm 100% sure it was OK under Vera, and maybe it was part of the custom code they wrote for the device, Idk.

                @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                That said, a position of 0.91 would be correct, as the scale of the position.value attribute in Reactor is 0.0 to 1.0, computed from the device range of 0 to 99 (90/99 = 0.91 rounded to two digits).

                ok, but I've asked for 0.90 via Reactor and I got 0.91 inside Reactor and 0.90 inside ZWaveJS. Imagine something that tries to position the device until it is OK...

                --
                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
                  #28

                  The rounding is a function of the scaling.

                  I believe I mentioned in another thread that comparing equality of floating point numbers is a well-known Bad Idea in pretty much all programming languages.

                  The raw value is always available in the x_ extended 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
                    #29

                    so, the correct way is to look for x_zwave_values.Multilevel_Switch_currentValue and divide by 100?

                    EDIT: anyway, I still think that this behavior is not OK, because value are not consistent, but the call is yours.

                    --
                    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
                      #30

                      I can change it, but it may be a breaking change for all users at this point. Not something to be taken lightly. I have considered it.

                      I still don't have enough information from you to do anything about the power issue, assuming there still is one.

                      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

                        I can change it, but it may be a breaking change for all users at this point. Not something to be taken lightly. I have considered it.

                        I still don't have enough information from you to do anything about the power issue, assuming there still is one.

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

                        @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                        I can change it, but it may be a breaking change for all users at this point. Not something to be taken lightly. I have considered it.

                        No problem, I found it strange and I was reporting. It's also strange 'cause after a refresh the value from the controller is overwritten.

                        I still don't have enough information from you to do anything about the power issue, assuming there still is one.

                        Yes, but it's zwavejs that's not updating. I suspect Vera was doing some magic behind the scene. I'll keep watching it, now that the new system is almost stable.

                        --
                        On a mission to automate everything.

                        My MS Reactor contrib
                        My Luup Plug-ins

                        toggledbitsT 1 Reply Last reply
                        0
                        • therealdbT therealdb

                          @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                          I can change it, but it may be a breaking change for all users at this point. Not something to be taken lightly. I have considered it.

                          No problem, I found it strange and I was reporting. It's also strange 'cause after a refresh the value from the controller is overwritten.

                          I still don't have enough information from you to do anything about the power issue, assuming there still is one.

                          Yes, but it's zwavejs that's not updating. I suspect Vera was doing some magic behind the scene. I'll keep watching it, now that the new system is almost stable.

                          toggledbitsT Offline
                          toggledbitsT Offline
                          toggledbits
                          wrote on last edited by
                          #32

                          @therealdb said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                          Yes, but it's zwavejs that's not updating.

                          I see. I guess I didn't understand that before. OK. Let me know if you figure anything out that helps. There may be something I can bolt on to help with that. There do seem to be delta-sensitivity configuration settings on the device. I wonder if those are related?

                          So for the moment, have we covered all the hot-button items? Anything I haven't addressed yet?

                          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

                            @therealdb said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                            Yes, but it's zwavejs that's not updating.

                            I see. I guess I didn't understand that before. OK. Let me know if you figure anything out that helps. There may be something I can bolt on to help with that. There do seem to be delta-sensitivity configuration settings on the device. I wonder if those are related?

                            So for the moment, have we covered all the hot-button items? Anything I haven't addressed yet?

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

                            @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                            There do seem to be delta-sensitivity configuration settings on the device. I wonder if those are related?

                            Maybe. I'm experimenting with parameter and I'll report back. I still have a couple of strange behaviors to fix before I could dedicate to fine tuning.

                            @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                            So for the moment, have we covered all the hot-button items? Anything I haven't addressed yet?

                            Yes, the only thing pending is tilt position. I managed to use it via raw ZWave commands, but I think it could useful to have a separate endpoint for that. RS 3 and 4 are already exposing multiple endpoints, where the first is controlling the blind and the second the lamellas (and root does nothing).

                            Unfortunately, those from Fibaro are the only ZWave devices in Europe that are supporting lamellas. I'm sure eventually Shelly will catchup with its new ZWave series from Qubino and I'll eventually replace my RS2s, since they're not ZWave+ and are 8+ years old (I bought them for the old house, where I started with just roller shutters, so they served their purpose well).

                            --
                            On a mission to automate everything.

                            My MS Reactor contrib
                            My Luup Plug-ins

                            toggledbitsT 1 Reply Last reply
                            0
                            • therealdbT therealdb

                              @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                              There do seem to be delta-sensitivity configuration settings on the device. I wonder if those are related?

                              Maybe. I'm experimenting with parameter and I'll report back. I still have a couple of strange behaviors to fix before I could dedicate to fine tuning.

                              @toggledbits said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                              So for the moment, have we covered all the hot-button items? Anything I haven't addressed yet?

                              Yes, the only thing pending is tilt position. I managed to use it via raw ZWave commands, but I think it could useful to have a separate endpoint for that. RS 3 and 4 are already exposing multiple endpoints, where the first is controlling the blind and the second the lamellas (and root does nothing).

                              Unfortunately, those from Fibaro are the only ZWave devices in Europe that are supporting lamellas. I'm sure eventually Shelly will catchup with its new ZWave series from Qubino and I'll eventually replace my RS2s, since they're not ZWave+ and are 8+ years old (I bought them for the old house, where I started with just roller shutters, so they served their purpose well).

                              toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by
                              #34

                              @therealdb said in [ZwaveJS] Position and cover not working for Roller Shutter 1/2/3:

                              Yes, the only thing pending is tilt position.

                              OK. I've lost the thread there. What's the problem with tilt at this point? In my bench-top use, changes in the Z-Wave reports feed to the position attribute correctly, so I'm not clear where the issue remains.

                              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
                                #35

                                Sorry, I was referring to this thread: https://smarthome.community/topic/1576/zwavejs-venetian-blind-tilt-for-fibaro-roller-shutters-2-fgr222/4

                                --
                                On a mission to automate everything.

                                My MS Reactor contrib
                                My Luup Plug-ins

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

                                  ok, meter fixed. I don't know how it worked all these years, but the associations of device 4 were completely wrong (assigned to a non-existence device), thus it was somewhat working on Vera. Go figure. I reset the values and now it's reporting ok.

                                  The very last thing about the device is that, after configuring a parameter, they support scene activation v0 and it would be nice to have a separate scene device, as in the switch. Otherwise, I'll simply go with x_zwave_values. 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
                                    #37

                                    Try activating the central scene on the device. Since these values are events, they aren't created until the first event is received. You may also need to refresh the browser, or at least "stimulate" the redraw of the entity list (by modifying the filters, etc.).

                                    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
                                    • toggledbitsT toggledbits locked this topic on
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    Recent Topics

                                    • Gradually turn on lights.
                                      G
                                      gwp1
                                      0
                                      4
                                      140

                                    • Stop the MSR by an external switch on Hubitat.
                                      wmarcolinW
                                      wmarcolin
                                      0
                                      1
                                      35

                                    • Error After Upgrade
                                      G
                                      gwp1
                                      0
                                      4
                                      105

                                    • Reset attribute value of entity in event handler
                                      R
                                      RHCPNG
                                      0
                                      5
                                      205

                                    • Need help figuring out how to delay a reset on reaction
                                      G
                                      gwp1
                                      0
                                      22
                                      929

                                    • Way to search for rules (rule state) in other rules
                                      T
                                      tamorgen
                                      0
                                      3
                                      101

                                    • Links to MSR from HA
                                      Tom_DT
                                      Tom_D
                                      0
                                      1
                                      91

                                    • Set Reaction > Script Action
                                      wmarcolinW
                                      wmarcolin
                                      0
                                      11
                                      437

                                    • Wiring Samotech SM308-S into light fitting
                                      akbooerA
                                      akbooer
                                      0
                                      2
                                      151

                                    • Errors after updating to MQTTController build 25139
                                      toggledbitsT
                                      toggledbits
                                      0
                                      6
                                      239

                                    • 🎉 My very first MSR controller: OpenSprinkler
                                      therealdbT
                                      therealdb
                                      5
                                      13
                                      919

                                    • Advice reqeusted to migrate MSR from Bare Metal to Container
                                      T
                                      tamorgen
                                      0
                                      5
                                      263
                                    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