-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add philips.light.zystrip support #24
Comments
@terenceng81 Do you use the MiHome app with the philips.light.zystrip and do you have a rooted android device? I'm interested in the Mie Home app plugin of this device. Are you able to control the device if you use the bulb model at your configuration.yaml? |
FYI, I am currently using "philips.light.bulb" for the Philips Cove light "philips.light.zystrip", it is working and having the "Google Home unable to add Unavailable issue" issue. |
Yes, I am able to control "philips.light.zystrip" using bulb model. Yes, I do have rooted Anroid simulator that i used to collect tokens from the database. |
For unknown reason, all assigned lights (philips.light.bulb and philips.light.downlight) are gone in Google Home.. It seems "Model" is not the root caused. All these devices are now in "Linked to you & Not in a Home & Room" in Google Home App, :-( |
It doesn't sound like an issue of this costum component. Do you have additional devices /components in Google Home which are stable? |
I have Yeelight products (strip, ceiling light, bulb, table lamb), they are stable. Aqara products (Curtain, Aircon Controller, Power Plug) Zhimi products (Pedestal Fan) Xiaomi products (Vaccum robot, Sensor, Air Humidifier, Air Purifier) All the above are ok except for the Xiaomi-Philips Downlight and Cove Light |
If you unplug and replug the Air Purifier, do you have the same issue? |
U are right, the same issue happens. Air Purifier becomes a "new found" device after I refresh the main page of Google Home App.. It does not happen to the integrated "linked Services" like "Yeelight" or "Smart Things". I've linked XiaoMi Service but only limited devices available and does not include XIaoMi-Philips downlight. |
The problematic devices are exposed by HA. The Yeelight and Smart Things devices are connected directly? May be this is a HA issue in general independent of the used HA component/integration? |
You are right, I just tested other devices and experienced the same issue, so long they are exposed by HA will then encounter this issue. The Yeelight and Smart Things devices are added to the Google Home App directly, Google called it "Linked Services", all these devices are not affected. High chance this is a HA issue but I do not know how to escalate this case to official HA, |
Please open an issue at the official repository: https://github.com/home-assistant/home-assistant |
Thanks syssi. I have reported this case using the link given. Below is the case link. BTW for your information, this issue does not happen to HA Cloud, maybe this is the only difference between Paid and Free service. :-( |
The zystrip supports following methods:
And properties:
|
@terenceng81 Could you provide the output of these commands:
In some cases it would be interesting, what's happening if you've called the command. Thanks in advance! |
Could you provide a link to a product page where I can see/buy the device we are talking about? |
i think it's this one |
I got it from I've compared the link given with my link, yes they are the same product. |
Hi syssi, May I know how do i run this command? ssh to my HA and entered the command below but does not work.. core-ssh:~# miiocli device --ip 192.168.8.152 --token 3bd3c23837xxxx info |
If you have another linux host just install python-miio by:
|
Only the first command is working, the rest having "Unknown command" errors. Last login: Mon Oct 28 13:27:07 on ttys002 Error: Unknown command (get_switch_en) |
I've fixed the command list. There was a parameter missing:
|
Everything is okay except for the Enable_AC_On and Enable_AC_Off miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e info miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command get_prop "['power', 'bright', 'cct', 'snm', 'dv', 'sw', 'bl', 'ms', 'ac']" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command get_switch_en miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command get_rc_mac miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_power "['off']" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_power "['on']" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_cct "[1]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_cct "[35]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_cct "[36]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_cct "[100]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command get_prop "['power', 'bright', 'cct', 'snm', 'dv', 'sw', 'bl', 'ms', 'ac']" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command set_power "['off']" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command enable_ac "[1]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command enable_ac "[0]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command enable_bl "[1]" miiocli device --ip 192.168.8.113 --token 527daede17f1afe5de70a5cd40f7317e raw_command enable_bl "[0]" |
2019-09-08 18:37:04 ERROR (MainThread) [homeassistant.components.xiaomi_miio.light] Unsupported device found! Please create an issue at https://github.com/syssi/philipslight/issues and provide the following data: philips.light.zystrip
Could you guys help to support the strip light? It should be technically possible according to https://www.openhab.org/addons/bindings/miio. Appreciate your help!
The text was updated successfully, but these errors were encountered: