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. Hardware
  3. Z-Wave.me
  4. Add Indicator commandClass to zNode metric
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
UZB/RaZberry Firmwares - Update
S
Topic thumbnail image
Z-Wave.me
Docker container for Z-Way
S
Hey guys ... I've started creating a Docker container for Z-Way. I was previously using the Razberry2 but found it a bit slow on my Raspberry Pi 3. I could upgrade to a Raspberry Pi 4 but since I already run a dedicated Linux server and many Docker containers I thought it might make more sense to run Z-Way on there. GitHub: https://github.com/sofakng/docker-zway DockerHub: https://hub.docker.com/repository/docker/sofakng/zway This container is based on other containers that are no longer updated: (ruimarinho/docker-z-way) and (EugenMayer/docker-image-zway) I'd love to hear feedback and any improvements that might be needed. One thing I want to add immediately is to separate the configuration files from the Docker volume but it looks like Z-Way has several user configuration files/directories? $ZWAY_DIR/config/Configuration.xml $ZWAY_DIR/config/Rules.xml $ZWAY_DIR/config/maps $ZWAY_DIR/config/zddx $ZWAY_DIR/automation/user_syscommands $ZWAY_DIR/automation/storage $ZWAY_DIR/automation/userModules $ZWAY_DIR/htdocs/smarthome/user $ZWAY_DIR/config.xml
Z-Wave.me
Migration to Virtualisation
CatmanV2C
Not 100% sure this is the best place, but this seems to be the sticking point. Background: My NotVera system has been working perfectly now for some years. USB Z wave stick in an old Intel NUC. The NUC has a bare metal install of Debian buster, and on that we have: Z-wave Smart Home OpenLuup AltUI MSR Mosquito server Home Automation Bridge. I also have a bare metal Raspian install of Home Assistant running on a Pi Due to my Buffalo Linkstation doing some odd stuff (like suddenly disconnecting, while maintaining everything was fine) I bit the bullet and bought a Synology DS224+ Now, given the age of my NUC I'm thinking that I should probably start thinking about how to replace / safeguard it. Pretty happy that I can make an image of the existing disk and drop it onto a virtual machine in the Synology, or re-install / restore or do some other things (not decided what yet) but I get stuck on the USB dongle. Can I connect that to a VM on the NAS, or do I need another solution? TIA C
Z-Wave.me
Razberry firmware upgrade from 5.04 to 5.27
S
I have a Razberry v2 with firmware v5.04, and Bootloader v8aaa with CRC 35498 (I did manage to upgrade to this version using the "ZMESerialUpdater" tool ). I want to upgrade the firmware to v5.27, which Z-Wave.me Support say is the newest version that my hardware can handle without bricking it. Firmware v5.27 introduces the Analytics tab, according to Poltos, which is what I want. I have been studying the firmware map (https://service.z-wave.me/expertui/uzb-stats/versions-graph.html?with_hidden) which I sort-of understand. I have also got the "ZMESerialUpdater" tool to do the update, and could use it if I knew which binaries to use. My question is, what firmware update route do I use to get from v5.04 to v5.27? What exactly are the URLs of the binaries (as in "UPD_FIRMWARE_Razberry500_from_05_04_to_05_07.bin")? Somewhat confused! ScotsDon
Z-Wave.me
UZB Firmware update failed!
D
Topic thumbnail image
Z-Wave.me
Z-Wave RF optimization
rafale77R
Topic thumbnail image
Z-Wave.me
Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
E
Topic thumbnail image
Z-Wave.me
z-way-server new release
rafale77R
Lagging a little here but I just upgraded my z-way-server version and couldn't find much information on their website or even forum. https://storage.z-wave.me/z-way-server/ What is interesting for the ubuntu/debian version is that it is now released as a .deb package making upgrades much easier. I just downloaded the package and ran: dpkg -i z-way-*.deb and nothing else. The previous versions required some manual work since it was just a bunch of files for us to overwrite our installations. From the release note, there could be interesting things for some folks here. It is a pretty long list compared to the previous incremental release.
Z-Wave.me
Z-way backup strategy
A
For all systems backup is a vital part of the long-term usability. I thought that I describe my set up with Z-way so far. Hopefully others can fill in with their backup thoughts as well. I am sure that there are much more streamlined ways of doing this and hope to learn from you all. I run Z-way on a Raspberry Pi 3B+ with a daughter RaZberry card. In order to reduce the risk of getting corrupt SD cards I have it running off an SSD. So far this works very well. Setting it up was really easy just reading a standard Raspbian image onto the SSD. The only minor obstacle was that I had to test a few old 2.5" enclosures to find one that the Pi liked. The Pi is then also powered via an UPS, hopefully this will avoid problems in the event of power outages. In order to backup Z-way I have so far done manual backups from the regular Smarthome backup & restore function creating .zab files and from the Expert UI creating .zbk files. As far as I have understood the .zab files which are bigger contain more information than the .zbk files. The strategy so far has been to make backup files after each inclusion/exclusion. Also before updating Z-way. I have yet to test restoring from these files. From Smarthome it is also possible to set up cloud backup. I have not yet set up this as I need to decide that it is safe enough to do so. On the other hand I had this set up on my two Veras. It would have been nice to be able to schedule a local backup of Z-way instead of having to put them in the cloud, perhaps from OpenLuup via the Z-way bridge? In addition to the built in backup function I try to do complete image copies of the SD cards on my Pi's with Win32DiskImager. When I moved to an SSD the image file grew to the size of the SSD since it is a raw copy including all the empty space. Image files of 160GB are not practical to handle so I found a good instruction on how to shrink the .img file with Gparted in Linux: https://steemit.com/raspberrypi/@wizzle/shrink-raspberry-pi-images-using-windows-virtualbox-running-raspberry-pi-desktop By shrinking the .img file with Gparted it is now a more reasonable 4GB. These file are stored on my NAS for safekeeping. The strategy here so far is to make a new image file before updating Z-way and to use these in combination with more frequent Z-way backups. I have tested restoring a Gparted shrinked .img file to the SSD when my Z-way for some strange reason became unreachable through the regular UI but remained reachable through the Expert UI. Always good to test the restore function and to see that it works. The downside of the .img strategy is that I need to power-off the Pi for a while when making the backup. However if the Z-way backup files work then the complete .img backup need not be done so very often. //ArcherS
Z-Wave.me
Z-way video tutorials
P
Have found these videos very informative as a zway(ve) novice .... https://www.youtube.com/watch?v=kW8UXYxSI2k&t=2902s https://www.youtube.com/watch?v=wbNL0ISw58s&t=3230s https://www.youtube.com/watch?v=VU4SXNBfQx4
Z-Wave.me
Lifeline/TKB switches
P
Have a number of TKB plug switches (TZ68) that are not reporting to the controller. Believe they should be associated to Z-Way in Group 1 but am not able to get the devices to report groups in the interview/call for NIF process and so there are no associations possible. Thermosat is telling them to come on/off (hurrah!) but they don't report their on/off status in the gui. In Associations tab: Can not configure associations: groups were not reported by the device. Do interview.
Z-Wave.me
Switched from RaZberry to UZB
K
Night and day difference for me. I think I was getting a lot of interference in my media closet. Devices were very slow to respond and sometimes not at all. Switched to UZB and used a USB extender to place it a good 5 ft from the location of my pi. Now things are fast and reliable.
Z-Wave.me
UZB and Zway server installation
P
(Solved - presume pijuice hat was upset battery wasn't connected. Took out the plastic protector and UZB now showing. Next - upgrade UZB firmware) Have I missed something? UZB not showing up in Zway ... Downloaded Raspberry Pi Imager and used to set up os (Buster) on an 8gb SD https://www.raspberrypi.org/software/ Then installed Zway from Terminal wget -q -O - https://storage.z-wave.me/RaspbianInstall | sudo bash https://z-wave.me/z-way/download-z-way/ Plugged in UZB Changed port to /dev/ttyACM0 in menu/apps/ZWave network access in basic UI
Z-Wave.me
Rpi kit
P
This arrived today - hope it has enough juice for the uzb. https://coolcomponents.co.uk/products/pijuice-hat-a-portable-power-platform-for-every-raspberry-pi Shame the cases are sold out everywhere.
Z-Wave.me
z-way-server 3.1.0 release
rafale77R
Topic thumbnail image
Z-Wave.me
UZB Long Range
R
Hi guys, Does anyone know if the UZB supports Long Range already? I can't find which chip is in there.
Z-Wave.me
Getting status update from device
DesTD
Probably @rafale77 will jump on this question first I'm using the new model of GE/Jasco switch (they replaced the dead one I got) and the new model is having also S2 security and send instant status update BUT, And probably @rafale77 will say yes, is it possible that interference can do that I'm missing some instant update status ? Often, I'm having the wrong status in the zwave.me web interface...and even clicking the icon, the status didn't changed to right one. I also try to do some "On/Off" using the web interface, and the device itself physically, toggle without a problem, but the web interface is still no correct.
Z-Wave.me
Add Indicator commandClass to zNode metric
R
I'm trying to monitor the indicator command class of a 5 button scene controller in Z-Way so openluup can properly create and track it. seems like Z-Way COMMAND_CLASS_INDICATOR (0x87 or 135) are not being monitored by the ZWave module as I couldn't find anything for this command class in (/z-way-server-path/automation/modules/ZWave/index.js) When a Get or Set Indicator command class request is sent to the controller. ZSniffer picks up the request and response just fine although this packets are not being monitored by the zwave module Example: ZWayIP:8083/ZWaveAPI/Run/SendData(NodeID,[ Command_Class, Instance, Value ]) ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 0x87, 0x01, 0x01 ]) (Hexa) ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 135, 1, 1 ]) (Decimal) the answer looks like: [2020-04-24 19:59:36.261] [I] [zway] Waiting for job reply: Indicator Get [2020-04-24 19:59:36.281] [D] [zway] RECEIVED: ( 01 0B 00 04 00 02 03 87 03 01 B6 00 C2 ) [2020-04-24 19:59:36.281] [D] [zway] SENT ACK I’d like to store the Indicator response “RECEIVED” correctly. I believe by modifying the index.js of the zwave module could do the trick and once the module start tracking the indicator command class values as a metric then openluup's z-way plugin would properly track any changes as well. I'm wondering if anyone around here could share any thoughts or comments that could make it easier...
Z-Wave.me
Aeon Multisensor 6 issue
PerHP
Posting here, as the z-wave.me forum seems desolated.. I have two multisensor 6 sensors, and one of them is not sending motion sensor updates? Looking at the configuration, they are both registered as battery sensors for som reason, even if they are USB powered. They respond quickly to parameter changes, except for parameter 100 and 110, that will not update. Any clues? How do i convince the controller that they are USB powered?
Z-Wave.me

