Multiple entities showing when only one is viewed


This started happening recently: some history graph started showing (seemingly) random other entities, even though not selected in the card. Also, when selecting certain entities to view status and history, others will show up as well. Here is an example of the history graph – only the temperature entities should be displayed and a zoneminder camera mode is being added (among other things not shown).

Note: I did not change anything in this card – it was working, and in the process of other configuration changes I have broken it.


I have stopped homeassistant, deleted the database and restarted and this is still happening. Any ideas how these extra entities can be creeping into cards without being explicitly referenced?

Thanks in advance.


Same issue here:
This should show only one item, but instead shows some random additional sensors:


I’m having the same issue here. Tried deleting the DB as well, but the problem persists…!



Ok, in my case everything was good until I made an apt-get update and apt-get upgrade.
I have been checked log in /var/log/apt/history.log and this what I have got:

Start-Date: 2019-03-13  14:43:52
Commandline: apt-get upgrade
Requested-By: pi (1000)
Upgrade: libopenjp2-7:armhf (2.1.2-1.1+deb9u2, 2.1.2-1.1+deb9u3), php7.0-cgi:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-cli:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-fpm:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-opcache:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), raspi-copies-and-fills:armhf (0.6, 0.10), php7.0-common:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-sqlite3:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-json:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-readline:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-xml:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-curl:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-snmp:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3), php7.0-mysql:armhf (7.0.33-0+deb9u2, 7.0.33-0+deb9u3)
End-Date: 2019-03-13  14:45:44

So i reverted this changes by commands:
sudo dpkg -i /var/cache/apt/archives/libopenjp2-7_2.1.2-1.1+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-common_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-cgi_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-cli_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-fpm_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-opcache_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/raspi-copies-and-fills_0.6_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-sqlite3_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-json_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-readline_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-xml_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-curl_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-snmp_7.0.33-0+deb9u2_armhf.deb
sudo dpkg -i /var/cache/apt/archives/php7.0-mysql_7.0.33-0+deb9u2_armhf.deb

After reboot my raspberry pi working like before.
In my case it works. I hope that this will help you too.


The only 2 updates I had in common were libopenjp2-7 and raspi-copies-and-fills. I see there’s an issue on github regarding this issue, and someone else only had the copies and fills package in common, so I removed that (no cache package so I can’t revert). The issue is now gone.

I’m guessing a lot of raspbian users are going to run into this over time as they upgrade.


I always run apt update && apt upgrade if I haven’t logged into my Pi in a while. I can confirm that simply removing the raspi-copies-and-fills package fixes the issue for me. Good sleuthing!

Now, what does raspi-copies-and-fills do, exactly? :yum:


Did a sudo apt-get --purge remove raspi-copies-and-fills, rebooted and it’s fixed. So I’m reiterating the question of am I losing any functionalities by removing the copies-and-fills package. :expressionless:


It’s a package to increase performance by replacing a few memory handling functions. There is some info on what happened at this link.

It looks like a rushed update broke a bunch of stuff, then moved to a version that reverted the worst of the breakage but still caused issues. Now another has been released (0.11). I have just updated to the latest (0.11) which is supposed to be equivalent to the original unbroken version and everything appears normal.

Now we just need to watch for that next update, the maintainer obviously wants to change something!


Update is out (as of yesterday)!