Mecheng70

Aeotec recessed door sensors are still not working. Have tried compatibility mode and write changes and sync.

Do you have a screen shot? Sometimes they are added, zwave tends to have child nodes. If you right click and group them, they are easier to visualize. As for the function, some are a mystery.

Not advocating for inovelli but the dimmers have the ability to change the parameters for instant on and not use the dimmer function.

I have it to only one lock that isn't functional. Pulled the batteries before I left town. Another lock doesn't seem to indicate alarm status. Chris mentioned a fix coming.

Switches are back up in 4.0.5.

Well that would be going back several months ago. So maybe a rebuild or move to another hub. I have readded/reset several devices post migration.

Just stopped working. Couldn't lock, unlock.

I did order a zooz stick. Need to look into removing the current zmatter and replacing it with the zooz. Probably another weekend of work. 😁 Assume it would be better to wipe all devices and start fresh.

I find the HA with triggers to be more flexible and robust.

Are you seeing the issue with switches not showing up in HA?

Chris did connect with me last week (I appreciated his time) and was able to get the door locks up and running... then 5.5.6 and only one out of four is working. Personally I used to look at this as the rock for my zwave network and that if HA goes down, ISY through Google Home is still usable. Now I am willing to forgo the "stability" that I have come to have known and push forward with HA and Zwave only.

This is a little bit of a rant and a lot of frustration. As an medical device engineer I am probably pretty critical of products and how they work, but the shear frustration the past several weeks is wearing on me. If my products fail, there is a good change you end up with more complications that can be life threatening. One day the system is working, the next day, none of the programs are responding because the devices aren't recognized and need to be resynced. How many times do I need to write changes and resync? They just aren't syncing. WTF. Starting to figure out that the battery operated zwave locks that would last for 3-4 months now have a life of 3-4 weeks. Dropped $500 for this heartburn. I understand the enormous ecosystem, but why was the 994 with zwave working and now it's a cluster.

@shbatm may have to jump on here. I thought it was rolled out in 2023.2.X. Curious, Do you have the HACS install of Universal Devices? Or just the Addon?

What HA version are you running?

On mobile. You need to use the number set call service. Before you try it: 1. make sure that you have enabled "adding variable entities" in the configure panel of the integration. 2. In the integration panel select the entities and enable them. They are disabled by default. You can select which ones to enable. 3. Use the Number Set call service and select the entity.

I feel your pain. Good luck.

@shbatm Redownloaded the integration from HACS. Restarted HA. Still having the unavailable issue on most of them. Is there another version I should be looking for? 4.0.4 is what I downloaded. As for the sensors - most are showing up as unavailable under the Device Info screen. Lights/Switches - What is more interesting is that most of the child nodes are showing up as Unavailable versus Unknown.

Apologies. The UDI integration in HA. Kind of the beta site.

I can't confirm this. However, I did just run the query due to the missing or not offered devices in the previous post. Will confirm if that works or not.

Just updated to 4.0.4 in HA and after reloading there are several devices that have the ? on the icon in the lovelace. In the entities panel: However, all devices are showing up and operational in UDI Mobile.

sent files

I will remember to do that next time. Working with Chris tonight to troubleshoot some zwave issues. If we reboot then I'll capture it. Thanks for the explanation. I get it. Appreciate it.

@shbatm Noticed this: if the nodes in eisy have not been queried (system reboot) then they are loaded as sensors until each one is queried and HA is restarted. This also removes all the icons that were selected in the entities section. Can we load them as what they are and not assume that they are sensors?

To add to this, eisy has rebooted on its own several times during the night.

Starting to get things up and running. Here is what I did: Power cycled each device and then updated with interview. Had one device that just didn't want to cooperate so that one was readded and it now functioning. Battery devices (the reason I updated) are going to have to wait until tomorrow.