Add Indicator commandClass to zNode metric

Scheduled Pinned Locked Moved Z-Wave.me
19 Posts 5 Posters 1.6k Views 5 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.
  • R Offline
    R Offline
    ronluna
    wrote on last edited by ronluna
    #1

    I'm trying to monitor the indicator command class of a 5 button scene controller in Z-Way so openluup can properly create and track it.

    seems like Z-Way COMMAND_CLASS_INDICATOR (0x87 or 135) are not being monitored by the ZWave module as I couldn't find anything for this command class in (/z-way-server-path/automation/modules/ZWave/index.js)

    When a Get or Set Indicator command class request is sent to the controller. ZSniffer picks up the request and response just fine although this packets are not being monitored by the zwave module
    Example:

    ZWayIP:8083/ZWaveAPI/Run/SendData(NodeID,[ Command_Class, Instance, Value ])
    ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 0x87, 0x01, 0x01 ]) (Hexa)
    ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 135, 1, 1 ]) (Decimal)
    

    the answer looks like:

    [2020-04-24 19:59:36.261] [I] [zway] Waiting for job reply: Indicator Get
    [2020-04-24 19:59:36.281] [D] [zway] RECEIVED: ( 01 0B 00 04 00 02 03 87 03 01 B6 00 C2 )
    [2020-04-24 19:59:36.281] [D] [zway] SENT ACK
    

    I’d like to store the Indicator response “RECEIVED” correctly. I believe by modifying the index.js of the zwave module could do the trick and once the module start tracking the indicator command class values as a metric then openluup's z-way plugin would properly track any changes as well.

    I'm wondering if anyone around here could share any thoughts or comments that could make it easier...

    P 1 Reply Last reply
    1
    • rafale77R Offline
      rafale77R Offline
      rafale77
      wrote on last edited by
      #2

      This is the problem with not having the bridge polling the zwave API or even the JS API. The readback is only from the Automation API which is more limited. You can obviously get the signal readback from the zwave API...
      Only three ways to get around this:
      Ask PoltoS to bridge this command class to the Automation API,
      Write a plugin in JS for Z-way. (I may be able to do this but will be learning in the process)
      Or... rely on @akbooer’s future change to move the bridge to one of the other APIs if this is still the plan.

      1 Reply Last reply
      1
      • R Offline
        R Offline
        ronluna
        wrote on last edited by
        #3

        not sure @akbooer would be in the mood migrate form the automation API and as you mentioned it seems is very limited as well.

        1 Reply Last reply
        0
        • rafale77R Offline
          rafale77R Offline
          rafale77
          wrote on last edited by
          #4

          We have been discussing it and it was clear that eventually it would be the direction we would have to take. A lot of the refactoring he has been doing to the bridge is to prepare for such a move.

          1 Reply Last reply
          0
          • akbooerA Offline
            akbooerA Offline
            akbooer
            wrote on last edited by
            #5

            Yes, this is the (a) plan. Each of the APIs has their own merit. I will, no doubt, end up with using aspects of all of them.

            But I’m a bit busy at the moment, and this, I think, is mainly a cosmetic issue?

            1 Reply Last reply
            0
            • R ronluna

              I'm trying to monitor the indicator command class of a 5 button scene controller in Z-Way so openluup can properly create and track it.

              seems like Z-Way COMMAND_CLASS_INDICATOR (0x87 or 135) are not being monitored by the ZWave module as I couldn't find anything for this command class in (/z-way-server-path/automation/modules/ZWave/index.js)

              When a Get or Set Indicator command class request is sent to the controller. ZSniffer picks up the request and response just fine although this packets are not being monitored by the zwave module
              Example:

              ZWayIP:8083/ZWaveAPI/Run/SendData(NodeID,[ Command_Class, Instance, Value ])
              ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 0x87, 0x01, 0x01 ]) (Hexa)
              ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 135, 1, 1 ]) (Decimal)
              

              the answer looks like:

              [2020-04-24 19:59:36.261] [I] [zway] Waiting for job reply: Indicator Get
              [2020-04-24 19:59:36.281] [D] [zway] RECEIVED: ( 01 0B 00 04 00 02 03 87 03 01 B6 00 C2 )
              [2020-04-24 19:59:36.281] [D] [zway] SENT ACK
              

              I’d like to store the Indicator response “RECEIVED” correctly. I believe by modifying the index.js of the zwave module could do the trick and once the module start tracking the indicator command class values as a metric then openluup's z-way plugin would properly track any changes as well.

              I'm wondering if anyone around here could share any thoughts or comments that could make it easier...

              P Offline
              P Offline
              PoltoS
              wrote on last edited by
              #6

              @ronluna said in Add Indicator commandClass to zNode metric:

              I'm wondering if anyone around here could share any thoughts or comments that could make it easier...

              You are right, Indicator CC is handled by lib zway, but is implemented on the high level yet. You can copy everything about Switch Multilevel and rename this part to Indicator. It will add support of this CC. You can them make a pull request to include it in the dev branch on our github. Or wait for us to implement it.

              1 Reply Last reply
              2
              • R Offline
                R Offline
                ronluna
                wrote on last edited by ronluna
                #7

                @PoltoS I've started your suggestion for adding Scene Controller indicator class and scene activation following your comment above by simply replicating "Switch Multilevel" in the index.js . Although wondering if this approach would be acceptable to submitted to the dev branch.

                After modifying the z-way-server-path/automation/modules/ZWave/index.js and adding the command classes 135 and 45 as:

                	this.CC = {
                		"Basic": 0x20,
                		"SwitchBinary": 0x25,
                		"SwitchMultilevel": 0x26,
                		"SwitchColor": 0x33,
                		"SoundSwitch": 0x79,
                		"SceneActivation": 0x2b,
                		"Alarm": 0x71,
                		"AlarmSensor": 0x9c,
                		"SensorBinary": 0x30,
                		"SensorMultilevel": 0x31,
                		"Meter": 0x32,
                		"MeterPulse": 0x35,
                		"ThermostatMode": 0x40,
                		"ThermostatSetPoint": 0x43,
                		"ThermostatFanMode": 0x44,
                		"DoorLock": 0x62,
                		"CentralScene": 0x5b,
                		"Battery": 0x80,
                		"DeviceResetLocally": 0x5a,
                		"BarrierOperator": 0x66,
                		"Wakeup": 0x84,
                		"Indicator": 0x87,
                		"sceneControllerConf": 0x2D
                	};
                

                And:

                				} else if (this.CC["sceneControllerConf"] === commandClassId) {
                
                			var devId = vDevId + separ + 'DS';
                
                			defaults = {
                				deviceType: 'sensorDiscrete',
                				location: smartStartEntryPreset && _.isNumber(smartStartEntryPreset.location)? smartStartEntryPreset.location : 0,
                				probeType: 'control',
                				metrics: {
                					probeTitle: 'Control',
                					icon: 'gesture',
                					level: '',
                					stat: '',
                					title: compileTitle('Sensor', 'Control', vDevIdNI),
                					state: '',
                					currentScene: '',
                					discreteStates: {},
                					isFailed: false
                				}
                			};
                
                			// apply postfix if available
                			if (changeVDev[changeDevId]) {
                				defaults = applyPostfix(defaults, changeVDev[changeDevId], devId, vDevIdNI);
                			}
                
                			var vDev = self.controller.devices.create({
                				deviceId: devId,
                				defaults: defaults,
                				overlay: {},
                				handler: function(command) {
                					if (command === "update") {
                						cc.Get();
                					}
                				},
                				moduleId: self.id
                			});
                
                
                			// disable value set on z-way startup
                			var startup = true;
                
                			setTimeout(function() {
                				startup = false;
                			}, 1000);
                
                
                			if (vDev) {
                				vDev.set('metrics:isFailed', self.zway.devices[nodeId].data.isFailed.value);
                				self.dataBind(self.gateDataBinding, self.zway, nodeId, instanceId, "SceneActivation", "currentScene", function(type) {
                					try {
                						if (!(type & self.ZWAY_DATA_CHANGE_TYPE["Invalidated"])) {
                							vDev.set("metrics:currentScene", this.value);
                						}
                					} catch (e) {}
                				}, "value");
                
                				self.dataBind(self.gateDataBinding, self.zway, nodeId, instanceId, "Indicator", "stat", function(type) {
                					try {
                						if (!(type & self.ZWAY_DATA_CHANGE_TYPE["Invalidated"])) {
                							vDev.set("metrics:stat", this.value);
                						}
                					} catch (e) {}
                				}, "value");
                
                			}
                

                The changes above start monitoring those two classes for my static scene controller

                http://z-way-server-ip:8083/ZAutomation/api/v1/devices shows the values as

                {
                creationTime: 1601994291,
                creatorId: 1,
                customIcons: { },
                deviceType: "sensorDiscrete",
                h: -849256330,
                hasHistory: false,
                id: "ZWayVDev_zway_17-0-45-DS",
                location: 0,
                locationName: "globalRoom",
                metrics: {
                probeTitle: "Control",
                icon: "gesture",
                level: "",
                title: "Cooper Control (#17)",
                state: "",
                currentScene: 5,
                discreteStates: { },
                isFailed: false,
                stat: 20,
                },
                nodeId: 17,
                order: {
                rooms: 0,
                elements: 0,
                dashboard: 0,
                },
                permanently_hidden: false,
                probeType: "control",
                tags: [ ],
                visibility: true,
                updateTime: 1602006617,
                },
                

                Now I'm wondering what would the best way to add support to this command classes (45 and 135) . "currentScene" would be for the last triggered scene and "stat" would be the Indicator value.

                @akbooer I've noticed that command class 45 is already there for Leviton Scene controller as:

                  -- Scene Controller Configuration
                  ["45"] = {
                    updater = function (d, inst)
                      d, inst = d, inst
                    end,
                
                     -- Leviton Zone/scene controller
                    files = { "D_SceneControllerLED1.xml", SID.SceneControllerLED, "D_SceneControllerLED1.json"},
                  },
                

                But is not grabbing the currentScene metric.

                Mind sharing a good approach for ZWay plugin to properly trace those two classes ?

                akbooerA 1 Reply Last reply
                0
                • R ronluna

                  @PoltoS I've started your suggestion for adding Scene Controller indicator class and scene activation following your comment above by simply replicating "Switch Multilevel" in the index.js . Although wondering if this approach would be acceptable to submitted to the dev branch.

                  After modifying the z-way-server-path/automation/modules/ZWave/index.js and adding the command classes 135 and 45 as:

                  	this.CC = {
                  		"Basic": 0x20,
                  		"SwitchBinary": 0x25,
                  		"SwitchMultilevel": 0x26,
                  		"SwitchColor": 0x33,
                  		"SoundSwitch": 0x79,
                  		"SceneActivation": 0x2b,
                  		"Alarm": 0x71,
                  		"AlarmSensor": 0x9c,
                  		"SensorBinary": 0x30,
                  		"SensorMultilevel": 0x31,
                  		"Meter": 0x32,
                  		"MeterPulse": 0x35,
                  		"ThermostatMode": 0x40,
                  		"ThermostatSetPoint": 0x43,
                  		"ThermostatFanMode": 0x44,
                  		"DoorLock": 0x62,
                  		"CentralScene": 0x5b,
                  		"Battery": 0x80,
                  		"DeviceResetLocally": 0x5a,
                  		"BarrierOperator": 0x66,
                  		"Wakeup": 0x84,
                  		"Indicator": 0x87,
                  		"sceneControllerConf": 0x2D
                  	};
                  

                  And:

                  				} else if (this.CC["sceneControllerConf"] === commandClassId) {
                  
                  			var devId = vDevId + separ + 'DS';
                  
                  			defaults = {
                  				deviceType: 'sensorDiscrete',
                  				location: smartStartEntryPreset && _.isNumber(smartStartEntryPreset.location)? smartStartEntryPreset.location : 0,
                  				probeType: 'control',
                  				metrics: {
                  					probeTitle: 'Control',
                  					icon: 'gesture',
                  					level: '',
                  					stat: '',
                  					title: compileTitle('Sensor', 'Control', vDevIdNI),
                  					state: '',
                  					currentScene: '',
                  					discreteStates: {},
                  					isFailed: false
                  				}
                  			};
                  
                  			// apply postfix if available
                  			if (changeVDev[changeDevId]) {
                  				defaults = applyPostfix(defaults, changeVDev[changeDevId], devId, vDevIdNI);
                  			}
                  
                  			var vDev = self.controller.devices.create({
                  				deviceId: devId,
                  				defaults: defaults,
                  				overlay: {},
                  				handler: function(command) {
                  					if (command === "update") {
                  						cc.Get();
                  					}
                  				},
                  				moduleId: self.id
                  			});
                  
                  
                  			// disable value set on z-way startup
                  			var startup = true;
                  
                  			setTimeout(function() {
                  				startup = false;
                  			}, 1000);
                  
                  
                  			if (vDev) {
                  				vDev.set('metrics:isFailed', self.zway.devices[nodeId].data.isFailed.value);
                  				self.dataBind(self.gateDataBinding, self.zway, nodeId, instanceId, "SceneActivation", "currentScene", function(type) {
                  					try {
                  						if (!(type & self.ZWAY_DATA_CHANGE_TYPE["Invalidated"])) {
                  							vDev.set("metrics:currentScene", this.value);
                  						}
                  					} catch (e) {}
                  				}, "value");
                  
                  				self.dataBind(self.gateDataBinding, self.zway, nodeId, instanceId, "Indicator", "stat", function(type) {
                  					try {
                  						if (!(type & self.ZWAY_DATA_CHANGE_TYPE["Invalidated"])) {
                  							vDev.set("metrics:stat", this.value);
                  						}
                  					} catch (e) {}
                  				}, "value");
                  
                  			}
                  

                  The changes above start monitoring those two classes for my static scene controller

                  http://z-way-server-ip:8083/ZAutomation/api/v1/devices shows the values as

                  {
                  creationTime: 1601994291,
                  creatorId: 1,
                  customIcons: { },
                  deviceType: "sensorDiscrete",
                  h: -849256330,
                  hasHistory: false,
                  id: "ZWayVDev_zway_17-0-45-DS",
                  location: 0,
                  locationName: "globalRoom",
                  metrics: {
                  probeTitle: "Control",
                  icon: "gesture",
                  level: "",
                  title: "Cooper Control (#17)",
                  state: "",
                  currentScene: 5,
                  discreteStates: { },
                  isFailed: false,
                  stat: 20,
                  },
                  nodeId: 17,
                  order: {
                  rooms: 0,
                  elements: 0,
                  dashboard: 0,
                  },
                  permanently_hidden: false,
                  probeType: "control",
                  tags: [ ],
                  visibility: true,
                  updateTime: 1602006617,
                  },
                  

                  Now I'm wondering what would the best way to add support to this command classes (45 and 135) . "currentScene" would be for the last triggered scene and "stat" would be the Indicator value.

                  @akbooer I've noticed that command class 45 is already there for Leviton Scene controller as:

                    -- Scene Controller Configuration
                    ["45"] = {
                      updater = function (d, inst)
                        d, inst = d, inst
                      end,
                  
                       -- Leviton Zone/scene controller
                      files = { "D_SceneControllerLED1.xml", SID.SceneControllerLED, "D_SceneControllerLED1.json"},
                    },
                  

                  But is not grabbing the currentScene metric.

                  Mind sharing a good approach for ZWay plugin to properly trace those two classes ?

                  akbooerA Offline
                  akbooerA Offline
                  akbooer
                  wrote on last edited by
                  #8

                  @ronluna said in Add Indicator commandClass to zNode metric:

                  But is not grabbing the currentScene metric.
                  Mind sharing a good approach for ZWay plugin to properly trace those two classes ?

                  This is just a stub, it doesn’t do anything.
                  I’ll take a look.

                  R 1 Reply Last reply
                  0
                  • akbooerA akbooer

                    @ronluna said in Add Indicator commandClass to zNode metric:

                    But is not grabbing the currentScene metric.
                    Mind sharing a good approach for ZWay plugin to properly trace those two classes ?

                    This is just a stub, it doesn’t do anything.
                    I’ll take a look.

                    R Offline
                    R Offline
                    ronluna
                    wrote on last edited by
                    #9

                    @akbooer I've tried adding

                        files = { nil, SID.EnergyMetering },
                      },
                    
                      -- IndicatorStatus
                      ["135"] = function (d, inst)
                        local indicatorStatus = tonumber (inst.metrics.stat)
                        setVar ("IndicatorStatus", indicatorStatus, SID[S_HaDevice], d)
                      end,
                    
                      -- Manufacturer proprietary
                      -- Leviton Zone/scene controller
                      ["145"] = {
                    

                    no joy

                    akbooerA 1 Reply Last reply
                    0
                    • R ronluna

                      @akbooer I've tried adding

                          files = { nil, SID.EnergyMetering },
                        },
                      
                        -- IndicatorStatus
                        ["135"] = function (d, inst)
                          local indicatorStatus = tonumber (inst.metrics.stat)
                          setVar ("IndicatorStatus", indicatorStatus, SID[S_HaDevice], d)
                        end,
                      
                        -- Manufacturer proprietary
                        -- Leviton Zone/scene controller
                        ["145"] = {
                      

                      no joy

                      akbooerA Offline
                      akbooerA Offline
                      akbooer
                      wrote on last edited by
                      #10

                      @ronluna said in Add Indicator commandClass to zNode metric:

                      I've tried adding

                      At first sight, that looks right. You're sure that your ZWay JS mods are doing the right thing?

                      Have you tried the same for the currentScene state?

                      R 1 Reply Last reply
                      0
                      • akbooerA akbooer

                        @ronluna said in Add Indicator commandClass to zNode metric:

                        I've tried adding

                        At first sight, that looks right. You're sure that your ZWay JS mods are doing the right thing?

                        Have you tried the same for the currentScene state?

                        R Offline
                        R Offline
                        ronluna
                        wrote on last edited by
                        #11

                        @akbooer I've tried with currentScene as well. the metric is being collected by ZAutomation/api just fine as shown here.

                        {
                        creationTime: 1601994291,
                        creatorId: 1,
                        customIcons: { },
                        deviceType: "sensorDiscrete",
                        h: -849256330,
                        hasHistory: false,
                        id: "ZWayVDev_zway_17-0-45-DS",
                        location: 0,
                        locationName: "globalRoom",
                        metrics: {
                        probeTitle: "Control",
                        icon: "gesture",
                        level: "",
                        title: "Cooper Control (#17)",
                        state: "",
                        currentScene: 5,
                        discreteStates: { },
                        isFailed: false,
                        stat: 20,
                        },
                        nodeId: 17,
                        order: {
                        rooms: 0,
                        elements: 0,
                        dashboard: 0,
                        },
                        permanently_hidden: false,
                        probeType: "control",
                        tags: [ ],
                        visibility: true,
                        updateTime: 1602028670,
                        },
                        

                        Even the Zway plugin see the classes on the device (In the example is device 17) but no their values.

                        4e1309cf-17df-449c-9626-6765334489c1-image.png

                        I've tried modifying L_ZWay2.lua as:

                             -- Leviton Zone/scene controller
                         --   files = { "D_SceneControllerLED1.xml", SID.SceneControllerLED, "D_SceneControllerLED1.json"},
                         -- },
                        
                          -- currentScene
                          ["45"] = function (d, inst)
                            local currentScene = tonumber (inst.metrics.currentScene)
                            setVar ("currentScene", currentScene, SID[S_HaDevice], d)
                        
                        end,
                        
                          -- binary sensor
                          ["48"] = {
                        

                        I'm not entirely sure that the ZWay js mods I've added is perfectly doing the right thing, I'm a little doubtful of how devId is being handled.

                        var devId = vDevId + separ + 'DS'; 
                        
                        not sure if it requires the "DS" suffix.
                        
                        
                        1 Reply Last reply
                        0
                        • akbooerA Offline
                          akbooerA Offline
                          akbooer
                          wrote on last edited by
                          #12

                          Unless you changed something really drastic, the fact that the values are not appearing in the raw zway_xxx variables indicates that they are not being sent correctly from the actual ZWay system.

                          1 Reply Last reply
                          0
                          • DesTD Offline
                            DesTD Offline
                            DesT
                            wrote on last edited by
                            #13

                            @ronluna I'm having also a bunch of Leviton scene controller everywhere and can't use them with zwave+openLuup!

                            Did you make some progress since October ?

                            1 Reply Last reply
                            0
                            • R Offline
                              R Offline
                              ronluna
                              wrote on last edited by ronluna
                              #14

                              I did, I will explain in detail in a little bit once I get to the computer.

                              1 Reply Last reply
                              0
                              • R Offline
                                R Offline
                                ronluna
                                wrote on last edited by
                                #15

                                Most scene controllers behave differently. I don't have a Leviton scene controller in my network. Although I've read they are a little easier to properly manage them as they report the indicator status of each button individually (Cooper RFWC5 does not whichi is what I have) . So I'm assuming Z-way has created 5 toggle switches in your Z-Way Automation API (1 for each LED button of your Leviton scene controller ). If that's the case there then the missing piece for your environment would be for the openluup Z-Way plugin to track the status of those variable (The toggle switches for each indicator button on your leviton scene controller) .

                                Can you share an screenshot of all the variable the openluup z-way plugin is reading for your Leviton scene controller?

                                Currently L_Zway2.lua is only updating metrics.level (updateChildren function #1649) and is not tracking all the z-way classes. so you will need to add support for the missing classes for your scene controller and update the "updateChildren function" accordingly inside L_Zway2.lua

                                1 Reply Last reply
                                0
                                • akbooerA Offline
                                  akbooerA Offline
                                  akbooer
                                  wrote on last edited by
                                  #16

                                  When you find out what’s missing, I’ll happily put it into the baseline. As you say, scene controllers vary wildly.

                                  1 Reply Last reply
                                  0
                                  • R Offline
                                    R Offline
                                    ronluna
                                    wrote on last edited by
                                    #17

                                    @akbooer I have not share what to modify on L_Zway2.lua because I'm not sure about the changes I've made on the Z-way automation module. I'll continue playing with it and report back in a couple of days.

                                    1 Reply Last reply
                                    0
                                    • DesTD Offline
                                      DesTD Offline
                                      DesT
                                      wrote on last edited by
                                      #18

                                      @ronluna that's the model I have
                                      https://store.leviton.com/collections/z-wave/products/vizia-rf-4-button-remote-scene-controller-vrcs4-m0z?variant=33666558595

                                      I'm trying to make it work properly on zway first, 'cause right now it not appearing under openLuup

                                      1 Reply Last reply
                                      1
                                      • DesTD Offline
                                        DesTD Offline
                                        DesT
                                        wrote on last edited by
                                        #19

                                        @ronluna @akbooer

                                        Done re-adding the device to zway correctly... not if I'm playing with one of them in the hallway, I got this in the openLuup log...

                                        2020-12-28 13:39:26.931 luup.variable_set:: 31940.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 4 now: 3 #hooks:0
                                        2020-12-28 13:39:26.932 luup.variable_set:: 31940.urn:micasaverde-com:serviceId:SceneController1.LastSceneTime was: 1609180558 now: 1609180766 #hooks:0

                                        2020-12-28 13:39:38.712 luup.variable_set:: 31940.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 3 now: 1 #hooks:0
                                        2020-12-28 13:39:38.713 luup.variable_set:: 31940.urn:micasaverde-com:serviceId:SceneController1.LastSceneTime was: 1609180766 now: 1609180778 #hooks:0

                                        2020-12-28 13:39:53.350 luup.variable_set:: 31940.urn:micasaverde-com:serviceId:SceneController1.sl_SceneActivated was: 1 now: #hooks:0
                                        2020-12-28 13:39:53.351 luup.variable_set:: 31940.urn:micasaverde-com:serviceId:SceneController1.LastSceneTime was: 1609180778 now: 1609180793 #hooks:0

                                        What I did, I click on number 3 (ON), then number 1 (ON), then number 1 again (OFF)

                                        The other thing, openLuup is not getting the "right" device name, sometime it use one "child" instead of the main device.

                                        So I think the best way to handle that under openLuup will be to have a scene that run when sl_SceneActivated "changed" and do some "IF = 1 then, IF = 2 then..... "

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


                                        Recent Topics

                                        • Advice reqeusted to migrate MSR from Bare Metal to Container
                                          T
                                          tamorgen
                                          0
                                          5
                                          43

                                        • Reactor (Multi-System/Multi-Hub) Announcements
                                          toggledbitsT
                                          toggledbits
                                          5
                                          122
                                          35.4k

                                        • Z-Wave Future....
                                          CatmanV2C
                                          CatmanV2
                                          0
                                          5
                                          131

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

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

                                        • Disaster recovery and virtualisation
                                          CatmanV2C
                                          CatmanV2
                                          0
                                          5
                                          662

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

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

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

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

                                        • Need help reducing false positive notifications
                                          T
                                          tamorgen
                                          0
                                          7
                                          520
                                        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