as mentioned everything but the dining table look fine... albeit a few are a little slow.
Have you tried just doing a repair on that one device? (dont do a full zwave repair).
the zwave page will not update immediately , because of this to see if the repair helps open up the zwave logs (from the zwave page) and see there what route it is taking after the repair.
Also assuming, the dining table and chandalier are both in the dining room. it would help to put a device like a repeater or something that is not in a metal outlet box in that room.
ie
Are you evading this question for some reason? It is important to know. Any metal will greatly interfere with the signals.
Is there any outlets you could possibly plug in a zwave repeater around here?
I am guessing you are in Europe somewhere, so not sure what is available for repeaters.
Also, sorry if this was responded to already but this is a long thread, how is the hub powered? PoE power (with a splitter) is known to cause z-wave problems. PoE and the C8 (with extensive testing)
ah sorry I wasn't evading. When i answered "10 mm gyprock. Plasterboard" i meant that's all there is. I should have been more specific. No metal junction boxes. Only metal would be the switch wall plate. I'll check that the aeotec is not behind it, it normally should hang down.
Possibly, people have had good luck with the included one but I can recall a couple of times where people said swapping it out fixed one thing or another. Ideally you want a non-PD supply (type A port) with an A->C cable. Needs to be at least rated for 1A or higher. I use an old iPhone supply, due to the small size it fits on my UPS nicely.
@anitesh.a.kumar Do those switches happen to have power reporting built in? If they are reporting power metric frequently it could be causing issues. Otherwise if they are only switches there should not be a lot of chatter and the S0 would not really be a problem.
in most cases it should prompt you, if it doesn't you will need a z-wave stick to pair it to hubitat without encryption. S0 is the worst. Note: If you have a lock running s0, leave it alone.
S0 will never prompt, SiLabs assumes devices using S0 require it and it forces you to use the encryption. The only way to avoid it is a trick using a secondary controller as explained.
If you have dialed back the reporting and can confirm it is not spamming messages out then you should be fine. S0 is not as horrible as people make it sound, it should only be a problem on sensors that are heavy on reporting. If you turn on debug logging every incoming message should get logged so you can confirm if setting the interval slows it down.
Can you post the info from the bottom of the device page in the "Data" section. I might be able to find more settings online using the model info, where the metering can be disabled.
Also, set the threshold as high as it can go, that will further reduce power reports. Not sure what this "Supported Reports" has for options?
Yes, that could be another work around to the S0 issue, BUT many of the devices that are S0 only, are so old they do not have Smart Start QR codes. It seems like Smart Start started getting pushed right around the same time that S2 came out.
basically it was that DNI shifting that didn't work. I'm guessing the S0 might have carried over from C5, not sure. I force removed devices, factory reset it, exclude, include, and boom it just works.
Plus the devices show security as "none". See sample alfressco 3.
You will need to power down the devices that you removed, shutdown and pull power to the hub for a couple mins and power back up then click refresh then remove on those lines. If they won't remove you will need a z-wave stick to remove them. The way you went about it wasn't clean. You should have run an exclusion instead of a force remove.
