Z-Wave Future....

[powisquare]

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.

[akbooer]

These used to work very well with Vera, I found. Haven’t tried with ZWay, but I could give it a go, if that would help.

[powisquare]

Would very much appreciate it!

[CatmanV2]

I have mostly those around here. They have no issues at all.

The setting of parameters in Z-way has always caused me challenges (as a human!) but again once having got them, no issues.

I assume they are going on and off OK when commanded manually?

C

[akbooer]

Just added one. 100% interview OK. Works fine in openLuup/Zway...

[powisquare]

Yes indeed they do. It seems to be the reporting back to controller is not quite working yet when switched by the thermostat. I associated them in Group 2 with the thermostat and it seems to control them nicely. Just unable to know whether they are on or off. If switched on or off in the gui they work fine.

Mine are all interviewed 100% also but does it need an association command class to do what I think it needs to do? (lifeline to controller?)

[akbooer]

Ah, I see. Is there anything I can try further to help, then?

[powisquare]

Thank you very much - much appreciated. I'll try tinkering some more.

[powisquare]

It would appear some scripting is needed to get these working ... definately getting in to the deeper end now. The switch does not support associations but vera may have had some sort of workaround. Is there a guide on how to create modules? This would need to go in it ...

function Fix_TKB_TZ68(deviceId) {
var dev = zway.devices[deviceId];
dev.data.nodeInfoFrame.bind(function(type) {
if (type == 0x41 /* Updated | PhantomUpdate */) {
dev.SwitchBinary.Get();
}
});
}

taken from https://forum.z-wave.me/viewtopic.php?f=3422&t=20621

[akbooer]

I've hardly ever (in fact, only once) found a personal need for using device associations (aside from Group 1 controller associations, which are, on the whole automatic.)

What's your use case? Why not just do this with a scene?

[rafale77]

So I went through my entire device list to find only one type of devices I own which does not support association. They are unfortunately not devices which can be manually actuated and z-way is the only one actuating them so they do not require instant status as z-way just polls them after every actuation to make sure that the device reached its target status (in my case they are vents which act like dimmers)

If these TKB switches don't have a lifeline association then they may not support instant status at all and it could be that the vera was just making status equal to the target every time they were actuated? If that's the case then a small plugin on z-way could probably fix this: I modified Niffler for my locks because of a delayed status report from my locks but it could apply to other zway devices as well. The problem I had was that z-way was polling the device too quickly after the lock actuation command and reporting back the wrong status.

GitHub - rafale77/Niffler: Workaround for Z-Wave devices that does not send unsolicited reports

Workaround for Z-Wave devices that does not send unsolicited reports - rafale77/Niffler

@CatmanV2 however appears to say that his work so I am wondering if it is a configuration/interview issue still or maybe a downrev firmware on your devices.

[akbooer]

IF I understand this, it's to do with additional, Group 2, ..., associations. The instant status works just fine.

[powisquare]

Thermostat controls 2 x TKBs turning on/off heaters via association (have tried Group 2 & 1). That works and have reactor contolling it. UI however does not know the switches have been turned on by thermostat. The workaround seems such that when the switch issues its nif on changing state (instead of a status report), controller will request status report on receiving nif.

[rafale77]

Yep then use niffler. So I misunderstood the problem, sorry but the solution is the same...

[powisquare]

Omg - just caught up reading Niffler. You guys rock - but I need a drink first. Cheers !

[powisquare]

Installed and appears to be functioning but status of added devices still not changing. Would it matter I have a UZB and not Razberry?

[2021-03-06 09:17:19.958] [I] [core] Niffler: stop() called
[2021-03-06 09:17:19.959] [I] [core] Niffler: unNiffling existing devices
[2021-03-06 09:17:19.961] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_32-0-37
[2021-03-06 09:17:19.961] [I] [core] Niffler: unNiffling ZWayVDev_zway_32-0-37
[2021-03-06 09:17:19.962] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_43-0-37
[2021-03-06 09:17:19.963] [I] [core] Niffler: unNiffling ZWayVDev_zway_43-0-37
[2021-03-06 09:17:19.969] [I] [core] --- Stopping module Niffler
[2021-03-06 09:17:19.973] [I] [core] --- Starting module Niffler
[2021-03-06 09:17:20.053] [I] [core] Niffler: init
[2021-03-06 09:17:20.057] [I] [core] Niffler: Niffling device ZWayVDev_zway_32-0-37
[2021-03-06 09:17:20.058] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_32-0-37
[2021-03-06 09:17:20.059] [I] [core] Niffler: Niffling device ZWayVDev_zway_43-0-37
[2021-03-06 09:17:20.059] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_43-0-37
[2021-03-06 09:17:20.060] [I] [core] Niffler: Niffling device ZWayVDev_zway_14-0-37
[2021-03-06 09:17:20.060] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_14-0-37
[2021-03-06 09:17:20.060] [I] [core] Niffler: Niffling device ZWayVDev_zway_8-0-37
[2021-03-06 09:17:20.060] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_8-0-37
[2021-03-06 09:17:20.060] [I] [core] Niffler: Niffling device ZWayVDev_zway_28-0-37
[2021-03-06 09:17:20.060] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_28-0-37
[2021-03-06 09:17:20.061] [I] [core] Niffler: Niffling device ZWayVDev_zway_13-0-37
[2021-03-06 09:17:20.061] [I] [core] Niffler: getdeviceindex: ZWayVDev_zway_13-0-37
[2021-03-06 09:17:28.249] [I] [zway] Adding job: Get background noise level
[2021-03-06 09:17:28.258] [D] [zway] SENDING: ( 01 03 00 3B C7 )
[2021-03-06 09:17:28.260] [D] [zway] RECEIVED ACK
[2021-03-06 09:17:28.268] [D] [zway] RECEIVED: ( 01 05 01 3B A7 A5 C2 )
[2021-03-06 09:17:28.268] [D] [zway] SENT ACK
[2021-03-06 09:17:28.268] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel1 = 167 (0x000000a7)
[2021-03-06 09:17:28.268] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel2 = 165 (0x000000a5)
[2021-03-06 09:17:28.269] [D] [zway] SETDATA controller.data.statistics.backgroundRSSI.channel3 = 127 (0x0000007f)
[2021-03-06 09:17:28.269] [I] [zway] Job 0x3b (Get background noise level): RSSI Ch#1: -91 dBm, Ch#2: -91 dBm, Ch#3: invalid
[2021-03-06 09:17:28.269] [D] [zway] Job 0x3b (Get background noise level): success
[2021-03-06 09:17:28.269] [I] [zway] Removing job: Get background noise level

[akbooer]

@powisquare said in Lifeline/TKB switches:

Would it matter I have a UZB and not Razberry?

Should not make any difference, AFAIK.

[rafale77]

As @akbooer said, that should not make any difference. I guess I am still not completely clear on how your device is setup. Are you saying you have already the lifeline association setup with the z-way controller and that you are not seeing status update when another associated device actuates the switch? Or is it that you can't setup any associations?

[powisquare]

The switch is unable to set up associations and has no lifeline (the thermostat can make associations and the switch is in the thermostat's group however if that makes sense).

[rafale77]

It does... But other people appear to be able to see the lifeline association on the switch it seems? Is your z-way node ID number "1"? I have seen devices having their lifeline hardcoded in their firmwares.
There is always a possible workaround. I could even give a scene code to get zway to poll the switch status when the thermostat state changes for example. Niffler probably won't work because zway is not even receiving any signal from the switch that anything has changed.
Otherwise it seems like you either have an older firmware on your switch or they are not fully interviewed but you seem to have already explored that.