That's exactly the point. The config is determined by manufacturer and product and that's also what is displayed in the admin screen. But the name of the channel is taken from the valueId label.
So: the device is not in the openzwave database but it still reports the name.
Fix: report it to openzwave
YAHKA tot Home Assistant, I get only 1 device instead all 3.
-
I've been playing around with HomeConnect to HomeKit. It seems that only the basic DeviceProperties + the Switch can be passed trought to Homekit.
Does anybody have experience getting more data trought the pipeline?
YAHKA offers Service Type:
-Accessoiry Information
-Service label
-LabelDoes any these services can carry extra information trough homekit? Like the current Dishwasher "time remaining" for example. Who knows wich functions do actually work for homekit? Trail and error did not get me there yet.
And I have another problem with YAHKA. If I use YAHKA to iOS it works fine with turning of and on 3 devices (DeviceProperties + the Switch).
But if I connect YAKHKA tot HomeAssistant.io, I only get 1 device, instead of 3.... Anyone experience with HomeAssistant and ioBroker's YAKHA coupling? -
Read out device properties optionally via ioBrocker.State or similar.
With this you can automatically read and enter the firmware, serial number, manufacturer etc..
