The only device I have seen myself and even that wasn’t in person, was a Fibaro Dimmer 2 module on one of those Ezlo Youtube videos. I spotted it had a “Heat Sensor” as a child device on their video etc.
So I asked them why ?
Their response was
"This is normal that such a kind of device has a separate heat sensor because in the manual it is said that when it is overheated or a voltage drop it will send a notification. It is not only about Fibaro Dimmer 2, we had 3-4 same kinds of devices and had a discussion with RF and IOS team, there is no sense to hide it, it should stay like this. "
My reply was:
"There is a parameter setting number 49 about Heat Alarm, I’ve never heard about this being exposed as an actual child device however.
- OVERHEAT (critical temperature) and VOLTAGE DROP (low voltage) alarm report
Available settings:
0 – No reaction
1 – Send an alarm frame
Default setting: 1
Parameter size: 1 [byte]
Should it not just send an alarm notification rather than being a child device?
Also that raises another question, how do you hide devices from the Ezlo system?
On Vera firmware hubs we can just add a single line of code containing the device number we wish to hide, into the Startup LUA section under Apps - Develop Apps."
And then I later raised this question:
"So if I set parameter number 49 to 0 No Reaction, presumably no overheat alarm would be sent to the controller hub. Would the Heat Sensor device in your GUI then just not function but remain visible? "
I never got a reply to that question however. But its a good question !
Regarding being able to select to hide particular devices from the Ezlo GUI , I did get this response.
“Yes, you are right, for now we don’t have any possibility to hide any device from Ezlo GUI.”
I am still not convinced these “Heat Sensor” child devices should be being created. Especially for the Fibaro Dimmer 2 example I looked in to.