07.08.2016, 16:43 (This post was last modified: 07.08.2016, 16:44 by andeug.)
Hi,
I've bought today a Fibaro Door/Window Sensor and a 1-wire temperature sensor.
I've connected them according to the attached picture and found that I was able to read only the below data:
1/1/19 Battery Level (looks currently 100%)
1/1/13 Sensor Object - doesn't do anything. I was expecting to give me the temperature from the DS18B20 sensor, but instead I get the value TRUE.
1/1/17 Contact Status - I get only value 22/23, value which gets changed if the magnet is near the Fibaro sensor or not. Currently I've assigned the values 22: Door Open (Ușă Deschisă) and 23: Door Closed (Ușă Închisă).
Am I doing something incorrect, so that I am not getting the temperature reading from the temperature sensor? Is the temperature feature implemented, or I have my temperature sensor broken?
I've seen this topic which is treating the 1-wire connection to Reactor v2, but my 1-wire sensor is actually connected to Fibaro Door/Window sensor and not to LM4.
So, the problem is that the Z-Wave /apps/data/zwaveapp/ interface does not reads the data from that sensor. My 1-wire tab from LM4 is empty now (I have turned off the Z-Wave sensor), as you can see in the attached screenshot.
The sensor should appear here, even if it's not connected directly to LM4 to the 1-wire wired interface? Note that I want to have the temperature readout remotely, via the Fibaro Door/Window + temperature sensor.
(08.08.2016, 10:08)admin Wrote: Sensors will only appear if connected directly. If Z-Wave is not handling it properly then the issues is in the Z-Wave app.
In my current situation, I think there's a SW bug or a feature that needs to be added in a future update of the Z-Wave app.
I have put a picture in attachment with what I get inside the Z-Wave application. For example, the temperature in my room was around 28 degrees Celsius during testing and none of the values that can be read in the Z-Wave application are pointing to that value. Also, when I approach the magnet on the sensor, the "Access Control Object" is changing its "Current value" from 22 to 23. It would be good to change it from 0 to 1, as it's more logically defined.
The extra parameter that the Fibaro Door/Window sensor can read, is the temperature via the 1-wire sensor.
Is it possible to address these issues to the SW developer that it's handling the Z-Wave application, so that we have this fixed in a future Z-Wave app upgrade?
(09.08.2016, 18:39)andeug Wrote: Yes, I've did the wirings to the sensor first and then added it into LM. It's strange that I cannot read the temperature in the Z-Wave application...
i can try this when im back at the office in 3 weeks.
Strange. I don't get Temperature Object in my sensor. See the enclosed image.
My sensor is connected exactly as you see it in the pictures. Did you connected yours with the same wirings and colours?
10.10.2016, 14:07 (This post was last modified: 10.10.2016, 14:11 by andeug.)
Hi,
Do you get the same menus as the ones I get when I mount my Fibaro door sensor?
See the enclosed pictures. I get more than you:
Sensor object- why you have 2?
Alarm type object
Alarm level object
SourceNodeId object
Access Control object - read the commend below about this parameter
Burglar object Temperature object Battery Level object General object
What is in GREEN, we both have. What is marked in RED, I am missing on my Z-Wave application.
How did you added/deleted the other ones? I was thinking to ask your help with below:
1. delete your Z-Wave Fibaro sensor and remove the temperature sensor
2. add it back again without mounting the temperature sensor. What will you get?
3. mount the temperature sensor. Will extra objects will be added?
Another thing is that Access Control object is changing its status from 22 to 23, depending on the magnet, if it's closer to Fibaro sensor or away from it. (door closed/open)
Maybe Edgars can help with a troubleshooting feedback. I could disable the 1-wire sensor and try connecting it directly to LM4. to see if it works.
Other else, can be a firmware issue on the Fibaro door/temperature sensor itself? Any clues?
11.10.2016, 10:09 (This post was last modified: 11.10.2016, 10:11 by andeug.)
(11.10.2016, 09:36)gjniewenhuijse Wrote: Please post your device parameters under advanced tab.
You can see all the parameters from the Advanced tab. Anything suspicious there?
I have sent today an e-mail to Fibaro Support, maybe they can help me with a feedback regarding the problem I am experiencing.
I will keep you posted as soon as I will get an update.
(11.10.2016, 09:36)gjniewenhuijse Wrote: Please post your device parameters under advanced tab.
You can see all the parameters from the Advanced tab. Anything suspicious there?
I have sent today an e-mail to Fibaro Support, maybe they can help me with a feedback regarding the problem I am experiencing.
I will keep you posted as soon as I will get an update.
I see something strange after device properties #5, thats not correct. Please ask admin or the zwave developer to login into your device to see whats wrong in de zwave config.
See my device properties attached.
Looks like its not fully included, normaly at include time all parameters are transported, but it looks like he doesn't recognize your device as a fibaro doorsensor.
