Closed brianrogers closed 6 years ago
CC @gurumitts It seems a version bump in setup.py was missed when releasing 0.2.4.
Hey I just fixed the version # bump. Can you try it again?
And one more thing to try: The paramiko dependency requires additional libaries to be available on the system. If the version bump does not fix ths issue can you sudo apt-get install build-essential libssl-dev libffi-dev python-dev
. Additional information can be found here: http://stackoverflow.com/questions/22073516/failed-to-install-python-cryptography-package-with-pip-and-setup-py
thanks!! I'll try this tonight and report back.
yes, this seems to have fixed the installation process. My issue now is that my bridge is refusing the telnet connection, but that's my problem to work through (I just realized I don't have a PRO bridge yet). Thanks for the fix!
It's looking like a connection is never established. HA log shows it's "taking more than 10 seconds" message for the component and nothing else. I have the SmartBridge Pro and I've noticed a peculiarity in that it rejects the first attempt at login from a telnet client. The second attempts works with the same credentials. Have you seen this and do you think this could be the issue with the component connecting?
I just got my pro bridge today so I'll setup to test and see if I also have connectivity issues tonight.
I've broken it apart to just a test script that leverages the SmartBridge object and I'm able to connect. However, when it's in an HA component it hangs and doesn't seem to call the setup method.
FWIW, mine connected immediately and the light switches just appeared in my dashboard. There was nothing in the log saying there was a failed connection or anything for that component. YMMV though...
What do you see in the logs on a successful connection?
He guys, only if the connection to the smartbridge fails will anything appear in the logs. Most of the other log statements are set to debug.
The setup method is called by HA. Can you share the relevant entries from your configuration.yaml?
BTW... When running on my RPI I get the "taking longer than 10 seconds" pretty much all the time. That first ssh connection is very expensive.
ok, I'm using an RPI as well. My config is passing the validation check in the component so I think everything is ok there. I'm just not seeing my device show up as a light ever.
Here is my integration report from the bridge ...
{
"LIPIdList" : {
"Devices" : [
{
"ID" : 1,
"Name" : "Smart Bridge",
"Buttons" : [
{
"Name" : "Button 1",
"Number" : 1
},
{
"Name" : "Button 2",
"Number" : 2
},
{
"Name" : "Button 3",
"Number" : 3
},
{
"Name" : "Button 4",
"Number" : 4
},
{
"Name" : "Button 5",
"Number" : 5
},
{
"Name" : "Button 6",
"Number" : 6
},
{
"Name" : "Button 7",
"Number" : 7
},
{
"Name" : "Button 8",
"Number" : 8
},
{
"Name" : "Button 9",
"Number" : 9
},
{
"Name" : "Button 10",
"Number" : 10
},
{
"Name" : "Button 11",
"Number" : 11
},
{
"Name" : "Button 12",
"Number" : 12
},
{
"Name" : "Button 13",
"Number" : 13
},
{
"Name" : "Button 14",
"Number" : 14
},
{
"Name" : "Button 15",
"Number" : 15
},
{
"Name" : "Button 16",
"Number" : 16
},
{
"Name" : "Button 17",
"Number" : 17
},
{
"Name" : "Button 18",
"Number" : 18
},
{
"Name" : "Button 19",
"Number" : 19
},
{
"Name" : "Button 20",
"Number" : 20
},
{
"Name" : "Button 21",
"Number" : 21
},
{
"Name" : "Button 22",
"Number" : 22
},
{
"Name" : "Button 23",
"Number" : 23
},
{
"Name" : "Button 24",
"Number" : 24
},
{
"Name" : "Button 25",
"Number" : 25
},
{
"Name" : "Button 26",
"Number" : 26
},
{
"Name" : "Button 27",
"Number" : 27
},
{
"Name" : "Button 28",
"Number" : 28
},
{
"Name" : "Button 29",
"Number" : 29
},
{
"Name" : "Button 30",
"Number" : 30
},
{
"Name" : "Button 31",
"Number" : 31
},
{
"Name" : "Button 32",
"Number" : 32
},
{
"Name" : "Button 33",
"Number" : 33
},
{
"Name" : "Button 34",
"Number" : 34
},
{
"Name" : "Button 35",
"Number" : 35
},
{
"Name" : "Button 36",
"Number" : 36
},
{
"Name" : "Button 37",
"Number" : 37
},
{
"Name" : "Button 38",
"Number" : 38
},
{
"Name" : "Button 39",
"Number" : 39
},
{
"Name" : "Button 40",
"Number" : 40
},
{
"Name" : "Button 41",
"Number" : 41
},
{
"Name" : "Button 42",
"Number" : 42
},
{
"Name" : "Button 43",
"Number" : 43
},
{
"Name" : "Button 44",
"Number" : 44
},
{
"Name" : "Button 45",
"Number" : 45
},
{
"Name" : "Button 46",
"Number" : 46
},
{
"Name" : "Button 47",
"Number" : 47
},
{
"Name" : "Button 48",
"Number" : 48
},
{
"Name" : "Button 49",
"Number" : 49
},
{
"Name" : "Button 50",
"Number" : 50
},
{
"Name" : "Button 51",
"Number" : 51
},
{
"Name" : "Button 52",
"Number" : 52
},
{
"Name" : "Button 53",
"Number" : 53
},
{
"Name" : "Button 54",
"Number" : 54
},
{
"Name" : "Button 55",
"Number" : 55
},
{
"Name" : "Button 56",
"Number" : 56
},
{
"Name" : "Button 57",
"Number" : 57
},
{
"Name" : "Button 58",
"Number" : 58
},
{
"Name" : "Button 59",
"Number" : 59
},
{
"Name" : "Button 60",
"Number" : 60
},
{
"Name" : "Button 61",
"Number" : 61
},
{
"Name" : "Button 62",
"Number" : 62
},
{
"Name" : "Button 63",
"Number" : 63
},
{
"Name" : "Button 64",
"Number" : 64
},
{
"Name" : "Button 65",
"Number" : 65
},
{
"Name" : "Button 66",
"Number" : 66
},
{
"Name" : "Button 67",
"Number" : 67
},
{
"Name" : "Button 68",
"Number" : 68
},
{
"Name" : "Button 69",
"Number" : 69
},
{
"Name" : "Button 70",
"Number" : 70
},
{
"Name" : "Button 71",
"Number" : 71
},
{
"Name" : "Button 72",
"Number" : 72
},
{
"Name" : "Button 73",
"Number" : 73
},
{
"Name" : "Button 74",
"Number" : 74
},
{
"Name" : "Button 75",
"Number" : 75
},
{
"Name" : "Button 76",
"Number" : 76
},
{
"Name" : "Button 77",
"Number" : 77
},
{
"Name" : "Button 78",
"Number" : 78
},
{
"Name" : "Button 79",
"Number" : 79
},
{
"Name" : "Button 80",
"Number" : 80
},
{
"Name" : "Button 81",
"Number" : 81
},
{
"Name" : "Button 82",
"Number" : 82
},
{
"Name" : "Button 83",
"Number" : 83
},
{
"Name" : "Button 84",
"Number" : 84
},
{
"Name" : "Button 85",
"Number" : 85
},
{
"Name" : "Button 86",
"Number" : 86
},
{
"Name" : "Button 87",
"Number" : 87
},
{
"Name" : "Button 88",
"Number" : 88
},
{
"Name" : "Button 89",
"Number" : 89
},
{
"Name" : "Button 90",
"Number" : 90
},
{
"Name" : "Button 91",
"Number" : 91
},
{
"Name" : "Button 92",
"Number" : 92
},
{
"Name" : "Button 93",
"Number" : 93
},
{
"Name" : "Button 94",
"Number" : 94
},
{
"Name" : "Button 95",
"Number" : 95
},
{
"Name" : "Button 96",
"Number" : 96
},
{
"Name" : "Button 97",
"Number" : 97
},
{
"Name" : "Button 98",
"Number" : 98
},
{
"Name" : "Button 99",
"Number" : 99
},
{
"Name" : "Button 100",
"Number" : 100
}
]
},
{
"ID" : 3,
"Name" : "Lutron Plug In Lamp Remote 1",
"Buttons" : [
{
"Number" : 2
},
{
"Number" : 3
},
{
"Number" : 4
},
{
"Number" : 5
},
{
"Number" : 6
}
]
}
],
"Zones" : [
{
"ID" : 2,
"Name" : "Lutron Plug In Lamp"
}
]
}
}
Oh. I think I know the issue. What is the actual lutron device you are using in your home? Right now the Hass component only supports "wall dimmer" and "wall switch" devices. We can easily add support for the "plug" if that is what you are using.
Oh, I see. It's the Caseta Wireless Plug-in lamp dimmer with remote (part number PD-3CPL). It shows up in the device list from the ssh call as "PlugInDimmer" and I see now that your setup_platform method for the light only includes "WallDimmer".
Thanks... I'll have the code updated this evening. Just so I don't get it wrong. Can you confirm that the ssh call returns "PlugInDimmer" for your device? Also should this be setup as a 'light' in HA so you have the dimming controls? Pretty sure the answer is yes.
Yes, it's "PlugInDimmer" and I hand modded the code to test to do this which works and shows my device in HA....
light_devices = bridge.get_devices_by_type("PlugInDimmer")
for light_device in light_devices:
dev = LutronCasetaLight(light_device, bridge)
devs.append(dev)
Wasn't sure if you wanted to modify your SmartBridge class and update the get_devices_by_type to take an array or not so I didn't commit any updates.
Yes... I was thinking that I would mod the smartbridge class and bump the version number. There are a couple of additional fixes to pick up anyway. Thanks for reporting the issue.
Great! Just a heads up, even with the version 24 bump it appears that the apt-get installs still need to be performed before HA tries to do the pip install. I wasn't clear on if you were saying those needed to be done or not. I have a Docker container running all this for development so I am regularly restarting from a clean state.
Yea.. I thought so. I'll update the docs to state as much.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Any chance of getting energy consumption from Lutron?
@brianrogers is this still an issue?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍
**Home Assistant release (
hass --version
):0.41.0**Python release (
python3 --version
):3.4.2**Component/platform:lutron_caseta
Description of problem: 17-03-27 00:51:18 ERROR (MainThread) [homeassistant.setup] Not initializing lutron_caseta because could not install dependency https://github.com/gurumitts/pylutron-caseta/archive/v0.2.4.zip#pylutron-caseta==v0.2.4 17-03-27 00:51:18 ERROR (MainThread) [homeassistant.setup] Setup failed for lutron_caseta: Could not install all requirements.
Expected: Expected component to install all deps properly.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Additional info: Hassbian image on RaspberryPi 3. Manually upgraded via website instructions.
I'm not seeing any permissions errors and the upgrade was done from within the environment as directed.