The sensor isn’t being properly passed to HA on my system.
Normally, all devices appear under Devices in HA, but this one doesn’t.
It appears under Devices and Services in MQTT, and something’s wrong there.
It also has an old name from previous tests (some time ago).
AND: It shows as OFF there, but it works in Z2M.
I’ve already deleted it from Devices and reinstalled it, but it always reappears with the same name.
How can I completely delete the sensor?
Or what else can I do?
It seems like you’ve may still have remnants of the old device entry still there. Delete the device from HA, deleting the device from Z2M too won’t hurt (also select force delete to remove the database entry). In HA go to devices and make sure it’s not there, delete if it is. Go to Entities, look for leftovers of the device, they may have red alert icons next to them like this:
Delete all the entities with the old/new name. Pair the device again in Z2M, and let HA discover it.
Hello absent.
I’m still having trouble with my T1 vibration sensor.
You sent me a picture of your setup.
In that picture, EVENTS and ACTION are displayed.
This section isn’t present in my setup.
My question is:
How does the sensor integrate into Home Assistant as a device for you? Where does it appear there?
For me, it always immediately switches to OFF upon the first activation in MQTT, and it doesn’t appear in HA devices either.
I tried deleting everything I could find related to the T1 sensor using the MQTT Explorer, according to the instructions, without success.
After uninstalling, would I have to delete everything in Z2M and MQTT1??? But I’m not familiar enough with that as a new user.
Or should I completely delete MQTT, but I’m hesitant to do that, and would that even help?
Would it help if I ordered a new T1 vibration sensor and programmed it?
Thank you,
Wolfgang P.
It will appear in your devices list, under the name you gave it in Z2M. When you click on the “turned off” what is it actually referencing? Are you sure that’s just not the firmware update notification setting to an off state, meaning there isn’t a firmware update available? Have you enabled events in the Z2M HA integration settings, and actually moved the device to trigger an action?
The previous vibration sensor is recognized in the device list and works perfectly.
The new T1 vibration sensor is not being added to the device list as a new device!
Perhaps the new sensor is faulty and I should order a new T1?
I’m sending a screenshot of the integration settings in Z2M and HA.
What should I configure there before the next installation?
How are you accessing this page if the device doesn’t appear in the device list? Do you have any filters enabled in the devices list?
Enable the event entities.
Thank you.
No filters are active.
I will activate them and test them.
You’re simply amazing!
The Vib.-T1 works, thank you so much for your help.
I’m already excited to see how it works once installed 
Will it be integrated as it is now (GitHub)? Will you be doing that?
May I contact you tomorrow or so about the device pictures?
Best regards,
WolfgangP.
Glad it’s working at last. There’s a PR in to update the Z2M device code.
The issue with the device images is simply that you’ve got an HA theme with a white background and the device images are of devices that are white. If you want them to show up better you can only either change your HA theme or change the device images from the default ones to ones with a dark background.
There’s a PR in to update the Z2M device code.
Will this happen automatically after an update?
Do I need to change anything?
Regarding device images:
I’m 100% certain that these device images were displayed with higher contrast on a white background.
This was definitely fine before an HA update,
then suddenly it’s worse!
Where are the images retrieved from, or…?
Perhaps something happened there?
(GitHub?)
You’ll need to update Zigbee2MQTT when the new version is out.
They’re pulled from the Zigbee2MQTT.io website. They usually only get updated when a new device is added. I doubt all the Aqara images were replaced recently. The change most likely happened in your HA theme setup or your display settings.
If you don’t like a device icon you can replace it with a custom one in the device settings:
Yes, it probably happened to me in HA after an update.
Is there a way to fix something like that?
Or if not:
If I create my own images, can I use a custom local path with a folder where the images are stored?
Or is there a specific area in HA where I have to put them?
I think it’s an area in HA, or Z2M.
But I’m not familiar with that.
As it says in the description “a path to a local file inside the `device_icons directory (e.g. device_icons/MODEL123.png).” That’ll be inside your HA install if you’re using Zigbee2MQTT as an addon.
A quick Google brings up a tutorial:
Thank you for your efforts!
I’ll search on Google.
I’ll keep you updated.
Thanks.
The updated is now in the Zigbee2MQTT code base and included in version 2.9.2+ so the sensor will work out of the box from now on.
Thank you so much for the information,
I’m very happy it works.
Best regards, Wolfgang P.
1 Like