11-25-2018, 04:33 PM
Yes that's how I added the lights, through the client side driver. Id's are correct.
Lutron Caseta & Zwave Issues
|
11-25-2018, 04:33 PM
Yes that's how I added the lights, through the client side driver. Id's are correct.
11-25-2018, 05:04 PM
Well, I'm at a loss then. The fact that it's not responding to the ping is already suspicious and now it's not responding to field writes either. Have you tried more than one light? Just to make sure? Or some of the buttons maybe? Is everything failing?
You might have to port forward it for me so that I can try it from here and see what is going on, because something just doesn't seem kosher with it.
Dean Roddey
Explorans limites defectum
12-02-2018, 05:47 AM
Let me know what you need from me to get the lights working
Here is what it looks like loaded
emailed some pics
Here is what it looks like loaded
12-02-2018, 10:11 AM
I think we are getting to the point where you are going to need to port forward so I can connect to it. But, as one last attempt at remote diagnosis, I've attached one where I just doubled the time the driver will wait for all msgs. Let's see if maybe yours is just really slow to respond or something perhaps.
Dean Roddey
Explorans limites defectum
12-02-2018, 02:07 PM
ok will try and let you know
12-02-2018, 05:14 PM
didn't work
12-02-2018, 05:35 PM
OK, it's just not responding. I'm not sure what I'll be able to figure out even if I connect to it. Unless there is something obvious, like you set up the wrong port or the username/password is not right or its IP has changed, I can't see what I could do since it's not going to respond to me either most likely. But at least I guess I can make sure if it's really not responding vs. if it's getting garbage.
Of course one difference is that the Caseta doesn't allow us to disable prompts. So it is always spitting out command line prompts as though someone were typing in messages and need to be prompted. It's possible that is confusing us somehow. That I could see if I connected to it. Also it's just a telnet connection, which means it's simple text format. You can get a terminal program and connect to it on port 23 and just type in commands. Set it up to do CR/LF type line endings (carriage return, line feed). When you connect to the Caseta it should prompt you for a user name and password, enter those, then you can enter commands and see the responses. Try something like: @PING and hit enter and see if it responds. If you can't get it to respond to a terminal program, it'll never respond to the driver. There are various query msgs you can send. So get a light status would be: ?DEVICE, [id], [num], 14 And hit return, where [id] is the device's integration id, and [num] is the device's number. 14 is the command for read a light status. You should also be able to do: ?HELP and hit return to get a list of all of the commands.
Dean Roddey
Explorans limites defectum
12-09-2018, 06:26 AM
ok been going through the set up for the driver, password and login, changed password. Same results, so I input fake name and password and the driver loaded and said it was connected, but wouldn't respond to commands, and lost its connection. I would think that it should not let the driver connect at all?
|
« Next Oldest | Next Newest »
|