Page 1 of 2

No log output

PostPosted: Thu Feb 15, 2018 3:28 pm
by new2me07
I'm trying to get all this figured out as I have about 5 evolve scene controller I used to use with vera. Just a simple single gang momentary switch. Everything seems straight forward enough except the logs show nothing. I enabled logging on the Zwave interface and can see the button presses, but no button ID or anything. I can see the scene controller enabling debugging in the log, it just doesn't print anything to it.

Any ideas?


Z-Wave Scene Controller Debug logging enabled
Z-Wave Debug RCVD basicSetState: 01 09 00 04 00 29 03 20 01 FF 06
Z-Wave Debug . . basicSetState: node 041, endpoint None, value 255 (no node dispatch)

Re: No log output

PostPosted: Thu Feb 15, 2018 3:48 pm
by howartp
Hi there.

It looks like the device is sending setBasicState() commands which I've not written into the plugin - in fact I've not seen them before.

The plugin supports both Basic Scene and Central Scene commands, which are the two types of Scene commands.

I can look at Basic State commands in due course but it will be a couple of weeks at the earliest.

Peter

Re: No log output

PostPosted: Thu Feb 15, 2018 3:56 pm
by howartp
(I've just quickly looked at specs - it's using the Basic command class which wouldn't normally be used for "Scene control" as such, but I can see with this model it will be useful to operate it in this way so I'll get support added.)

Peter

Re: No log output

PostPosted: Thu Feb 15, 2018 3:58 pm
by new2me07
In case this helps this is the Zwave output when I press and hold the "up" toggle.


Z-Wave Debug RCVD dimmerLevelChangeStop: 01 08 00 04 00 29 02 26 05 FB
Z-Wave Debug . . dimmerLevelChangeStop: node 041, endpoint None
Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 29 02 20 02 FA
Z-Wave Debug . . basicGetState: node 041, endpoint None

Re: No log output

PostPosted: Thu Feb 15, 2018 3:59 pm
by new2me07
Thank you very much Sir!

Re: No log output

PostPosted: Thu Feb 15, 2018 5:16 pm
by matt (support)
Can you also re-sync it in Indigo (no debug logging needed please) and copy/paste the log results into a reply for me? I'd like to get the details on how that module is identifying itself.

Re: No log output

PostPosted: Thu Feb 15, 2018 5:53 pm
by howartp
As well as Matts request, do you know the model no and have a link to manual?

If not we’ll get it from Matts info.

If you can press each button and paste logs again that would also help.


Sent from my iPhone using Tapatalk Pro

Re: No log output

PostPosted: Mon Feb 19, 2018 6:01 pm
by new2me07
Log output from Re-sync

Z-Wave Syncing - started for "041 - Remote Switch"
Z-Wave Syncing - retrieved module neighbors list: 3, 5, 6, 7, 9, 10, 13, 14, 15, 17, 19, 21, 22, 23, 24, 26, 27, 28, 30, 31, 32, 38, 39
Z-Wave Syncing - assigning return route to "041 - Remote Switch"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Evolve - 0113, Remote Switch - 54573033
Z-Wave Syncing - retrieved protocol version 3.36, app version 5.30
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Remote Switch : -- (04 : 12 : 00, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 85v1 26v1 87v1 27v1 70v1 72v1 86v1 25v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - complete

Re: No log output

PostPosted: Mon Feb 19, 2018 6:06 pm
by new2me07
Button Press results


Up
Z-Wave Debug RCVD basicSetState: 01 09 00 04 00 29 03 20 01 FF 06
Z-Wave Debug . . basicSetState: node 041, endpoint None, value 255 (no node dispatch)

Held in up Position
Z-Wave Debug RCVD dimmerLevelChangeStart: 01 0A 00 04 00 29 04 26 04 20 63 BD
Z-Wave Debug . . dimmerLevelChangeStart: node 041, endpoint None, brightening
Z-Wave Debug RCVD dimmerLevelChangeStop: 01 08 00 04 00 29 02 26 05 FB
Z-Wave Debug . . dimmerLevelChangeStop: node 041, endpoint None
Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 29 02 20 02 FA
Z-Wave Debug . . basicGetState: node 041, endpoint None

Down
Z-Wave Debug RCVD basicSetState: 01 09 00 04 00 29 03 20 01 00 F9
Z-Wave Debug . . basicSetState: node 041, endpoint None, value 0 (no node dispatch)

Held Down
Z-Wave Debug RCVD dimmerLevelChangeStart: 01 0A 00 04 00 29 04 26 04 60 01 9F
Z-Wave Debug . . dimmerLevelChangeStart: node 041, endpoint None, dimming
Z-Wave Debug RCVD dimmerLevelChangeStop: 01 08 00 04 00 29 02 26 05 FB
Z-Wave Debug . . dimmerLevelChangeStop: node 041, endpoint None
Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 29 02 20 02 FA
Z-Wave Debug . . basicGetState: node 041, endpoint None

Re: No log output

PostPosted: Mon Feb 19, 2018 6:11 pm
by new2me07
It's an Evolve LTM-5 switch. All the manuals I found were just two pages. I don't think they will help.

Re: No log output

PostPosted: Wed Feb 28, 2018 11:03 am
by new2me07
Is there anyway to make a trigger based on the raw zwave output?

Re: No log output

PostPosted: Wed Feb 28, 2018 12:45 pm
by FlyingDiver
new2me07 wrote:
Is there anyway to make a trigger based on the raw zwave output?


Yes, there's a Z-wave trigger for matching raw output from a specific device.

Re: No log output

PostPosted: Mon Mar 05, 2018 5:04 pm
by new2me07
Every other device that seems to be the case but the Evolve Scene Switches (because they're not defined, I imagine) don't have any options available as being set up as a trigger. Any relatively easy work arounds that may work?

Re: No log output

PostPosted: Mon Mar 05, 2018 5:10 pm
by FlyingDiver
new2me07 wrote:
Every other device that seems to be the case but the Evolve Scene Switches (because they're not defined, I imagine) don't have any options available as being set up as a trigger. Any relatively easy work arounds that may work?


You sure you're looking in the right place? The trigger is "Z-Wave command received". Then after you pick the device, you want "Match Raw Packet".

Re: No log output

PostPosted: Mon Mar 05, 2018 5:43 pm
by new2me07
Yes Sir, thats exactly where. Theres simply no options available at all from those devices. All others populate with at least that option.