Z-wave & oomi (aetoec) plug issues

keith_munro · March 16, 2020, 3:09am

@Wounded - Thankyou ! That would explain the not setting 90, I'll spin them up this arvo and unlock them

keith_munro · March 18, 2020, 1:05am

interesting the brightness on this one, 84 has a default value of 3289650 and does not like percentages, think this might be a v7 with an au plug. Was able to dim it by making it 1/4 the value

saxnix · March 18, 2020, 2:27am

How did you do this Keith? Would there be any way to have the light off when the plug is in use?

Wounded · March 18, 2020, 3:02am

@saxnix, you might want to use Momentary mode. The manual says that the light will turn off after 5 seconds.
Parameters 81, 83 and 84 control the LED mode, color and brightness.
81 is the mode: 0 = Energy mode (default), 1 = Momentary mode and 2 = Night light mode
83 is the RGB value for Night light mode. Red + Green + Blue. Default is Red = x1B, Green=x14, Blue=x1B. 1B141B Hex is 1774619 decimal.
84 is the LED brightness level in Energy or Momentary modes. Default is Green = x32, Yellow=x32, Red=x32. 323232 Hex is 3289650 decimal.

saxnix · March 18, 2020, 3:18am

Ha ha, that's all over my head. . No clue what any of that means. Not a programmer, just fumbling my way through.

keith_munro · March 18, 2020, 4:29am

@saxnix direct message me, tell me what you want it to do and I'll play and the send back instructions.

njanda · March 20, 2020, 2:46am

Hey Keith,
do your Oomi's show more Clusters than this...

or does that only become visible AFTER unlocking them ??

Wounded · March 20, 2020, 3:21am

Hi @njanda. Here are the clusters for mine:

njanda · March 20, 2020, 3:39am

yeah that's what I expected to see.
Thx

njanda · March 20, 2020, 4:12am

I wonder if being "locked' alters the Device Type, as yours are different also ?
Same manufacturer and Device ID

keith_munro · March 20, 2020, 7:06am

I don't have a pre-unlock screenshot and cannot tell from the logs but mine now has
inClusters: 0x5E,0x25,0x26,0x33,0x70,0x27,0x32,0x81,0x85,0x59,0x72,0x86,0x7A,0x73

Wounded · March 20, 2020, 3:03pm

@njanda. Mine were locked when I added them to Hubitat. It is more likely that the different Device Type is due to country or manufacturing versions.

njanda · March 21, 2020, 5:00am

@keith_munro, @Wounded - I excluded and then Included and it got associated correctly this time so now everything seems to be working as expected.
I've also unlocked the device using the Basic Zwave tool
It is now showing...

Thanks guys

keith_munro · March 21, 2020, 6:59am

@njanda - I need to go check mine again, output using aeotec 6 driver device type and manufacturer seem to be different on yours between screenshots

deviceType: 515
inClusters: 0x5E,0x25,0x26,0x33,0x70,0x27,0x32,0x81,0x85,0x59,0x72,0x86,0x7A,0x73
outClusters: 0x5A,0x82
deviceId: 96
manufacturer: 362

I've got full config control so they are definately unlocked
did you unlock then exclude and add them again ?

njanda · March 21, 2020, 7:06am

G'day Keith, I Excluded then Included and then unlocked

njanda · March 21, 2020, 9:26am

I'm going to have a play and see if @srwhite's Zwave Repeater Driver could be used to check routing through these Oomi devices.

github.com

shackrat/SmartThings-by-Shackrat/blob/master/devicetypes/shackrat/iris-zwave-repeater.src/iris-zwave-repeater.groovy

