Some of the logos already exist in another part of the repository. Another PR has to be created to remove them when the new ones are created.
1 Like
Yup happened to me on several installs (108, 108.3, 108.5). Iāve given up. Seems The google_calendar component has had an undocumented breaking change.
Click the letter to enter your profile itās under the bell:
1 Like
modbus serial rtu not works on all 0.108.X versions
Thanks @firstof9 !!
Now itās really better!
One more thing.
Iāve several addon in the sidebar that I see with an admin user. With a ānormalā user I donāt see a lot of them, but I see some.
Is there a way to hide also these others?
Thanks again
I donāt think there is just yet. The whole user system is still new and a work in progress.
What can I do to help diagnose the system gradually slowing down issue?
Thereās nothing in my logs apart from some components/integrations I havenāt tidied up and my CPU/Memory usage stays pretty stable.
Issues goes away if I roll back to 107.x
yeah i noticed that too!
Also is anyone else not getting the 108.6 update?
I just upgraded from 0.107.7 to 0.108.6 without any error.
Was holding the update until the Broadlink integration was fixed, and it works flawlessly.
Thanks to de devs, and specially to Danielhiversen.
I have 2 broadlink RM Pro. One RM2 PRO and an RM4 Pro. RM2 works perfectly just from the first moment when I used it. After I upgraded HA to the latest version 0.108.6, I am not able to integrate RM4 Pro.
These are my settings from configuration.yaml
for the switch
- platform: broadlink
host: 192.168.1.166
mac: 24:DF:A7:B9:C6:81
type: rm4_pro
for the sensor
- platform: broadlink
host: 192.168.1.166
mac: 24:DF:A7:B9:C6:81
type: rm4_pro
monitored_conditions:
- 'temperature'
- 'humidity'
Each time when I press Check Config button I receive the following message:
Blockquote
Invalid config for [sensor.broadlink]: [type] is an invalid option for [sensor.broadlink]. Check: sensor.broadlink->type. (See ?, line ?).
Invalid config for [switch.broadlink]: value is not allowed for dictionary value @ data[ātypeā]. Got ārm4_proā. (See ?, line ?).
Can you help me please with some advises? I want to mention that RM4 PRO is already Registered in Broadlink app and has a fix IP.
[Later Edit]
I comment out type line from both blocks of code and I didnāt receive any error when I check the configuration. After reboot, the switch is not available and the sensors return the following state
Logos - how do custom components provide for or specify a logo?
After waiting for the Broadlink fix I have now found that HA version 108.6 with broadlink integration 13.1 has not fixed the issue of long IR codes not being sent by RM mini 3.
1 Like
Yep! I was refreshing the damn supervisor page many times today waiting for .6 release to fix the broadlink integrationā¦
Very disappointed that itās not a fix at all, in fact I donāt even think whoever worked on the āfixā tested if it really fixed the problem of long codes not being sentā¦
He asked users to test it. Did you?
They donāt (not currently at least)
In conclusion, they didnāt push the code in .06?
Version 0.108.6 still having issues with height in other views than the default home view.
I did test it, the broadlink component from 107 does work and thatās what I have as a temp fix.
It hasnāt been pushed out to the newest release
Checking Broadlink init.py from Github, I observed that RM4 integration is implemented. Maybe is not merged in .06?!
rm4: [0x51da, # RM4b
0x5f36, # RM Mini 3
0x6026, # RM4 Pro
0x610e, # RM4 Mini
0x610f, # RM4c
0x62bc, # RM4 Mini
0x62be # RM4c