Claude Flammang

@Mpeach45

My question was how you did manage to adjust the entity type. (As I don’t have zwave)

By the way:
Homeassistant simply works with the entities provided by the various integrations. So in this case the Zwave integration (Happens to be also maintained by the Homeassistant project) has to learn to report your device correctly to Homeassistant.

@bluesheep
I must admit that this is by far the most extensive but really, really convincing way to say: „I have no clue what Homeassistant is“ that I have seen so far.

@Mpeach45
What is the solution in zwave world?

@Mpeach45
Click on „Basic“ then settings (the gear icon) and you should have a „display as“ setting.
If z-wave integration does not allow that, you can always create a template sensor that converts it to binary sensor.
Did anyone tell you that HA can be quite a rabbit hole where you can achieve virtually anything but not always easily.

@AndLeoErd
Sure as you did add them manually.

@AndLeoErd
Entities with the „visible“ attribute set to „off“ do not appear in any of the automatically populated dashboards.

@ikidd
Currently SLZB-06M and Reolink RLC-810K cam. During my professional life I got to use a few POE devices, never a failure.

@Archer
I still have Multiprotocol on SkyConnect, but only a dozen devices. Still didn’t bother to reconfigure.

@domi
ZHA with 50+ devices from Ikea, Aqara, Frient and Hue over SLZB-06M. Works flawlessly.

@early_riser
Considering the fact that just like Apple Home, HA dashboards strip the first part of the display name if it’s identical to the area name, I use the „area device“ convention. So „Bathroom Leak Moisture“ is displayed as „Leak Moisture“ under the area „Bathroom“.
Furthermore HA allows to recreate entity Ids after renaming a device resulting in: „binary_sensor.bathroom_leak_moisture“.
So if I move my sensor to another location, I simply rename it to „Attic Leak „.

@CAVOK
I have two HAOS installations with MQTT as well as ZHA. Mosquito being an add-on, as far as I know it’s a container anyway but ZHA and MQTT are normal integrations and I never have any issues. Generally speaking I always try to stick with what the developers suggest, in my eyes it’s the best strategy to avoid messing up with dependencies as they take care of those.

@daq
480p is better than 480i, the TV format I grew up with. And guess what, I recognized the actors even on those old Tv sets with their distortion ridden crappy analogue signals.

@lka1988
According to Nabu Casa sales of Yellow went too low to justify the launch of a new production batch.

@southernbrewer
I‘m not a Home brewer but three of our fridges get the same treatment as their primitive „thermostats„ are so crappy. Two simply were either too cold or not cold enough with a ridiculous amount of variation while the third one, an outdoor fridge-freezer combo has the thermostat in the fridge compartment and during cool nights sees no need to cool while the freezer compartment gets close to thawing.

@okamiueru
For over one year now Homeassistant has been reliably announcing the end of the cycle by flashing all smart lights in RV before switching them back to their original state. What i like most is the fact that with the same reliability the washer beeps thirty seconds later.

@KyuubiNoKitsune
I use cheap Aqara sensors, in fridge battery hold several months, but in freezer I have to replace them every two months. Attenuation seems to be less of a problem, at least since I switched to Homeassistant with central coordinator and my Ikea ceiling lights in virtually every room act as repeaters. I the beginning I had separate hubs for each ecosystem and consequently 4 poor Zigbee networks.

@paraphrand
My mothers Miele does it.

@Amberskin
On Pi5 no need for SD it boots and runs perfectly well from SSD.

@tofubl
These are all smartplugs and I confirm that behavior with those i have, they are great for energy metering but not real time power monitoring .
The Shellys I use are those: https://www.shelly.com/products/shelly-pro-4pm

@tofubl
With EspHome you can easily report only changes that are above a defined threshold:

sensor:
- platform: adc
pin: GPIO34
name: “ADC Sensor”
update_interval: 10s # read every 10s
filters:
- delta: 0.05 # only report if change ≥ 0.05