org.openhab.binding.zwave
org.openhab.binding.zwave copied to clipboard
Aeon Labs DSC11-ZWUS Z wave Smart Strip, missing endpoints (no data on channel 5 and 6)
- OH2 Version: 2.3.0-SNAPSHOT (current)
- Binding Version: 2.3.0.201802081624
If the problem is associated with a device, please provide the following -:
- Device name: Aeon Labs DSC11-ZWUS
- Device version: 1
- Link to database: here
- XML - here.
Log will be provided if needed.
The problem with the device is that endpoints 5 and 6 are missing, so device does not report power consumption for sockets 5 and 6. Channels are there, but I wasn't able to get any data from them. It seems there was a 'hack' to add those endpoints in OH1 binding (worked well there).
Thanks a lot for looking into this!
Please provide a logfile showing what data is received from the device for these endpoints.
2018-02-20 19:00:19.966 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint = 1, calling handleApplicationCommandRequest.
2018-02-20 19:00:20.028 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint = 2, calling handleApplicationCommandRequest.
2018-02-20 19:00:20.168 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint = 3, calling handleApplicationCommandRequest.
2018-02-20 19:00:20.227 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint = 4, calling handleApplicationCommandRequest.
2018-02-20 19:00:20.337 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint 5 not found. Cannot set command classes.
2018-02-20 19:00:20.428 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint 6 not found. Cannot set command classes.
It seems no data is received from device as those endpoints do not exist. I think this commit https://github.com/openhab/openhab1-addons/pull/2704/commits/5f1b4fb721c9cd8aad7418076a50bc51b13f8c11 fixed it for OH1.
Also originally it was discussed here
I'm also attaching the the DEBUG log for NODE 12 (which is the device in question) node12.log
Please provide an unfiltered logfile showing what data is received from the device for these endpoints during initialisation.
Here you are. Please let me know if that is what you're looking for. I can post full debug openhab startup log but that is >60M
This is a debug log for ZWave from the moment of startup (after Node 12 was deleted, to re-query)
P.s. thank you for your patience, newbie in ZWave :)
All outlets report for me. Here is my item setup:
Number SmartSwitch_01_Power_0 "PowerStrip1 Master Power [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts" }
Number SmartSwitch_01_Power_1 "PowerStrip1 Power 1 [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts3" }
Number SmartSwitch_01_Power_2 "PowerStrip1 Power 2 [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts4" }
Number SmartSwitch_01_Power_3 "PowerStrip1 Power 3 [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts5" }
Number SmartSwitch_01_Power_4 "PowerStrip1 Power 4 [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts6" }
Number SmartSwitch_01_Power_A "PowerStrip1 Power A [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts1" }
Number SmartSwitch_01_Power_B "PowerStrip1 Power B [%.2f W]" {channel="zwave:device:zwave:node160:meter_watts2" }
@omatzyo interesting. My setup is virtually identical
Number pwr_W_zTable <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts"}
Number pwr_W_zTable_AO1 <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts1"}
Number pwr_W_zTable_AO2 <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts2"}
Number pwr_W_zTable_s1 <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts3"}
Number pwr_W_zTable_s2 <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts4"}
Number pwr_W_zTable_s3 <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts5"}
Number pwr_W_zTable_s4 <energy> (gInflux, gTable) {channel="zwave:device:78aa85e9:node12:meter_watts6"}
Can you please share zwave configuration parameters for your device?
@cdjackson I'm unsure if this is related. But I'm unable to add the thing from Inbox to with the following error:
Thing zwave:device:512:node12 unable to be approved: Duplicate channels zwave:device:512:node12:switch_binary
I’ve been getting this same message actually since upgrading from the dev binding (which I’ve been on for months) to the snapshot this week.
New checks were recently added to esh so this is a new error that is highlighting a problem in the database for this device. It is already fixed and will be I the next update.
Sent from my iPhone
On 19 Oct 2018, at 00:49, omatzyo [email protected] wrote:
I’ve been getting this same message actually since upgrading from the dev binding (which I’ve been on for months) to the snapshot this week.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.