Philips Eyecare - physical buttons stops working after few days

[pniewiadowski]

Hi There,

don't know really where to put this issue, here or in Home Assistant, but let me try to explain and the you can redirect me to appropriate project.

Once the light is hooked up to Home Assistant via the miio integration, after few days, the physical buttons stops working on the device.

So we have two scenarios:

1. Philips eyecare synced with Mi Home app, works without problem. Both, physical buttons and app control works without problem,
2. Philips eyecare integrated into Home Assistant, works for 4, 5 days (physcial buttons, Mi Home app control, and via Home Assistant). After 4, 5 days, buttons doesn't react on touch, app control and HA integration works though.

Once I pull out the plug and plugin back again, the device reconnect to network, and buttons work again for few days.

I have run some debug commands and I am not able to spot anything interesting here, but maybe you are.
This is what I can see just after reset:
PS C:\WINDOWS\system32> mieye --ip=192.168.0.113 --token=xxxxxxxxxx-d INFO:miio.philips_eyecare_cli:Debug mode active DEBUG:miio.philips_eyecare_cli:Connecting to 192.168.0.113 with token xxxxxxxxxx DEBUG:miio.protocol:Unable to decrypt, returning raw bytes: b'' DEBUG:miio.device:Got a response: Container: data = Container: data = b'' (total 0) value = b'' (total 0) offset1 = 32 offset2 = 32 length = 0 header = Container: data = b'!1\x00 \x00\x00\x00\x00\x03.\xa0"\x00\x00\x02\xd2' (total 16) value = Container: length = 32 unknown = 0 device_id = unhexlify('032ea022') ts = 1970-01-01 00:12:02 offset1 = 0 offset2 = 16 length = 16 checksum = b'\x8f\x00\xcb\x89]\xe5j\x00\x0e\x8e\xc3\xca\x85\xec\x03\xe2' (total 16) DEBUG:miio.device:Discovered 032ea022 with ts: 1970-01-01 00:12:02, token: b'xxxxxxxxxx' DEBUG:miio.device:192.168.0.113:54321 >>: {'id': 2, 'method': 'get_prop', 'params': ['power', 'bright', 'notifystatus', 'ambstatus', 'ambvalue', 'eyecare', 'scene_num', 'bls', 'dvalue']} DEBUG:miio.device:192.168.0.113:54321 (ts: 1970-01-01 00:12:02, id: 2) << {'result': ['on', 47, 'off', 'on', 1, 'on', 1, 'on', 0], 'id': 2} Power: on Brightness: 47 Eye Fatigue Reminder: False Ambient Light: True Ambient Light Brightness: 1 Eyecare Mode: True Eyecare Scene: 1 Night Light: True Countdown of the delayed turn off: 0 minutes

This is once the button stooped reacting:
PS C:\Users\Przemek> mieye --ip=192.168.0.113 --token=xxxxxxxxx -d INFO:miio.philips_eyecare_cli:Debug mode active DEBUG:miio.philips_eyecare_cli:Connecting to 192.168.0.113 with token xxxxxxxxx DEBUG:miio.protocol:Unable to decrypt, returning raw bytes: b'' DEBUG:miio.device:Got a response: Container: data = Container: data = b'' (total 0) value = b'' (total 0) offset1 = 32 offset2 = 32 length = 0 header = Container: data = b'!1\x00 \x00\x00\x00\x00\x03.\xa0"\x00\x04\x8e\xaa' (total 16) value = Container: length = 32 unknown = 0 device_id = unhexlify('032ea022') ts = 1970-01-04 10:57:46 offset1 = 0 offset2 = 16 length = 16 checksum = b'\x8f\x00\xcb\x89]\xe5j\x00\x0e\x8e\xc3\xca\x85\xec\x03\xe2' (total 16) DEBUG:miio.device:Discovered 032ea022 with ts: 1970-01-04 10:57:46, token: b'xxxxxxxxx' DEBUG:miio.device:192.168.0.113:54321 >>: {'id': 2, 'method': 'get_prop', 'params': ['power', 'bright', 'notifystatus', 'ambstatus', 'ambvalue', 'eyecare', 'scene_num', 'bls', 'dvalue']} DEBUG:miio.device:192.168.0.113:54321 (ts: 1970-01-04 10:57:47, id: 2) << {'result': ['off', 50, 'off', 'off', 1, 'on', 1, 'on', 0], 'id': 2} Power: off Brightness: 50 Eye Fatigue Reminder: False Ambient Light: False Ambient Light Brightness: 1 Eyecare Mode: True Eyecare Scene: 1 Night Light: True Countdown of the delayed turn off: 0 minutes

I can try to help with debuging this, but please tell me what else I can do here.
I own two of these lights, and both react the same way. I found a guy on the internet, which has same problem as mine.

[syssi]

Do you mean the button of the device itself? What happens after 4-5 days if you remove the integration from HA?

[pniewiadowski]

Yes, I mean the button of the device itself. Any of the buton doesn't react.
Well, I didn't think of removing this integration, but le me check and come once the issue occur again. It can take few days :)

[pniewiadowski]

This time issue appeared a bit faster. After few hours. I have removed the integration from HA, but this did not resolve the problem. The other light which is not integrated with HA works as it should.

[syssi]

You should contact the manufacturer of your device because it looks like an firmware issue which cannot be solved here.

[pniewiadowski]

Hmm, so why is that the manufacturer integration (Mi Home app) works, while once I start using python-miio it stops?

[syssi]

What did you mean by:

I have removed the integration from HA, but this did not resolve the problem.

If the issue appears without interaction with 3rd party apps/libraries it should be a hardware/firmware issue of the device itself. Correct me if I'm wrong. :-)

[pniewiadowski]

I thought you want me to remove the integration from HA, once the issue occur again.
So I did, and the issue persists.

The other Philips light is sync with Hi Home app, but not with HA and the issue doesn't appear so I think there is something with python-miio.

Hope I am clear now :)

[pniewiadowski]

Hey, I found out this is the same here: syssi/philipslight#25

I can try and help, but need some guidance, what I can check.

[maximalexanian]

The same issue here with two different versions of the lamp. Please let me know if I can help debugging it

[Emilv2]

Same issue here, when integrated with Home Assistant the physical buttons stop working after a while until the power is turned off (after which it happens again). When it's not connected with Home Assistant this problem does not occur.

I would say that the most logical explanation is that python-miio somehow triggers a bug (or a hidden child lock function?) in the firmware, but maybe we can find a workaround for it?

[pniewiadowski]

Hey, any news about this? I really would like to help, but not sure how.

[rytilahti]

Well, the only real way (in my opinion) to find out is to use the command-line tool (or create a script to do those calls) and find out at which point and at which call it will get stuck.

My intuition agrees with the analysis of @Emilv2 on that regard, but we need to find out what triggers it and then create a workaround for it.

As it does not hit until a few days later, maybe this has something to do with the sequence numbers?
So perhaps:

• Too high sequence numbers trigger that behavior, or
• Cycling the ID back to one triggers this.

One way to try that out would be to initialize the device with a large sequence number and see what happens when it hits the limit (see https://github.com/rytilahti/python-miio/blob/master/miio/miioprotocol.py#L231).

[seafoodrice]

To refresh the discussion of the defect, I am joining the party and become another additional victim of the issue.

[xekil]

I have exactly the same problem with 3 lamps, it is annoying because my children can no longer use the lamp, you can find a solution? Thanks you

[bazuchan]

A have the same problem with xiaomi zhimi heater and it started after firmware upgrade.