Smanny
(Felice Marra)
January 2, 2019, 7:15pm
1
So, new firmware 1.4.1_161.0157, new problems:
door/windows sensors work as expected;
xiaomi wireless button doesn’t work anymore;
aqara cube doesn’t work anymore;
temperature/humidity sensors not sure, they update for a while, then I get an error in hass.io that the xiaomi/aqara hub doesn’t update anymore, but the door/windows sensors continue to work.
I updated it today.
Anyone else in my situation?
Thanks for the heads up with latest firmware, you should always wait until its confirmed working with firmware’s before updating.
Smanny
(Felice Marra)
January 2, 2019, 7:44pm
3
I know, but… I saw in the changelog some new devices added and I was curious to see which one. Shame on me.
Smanny
(Felice Marra)
January 2, 2019, 8:31pm
4
I activated the log and it seems home assistant is able to get the commands from the cube and from wireless switch. Not sure why the automations with them don’t work anymore…
The temperature/humidity sensors now update the data correctly.
uiguy
January 2, 2019, 10:48pm
5
I have noticed my wireless switches no longer work…
Smanny
(Felice Marra)
January 2, 2019, 11:06pm
6
something changed, but the wireless switch sends the commands correctly, I can see them in the log
This might be of use, there’s a slightly different way of talking to them in HA now:
Thanks a million
That worked for me! Couldn’t figure it out last night.
Example working code:
- alias: Long Click to toggle Light Strip
initial_state: 'on'
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
entity_id: binary_sensor.switch_118xxxxxxxxxxx
click_type: long_click_press
action:
- service: light.toggle
entity_id:
- light.light_strip
1 Like
@Bit-River is right the component service call was changed around 0.80.0 ish.
Smanny
(Felice Marra)
January 3, 2019, 10:38am
9
I just, sadly , realised that all my automations in automation.yaml don’t trigger. Not even 1.
Something really bad happened to my hass.io
echopage
(riccardo)
January 3, 2019, 10:46am
10
I still have the firmware 1.4.1_161.0143 and no updates reported
Klagio
(Klagio)
January 3, 2019, 10:51am
11
I also thank him but someone has to try…
1 Like
Make sure you’re automations include the following line:
initial_state: 'on'
Seems to be a relatively new requirement.
A working example:
- alias: Long Click to toggle Light Strip
initial_state: 'on'
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
entity_id: binary_sensor.switch_118xxxxxxxxxxx
click_type: long_click_press
action:
- service: light.toggle
entity_id:
- light.light_strip
jrscrs
(Joris)
January 9, 2019, 8:18am
13
Hi Smanny,
Are you sure it’s the Xiaomi firmware update is the problem? I recently encountered something simular when updating home assistant, my automations didn’t work. Turns out the event type did change (in HASS) from
event_type: click
To
event_type: xiaomi_aqara.click
Smanny
(Felice Marra)
January 9, 2019, 8:38am
14
I am not sure of anything… I already made that change and none of my automations worked anymore. I had to reset completly my hass.io . The firmware made a change, time to time I get a no response from the gateway in the log
My Hub also stopped working after firmware upgrade. I’ve managed to make it working after a lot of retries using this config:
xiaomi_aqara:
discovery_retry: 10
gateways:
- mac: !secret xiaomi_mac
key: !secret xiaomi_key
host: !secret xiaomi_ip
I am running the Xiaomi Gateway under the firmware version 1.4.1_161.0158
Yoinkz
January 16, 2019, 7:33pm
16
Where do you see what latest firmware that is supported?
Now I see a new firmware for my Xiaomi Gateway: 1.4.1_164. 0158
Smanny
(Felice Marra)
January 16, 2019, 7:46pm
17
It was replaced by that one quite immediately and now there is no problem anymore.
RKor
(Rani)
June 1, 2019, 11:36am
18
Yoinkz:
1.4.1_164. 0158
Just confirming, is 1.4.1_164. 0158 fine or does it need to be hacked?
Xiaomi Gateway no Longer connecting on latest firmware - "Invalid Config" - #81 by Routout says he had to hack it or something?