How many entities do you have?
I have around 700. The new thing is that now all automations are listed in the entities list. In my installation it made the number of listed entities grow from maybe 400 to 700.
The problem is amplified by the fact that default is to list everything
Rebuild database has nothing to do with it. This is a browser problem. HA frontend is loading too much on a single page. And it is not just text. Each line is code that loads dynamic information
Custom card?
I am talking about the Configuration -> Entities page. It is not part of Lovelace.
And I have no costum theme either
after upgrade, icon will not change color status whether the unit is on or off
cards:
- cards:
- current: true
details: false
entity: weather.emil_stangs_vei_21c
forecast: true
name: NĆ„
type: 'custom:weather-card'
type: horizontal-stack
- cards:
- entity: light.downlight_stue
hold_action:
action: more-info
icon: 'mdi:spotlight-beam'
name: Stue
tap_action:
action: toggle
type: entity-button
- entity: light.taklampe_kjokken
hold_action:
action: more-info
icon: 'mdi:ceiling-light'
name: KjĆøkken
tap_action:
action: toggle
type: entity-button
- entity: light.ledlys_trapp
hold_action:
action: more-info
icon: 'mdi:stairs'
name: Trapp
tap_action:
action: toggle
type: entity-button
- entity: switch.env2001pe_climate_control
hold_action: more-info
icon: 'mdi:air-conditioner'
name: Nissan
tap_action:
action: toggle
type: entity-button
type: horizontal-stack
- cards:
- entity: light.alle_lys_soverom
hold_action:
action: more-info
icon: 'mdi:ceiling-light'
name: Soverom
tap_action:
action: toggle
type: entity-button
- entity: light.downlight_baderom
hold_action: more-info
icon: 'mdi:spotlight'
name: Bad
tap_action: toggle
type: entity-button
- action: more-info
entity: light.lys_ventilator
hold_action: more-info
icon: 'mdi:chemical-weapon'
name: Viftelys
tap_action:
action: toggle
type: entity-button
- entity: light.hue_color_lamp_gang
hold_action:
action: more-info
icon: 'mdi:ceiling-light'
name: Gang
tap_action:
action: toggle
type: entity-button
- entity: light.paere_spisebord_conbee
hold_action:
action: more-info
icon: 'mdi:lamp'
name: Spisebord
tap_action:
action: toggle
type: entity-button
type: horizontal-stack
- cards:
- entity: switch.moccamaster
hold_action: more-info
icon: 'mdi:coffee-maker'
name: Moccamaster
tap_action: toggle
type: entity-button
- entity: light.downlight_veranda
hold_action:
action: more-info
icon: 'mdi:track-light'
name: Utelys
tap_action: toggle
type: entity-button
- entity: light.julelys_ute
hold_action:
action: more-info
icon: 'mdi:pine-tree'
name: Julelys
tap_action:
action: toggle
type: entity-button
- entity: light.julelys_inne
hold_action:
action: more-info
icon: 'mdi:snowflake'
name: Julelys
tap_action:
action: toggle
type: entity-button
type: horizontal-stack
- cards:
- entity: switch.qnap_419_wol
hold_action: more-info
icon: 'mdi:nas'
name: QNAP
tap_action:
action: toggle
type: entity-button
- entity: switch.samsung_power
hold_action: more-info
icon: 'mdi:television-classic'
name: TV
tap_action:
action: toggle
type: entity-button
- entity: switch.samsung_hdmi1
hold_action: more-info
icon: 'mdi:video-input-hdmi'
name: HDMI 1
tap_action:
action: toggle
type: entity-button
- entity: switch.samsung_hdmi2
hold_action: more-info
icon: 'mdi:video-input-hdmi'
name: HDMI 2
tap_action:
action: toggle
type: entity-button
type: horizontal-stack
- cards:
- entity: alarm_control_panel.emil_stangs_vei_21c
name: Alarm
states:
- arm_away
type: alarm-panel
type: horizontal-stack
type: vertical-stack
700 is an impressive number. Iām curious what makes up the majority of those. For the history page I would imagine you probably wouldnāt need history on all of them? Maybe excluding some from recorder would help with the history not loading part? Like I had scenes in there from lutron and there was no need to see round the clock of the same status of āSceneingā.
think this is related to a change introduced in 0.105ā¦assuming Iām right then you need to add state_color: true to the card(s) and youāll be back in action (thereās more on this in the comments under the 0.105 release notes)
As I said, the history graph is not that important on a portable device.
The issue I am deeply concerned about is the entity view because there is nothing I can do to limit the displayed number before the page is loaded. If I could apply a filter and then click submit then I could limit the list.
But listing an html table with 700 lines on an iPad is not a big challenge for a browser. It is the fact that each line is an active element that fetch data and it seems to kill the rendering engine.
On a stationary computer you can see that the browser works hard. The html loads in 0.4 seconds and the. It takes around 6 seconds to load the data. And this is on an i7 with loads of RAM and gigabit Ethernet. The HA machine is also a real computer and not a Raspberry pi.
The entity page has become really heavy and for a mature installation like mine, it kills IOS Safari browsers. As I said 700 entities. Remember many devices represent many entities. A single Philips Hue motion sensor is also a light sensor, temperature sensor, and battery sensor. Each window and door sensor reports battery and temperature. Each Philips remote is a battery sensor and there is an automation associated with each button and long press. So that is at least 9 entities for a Philips remote. It quickly adds up. I have around 35 zigbee lights. I have around 15 MQTT type devices with multiple entities each. The Unifi integration adds all devices on the Wifi as an entity. . And 7 Amazon Echos and 7 Google Homes. An Apple Tv, a Samsung TV, a Kodi box. Two sirens. Two smoke alarms. It adds up quickly. Around 400 entities are device related. And around 300 automations. It sounds big but really it is not. You will all end there within a year if you are just a little serious about home automation. And we all are, right? Otherwise we would just have a Hue bridge and a couple of Echos.
Same here! frustrating! @Petter_Aarak what did you do tofix it? Did you remove the deconz plugin/add-on and re-add it? I have a lot of zigbee devices and i am worried to loose them.
While I am still not quite near even 400 entities, I agree with you about the way the frontend loads those pages. Yes not many folks have 700 entities or even 400 devices, but it should still be a concern for everyone that if you had to add so many devices that would run into these issues. Probably kind d of an edge case so not sure the devās motivation to fix it, but having this fixed would at least give peace of mind to the rest of us that we can dream bigger about our ha systems. At least for myself with āonlyā 50ish devices and about 200 entities, I donāt want to think of such limitations as I brainstorm the otherwise seemingly limitless application of ha in the home.
Yes, delete decons from home assistant. Add it again and everything became normal. Now I see Circadian Lighting is not working properly 
. Thank goodness it seems automation and script work OK 
so I can wake up to dim lights, radio and freshly cooked coffee
I had deleted integration and added again. HA added new sensor (new names). I had to made new automations based on deconz integration, but when I restarted HA, sensors became unavailable again. This is problem with this integration in 0.106 release!
I removed deconz plugin and re added it. After this sensors have new names - I had to made new automation based on new names. This is huge bug
But if i delete the addon, does all the zigbee entities also getting removed?
Yes but when You re-add integration they get back. In my situation they back but with changed names. After reboot HA they are unavaliable.
Anyone else having issues with Node Red not connecting to the HA nodes after this update?
entities are stored on decon and same on hue hub. entities must be removed from home assistant and everything became normal when I reconnect decon. i only have sensors on conbee and all philips and ikea lights on hue hub. i havenāt changed anything on light since iāve only seen errors on the conbee and the sensors.
I canāt get the more_info for person displaying correctly - it just shows the same as previously? Does more_info only work if I am away from home?
(as Iām home itās using the ping sensor instead of GOS but in my person config it has GPS as well)
Also, I suddenly seem to have 3 system generated cast users that I canāt get rid of?
The map card and page itself only shows users who are not_home so I would imagine this uses the same logic.
I am glad i made a full snapshot before the 106 upgrade today, i had to restore since the most of my Deconz sensors went unaccessibleā¦
After restore to 105.5 and config from earlier today my HA is ok again 
Hue hubs have rate limits. If you have a lot of lights on it and you have those devices in groups in HA, itās a single call for each individual light. This causes rate limiting as you can only send ~12-15 requests to a Hue hub per second before the hub will rate limit requests (seriously dumb decision on Philipās part). I understand why it was done (Hue groups donāt pass unique IDs, so creating entities for them has been problematic at best), but there needs to be something built into the integration to allow for groups to be enabled in addition to the configuration.yaml parameter.
Hue groups can be re-enabled via configuration.yaml, but for new users (especially those with large Hue systems), this is going to probably cause issues for them.
