iHomecam Temp/Humidity shows values but no attributes
Hi Community,
I recently purchased me a temp and humidity sensor from Aliexpress since the price and dimensions were what I was looking for.
This is the sensor:
Now to my question;
I can add it to the Zipabox without problems and also get values. It shows and updates just fine in the app.
However, I am unable to create any rules with the unit as it just says "no attributes" in the dropdown when I try.
Does this mean that there is no true support for the device in Zipabox?
If so, what can I do / contribute with to get the support included?
Also worth mentioning is that when I added it it popped us a "unknow manufacturer".
It also seems to be the same sensor as this one from Heimantech:
http://www.heimantech.com/product/86.html
Does anybody know if "that version" works better or if it's just a branded version of the one I already bought?
The same problem 
Hi Kristoffer,
What is weird is that you can get values from devices view. So, the device is correctly supported. In device manager, in the tree of this device, maybe you should have a look at the checkboxes "show as device", "hide in rules creator", "hide in device browser"... There may be a mis-configuration...
Hi Kristoffer,
What is weird is that you can get values from devices view. So, the device is correctly supported. In device manager, in the tree of this device, maybe you should have a look at the checkboxes "show as device", "hide in rules creator", "hide in device browser"... There may be a mis-configuration...
Hi Robin,
I checked again and the device is tagged with "Show as device" and the "Hide in rule creator" and "Hide in device browser" aren't checked.
I can choose the device and put it in a sensor field in a rule, but when I choose the dropdown to select which attribute to use it only shows "no attributes".
I have a Aeon Labs Multi Sensor 6 as well and the configuration between the two are "the same" in terms of visibility etc.
I've attached it as a picture here to illustrate as well
Hi Robin,
I checked again and the device is tagged with "Show as device" and the "Hide in rule creator" and "Hide in device browser" aren't checked.
I can choose the device and put it in a sensor field in a rule, but when I choose the dropdown to select which attribute to use it only shows "no attributes".
I have a Aeon Labs Multi Sensor 6 as well and the configuration between the two are "the same" in terms of visibility etc.
I've attached it as a picture here to illustrate as well
I have the same problem with another device Z-Uno
http://z-uno.z-wave.me/
I can add it to the Zipabox without problems and also get values. It shows and updates just fine in the app.
However, I am unable to create any rules with the unit as it just says "no attributes" in the dropdown
I have the same problem with another device Z-Uno
http://z-uno.z-wave.me/
I can add it to the Zipabox without problems and also get values. It shows and updates just fine in the app.
However, I am unable to create any rules with the unit as it just says "no attributes" in the dropdown
Kristoffer,
Could you post a print screen of the tree of the device with all leafs expanded in the device manager please?
Kristoffer,
Could you post a print screen of the tree of the device with all leafs expanded in the device manager please?
Of course Robin, attached to this comment :)
Of course Robin, attached to this comment :)
So, you clearly have Temperature and Humidity Attributes attached to the device. Seems that it is a Zipato support issue.
Open a ticket on zipato support, joining your zipabox/Zipatile S/N and they should be able to help you.
So, you clearly have Temperature and Humidity Attributes attached to the device. Seems that it is a Zipato support issue.
Open a ticket on zipato support, joining your zipabox/Zipatile S/N and they should be able to help you.
Ok, I've opened a ticket and we'll see what reply I get.
Hopefully the reply can help @Sergey as well :)
Will update the post once I get a reply from the support.
Ok, I've opened a ticket and we'll see what reply I get.
Hopefully the reply can help @Sergey as well :)
Will update the post once I get a reply from the support.
I opened a ticket on this issue on 24 October. So far nothing has been answered.
I opened a ticket on this issue on 24 October. So far nothing has been answered.
i also opened one, on 23.10 :). I asked them to support two more devices with similar problems.
answer was: We will support those devices, however, due to other priority issues we are facing at the moment - there is no time to deal with this.
Please have patience as this may take some time.
i also opened one, on 23.10 :). I asked them to support two more devices with similar problems.
answer was: We will support those devices, however, due to other priority issues we are facing at the moment - there is no time to deal with this.
Please have patience as this may take some time.
I got a very quick response to my ticket but unfortunately it was not really what I had hoped for, although I do understand the perspective.
The answer was:
This device is not full supported by Zipato. When you add it you receive generic descriptor for it and you can use of its functionalities.
We don't have full support for this device.
Heiman device is supported by official Z-Wave standard and it will work better.
There are a lot of alternative solutions on the market and we cannot support all of them.
I got a very quick response to my ticket but unfortunately it was not really what I had hoped for, although I do understand the perspective.
The answer was:
This device is not full supported by Zipato. When you add it you receive generic descriptor for it and you can use of its functionalities.
We don't have full support for this device.
Heiman device is supported by official Z-Wave standard and it will work better.
There are a lot of alternative solutions on the market and we cannot support all of them.
hmm, actually the are alternative solutions, but not many. in that case i don't understand the z-wave standard, when every single device must be implemented in every system to have full support (and in this case it is a stupid thermometer, in my other case door sensor)
hmm, actually the are alternative solutions, but not many. in that case i don't understand the z-wave standard, when every single device must be implemented in every system to have full support (and in this case it is a stupid thermometer, in my other case door sensor)
Replies have been locked on this page!