/**
 *  Copyright 2017 Steve White
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */
metadata
{
	definition (name: "Iris Z-Wave Repeater", namespace: "shackrat", author: "Steve White")
	{
		capability "Health Check"
		capability "Polling"
		capability "Refresh"

This file has been truncated. show original

keith_munro · March 22, 2020, 10:54pm

Let me know how you go with that please @njanda

njanda · March 25, 2020, 3:20am

Hey Keith,
It looks like the Oomi's are doing their thing;
I loaded up @srwhite's Iris Zwave Repeater driver and here's what I got .........

#### Current States

*** lastMsgRcvd : 2020-03-25 14:12:03: POWER LEVEL NODE TEST REPORT V1**
*** lastTest : SUCCESS 30 of 30 frames received.**
*** status : online**

I then set all logging to ON.
Pressed "interrogate Device" and got....

dev:20212020-03-25 02:16:51.217 pm infoDevice is online

dev:20212020-03-25 02:16:51.197 pm debugMANUFACTURER SPECIFIC V2: Manufacturer ID: 016A, Manufacturer Name: Fantem, Product Type ID: 0203, Product ID: 0060

dev:20212020-03-25 02:16:51.190 pm debugParsing zw device: 62, command: 7205, payload: 01 6A 02 03 00 60 , isMulticast: false

dev:20212020-03-25 02:16:51.043 pm traceSending command... ManufacturerSpecificGet()

dev:20212020-03-25 02:16:51.040 pm debugQuerying device for manufacturerSpecificV2 information...

dev:20212020-03-25 02:16:02.731 pm traceDevice Interrogation: Phase 0 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:57.798 pm infoDevice is online

dev:20212020-03-25 02:15:57.791 pm debugASSOCIATION GROUP REPORT V2: Oomi-2 - WiFi controller in Group #1 with nodes: [1]

dev:20212020-03-25 02:15:57.787 pm debugParsing zw device: 62, command: 8503, payload: 01 05 00 01 , isMulticast: false

dev:20212020-03-25 02:15:57.739 pm traceDevice Interrogation: Phase 6 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:57.709 pm traceSending command... AssociationGet(groupingIdentifier:1)

dev:20212020-03-25 02:15:52.809 pm infoDevice is online

dev:20212020-03-25 02:15:52.803 pm debugASSOCIATION GROUP NAME REPORT V1: Oomi-2 - WiFi controller belongs to group Lifeline

dev:20212020-03-25 02:15:52.798 pm traceReceived: AssociationGroupNameReport(groupingIdentifier:1, lengthOfName:8, name:[76, 105, 102, 101, 108, 105, 110, 101])

dev:20212020-03-25 02:15:52.776 pm debugParsing zw device: 62, command: 5902, payload: 01 08 4C 69 66 65 6C 69 6E 65 , isMulticast: false

dev:20212020-03-25 02:15:52.722 pm traceDevice Interrogation: Phase 5 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:52.689 pm traceSending command... AssociationGroupNameGet(groupingIdentifier:1)

dev:20212020-03-25 02:15:47.901 pm infoDevice is online

dev:20212020-03-25 02:15:47.882 pm infoDevice is online

dev:20212020-03-25 02:15:47.872 pm debugMANUFACTURER SPECIFIC V2: Manufacturer ID: 016A, Manufacturer Name: Fantem, Product Type ID: 0203, Product ID: 0060

dev:20212020-03-25 02:15:47.792 pm debugParsing zw device: 62, command: 7205, payload: 01 6A 02 03 00 60 , isMulticast: false

dev:20212020-03-25 02:15:47.763 pm debugMANUFACTURER SPECIFIC V2: Manufacturer ID: 016A, Manufacturer Name: Fantem, Product Type ID: 0203, Product ID: 0060

dev:20212020-03-25 02:15:47.754 pm debugParsing zw device: 62, command: 7205, payload: 01 6A 02 03 00 60 , isMulticast: false

dev:20212020-03-25 02:15:47.705 pm traceDevice Interrogation: Phase 4 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:47.668 pm traceSending command... ManufacturerSpecificGet()

dev:20212020-03-25 02:15:42.861 pm infoDevice is online

dev:20212020-03-25 02:15:42.842 pm debugFIRMWARE METADATA REPORT V1: Oomi-2 - WiFi controller is running firmware ID: 0000 with checksum: 97E9

dev:20212020-03-25 02:15:42.839 pm debugParsing zw device: 62, command: 7A02, payload: 01 6A 00 00 97 E9 , isMulticast: false

dev:20212020-03-25 02:15:42.795 pm infoDevice is online

dev:20212020-03-25 02:15:42.770 pm debugFIRMWARE METADATA REPORT V1: Oomi-2 - WiFi controller is running firmware ID: 0000 with checksum: 97E9

dev:20212020-03-25 02:15:42.765 pm debugParsing zw device: 62, command: 7A02, payload: 01 6A 00 00 97 E9 , isMulticast: false

dev:20212020-03-25 02:15:42.694 pm traceDevice Interrogation: Phase 3 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:42.646 pm traceSending command... FirmwareMdGet()

dev:20212020-03-25 02:15:37.800 pm infoDevice is online

dev:20212020-03-25 02:15:37.755 pm debugVERSION REPORT V1: Oomi-2 - WiFi controller is running firmware version: 1.5, Z-Wave version: 4.5, Library type: 3

dev:20212020-03-25 02:15:37.751 pm debugParsing zw device: 62, command: 8612, payload: 03 04 05 01 05 60 00 , isMulticast: false

dev:20212020-03-25 02:15:37.655 pm traceDevice Interrogation: Phase 2 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:37.621 pm traceSending command... VersionGet()

dev:20212020-03-25 02:15:32.732 pm infoDevice is online

dev:20212020-03-25 02:15:32.695 pm debugPOWER LEVEL REPORT V1: Transmit power for Oomi-2 - WiFi controller is NOMINAL.

dev:20212020-03-25 02:15:32.687 pm debugParsing zw device: 62, command: 7303, payload: 00 00 , isMulticast: false

dev:20212020-03-25 02:15:32.623 pm traceDevice Interrogation: Phase 1 of 6; Attempt 1 of 3...

dev:20212020-03-25 02:15:32.570 pm traceSending command... PowerlevelGet()

dev:20212020-03-25 02:15:32.537 pm traceInterrogating device...

I think it's all good.

njanda · March 25, 2020, 3:53am

As an addendum or follow up;
I've configured one of my Oomi's as a power switch for my WiFi router.
Using the "HTTP Present" App from @jwetzel1492, it pings a WiFi device I have.

See more info HERE

system · September 22, 2022, 5:48pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.