New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs for adding new devices #22
Comments
I don't have any docs. Are you trying to add the device to Home Assistant? If you think this thing is supposed to be ZHA compliant, we can work through figuring out why it's not working properly. If it's not ZHA compliant, I'd prefer to avoid adding special code in hass until I have a better framework in place for handling non-compliant devices. Can you send me the output of "bellows devices", and if you're doing this in Home Assistant, debug logs of the startup, and when you attempt to switch on/off? |
AFAIK it is, seems that there is support for 2 clusters missing 0x0008 and 0x0202 0x0008 is the light dimmer and 0x0202 is the fan controller, at least its what I get when taking the list of clusters in https://github.com/dcoffing/KOF-CeilingFan/blob/master/devicetypes/dcoffing/kof-zigbee-fan-controller.src/kof-zigbee-fan-controller.groovy#L81 and looking at the list in bellows/zigbee/zdo/types.py I am using Home Assistant. Will get some logs tonight. |
logs on startup are 2017-06-28 03:38:26 INFO (MainThread) [homeassistant.setup] Setting up zha logs on toggling the switch are At this point the light turns on, but not off. The dimmer and fan do not show up, I suspect it is because the zdo bits for their clusters is missing. |
Can you send me the output of "bellows devices"? |
(homeassistant) [dennis@wandboard02 bellows (master)]$ bellows devices Error: Missing option "-d" / "--device". there does not seem to be an option to specify the database needed |
changed the code and hardcoded in the location of my zigbe db from home assistant Device: |
I don't see any calls to the "turn_off" service in hass, so either the logs don't include it, or the UI toggle isn't actually generating the service call. So, basically, I have no information about why it's failing. What I can see is that getting the response from the device is timing out during the turn on (I think, your log timestamps seems weirdly out of order). What I wanted to check with the devices output was how the fan control was exposed. Since it's a different cluster, I don't think there'll be any weirdness about how the fan and light control interact. Also, adding support in hass for the fan shouldn't be too hard. However, what I do have in bellows isn't the full spec: https://github.com/rcloran/bellows/blob/master/bellows/zigbee/zcl/clusters/hvac.py#L111-L123 , so it'll need a change there first. |
You should be able to get the dimmer working by adding something like this to your config:
|
Oh, it looks like the Fan cluster in bellows is complete. So only work in hass will be needed to make it work. |
okay, setting the device_config I can turn the light on and control the brightness, something about the on off swicth does not work. it just stays as off. I will look at what needs doing in hass. I do wonder if in https://github.com/rcloran/bellows/blob/master/bellows/zigbee/profiles/zll.py and https://github.com/rcloran/bellows/blob/master/bellows/zigbee/profiles/zha.py we would have to add some profile and device info for the fans and the device to be recognised correctly. |
Are you saying that you can't turn it off because the software switch just flips back to off? That would make sense if the turn_on is failing (timeout from your logs). You won't need to add to the profiles. Your device reports a device type of 14 (0x0e), which I cannot find in the spec. You would need to add to https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/zha/const.py#L38-L42 |
yeah the switch just flips back to off |
Aha. Good, now I understand the problem better. If you call the light.turn_off service "directly" without the convenience UI (eg, from /dev-service), does it switch off? Can you send me debug logs from the turn on again, but make sure to include triple back-ticks before and after so that github doesn't treat it as markdown? I'd like to decode the hex from packets being sent and received, but it's mangled. |
Also dove in and installed the same king of fans receiver as ausil. |
calling "the light.turn_off service "directly" does switch off the light |
debug turn on from UI
|
I have started working on adding a fan.zha device https://github.com/ausil/home-assistant/tree/zha-fan right now the fan device shows up. but none of the controls work yet. though it will turn the light off. so i suspect I have not got it right |
just a note, i am under the impression that this KOF controller has 4 fan speeds |
It is a 4 speed fan with "breeze" mode that randomly changes the speed, as well as on/off/dimmer light. I beleiev there is also a control to turn everything on or off, though that may be implemented in software |
Hi Russell |
I don't believe there's any work needed in bellows to make this work, which is why I closed this issue. I left some comments on @ausil's home-assistant branch linked above, but it looks like it's just a copy of the ZWave fan component so far, so there's not much to discuss. I'd be happy to provide pointers, but I'm not in a position to write this code myself. As far as I can tell, the zigbee part of this simply involves writing to an attribute, and bellows already provides an API for that. |
I have the reciever from http://www.homedepot.com/p/Home-Decorators-Collection-Gardinier-52-in-LED-Brushed-Nickel-Ceiling-Fan-43260/206648825 and was wanting to add support for it. it paired okay. and shows up as a switch, which seems to be the switch to turn everything on/off. Turning it on works, however turning it back off does not seem to, the light is a dimmer and the fan speed control ihas 4 speeds, there is a comfort breeze mode that randomly changes the speed of the fan. There is support in smartthings for the receiver, I was wondering if you had any docs on how to best add support for new devices.
The text was updated successfully, but these errors were encountered: