Aeotec door sensor state does not change

      using 

Aeotec z stick gen 5, door sensor, openhab , habmin

door status always shows closed

curl http://localhost:80t/items/Door_Motion/state

always give

CLOSED

item file -

cat /usr/share/openhab/configurations/items/default.items

Contact Door_Motion “Window [%s]” (DollHouse) {zwave=“2:command=SENSOR_BINARY,refesh_interval=1,respond_to_basic=true”}

openhab.cfg has following configuration for z wave binding

zwave:port=/dev/ttyACM0

habmin shows door sensor with green circle as node 2

configuration parameters for node are set as -

send sensory binary reports on open close events - on for close, off for open

send basic also similar

door status value always comes as closed , even when door is open

Can you provide a debug log showing the problem - ie data being received from the device when the door is open and closed.

I would also remove the refresh_interval as it won’t do anything useful and could cause problems.

log.pdf (393.2 KB)

Thanks Cris, Kindly find log attached

Can you post the log as a text file please - I can’t easily process it as a PDF…

I do note a lot of duplicate messages in your log - are you running on an RPi? You might be suffering from the RPi problem :frowning:

Sorry Chris
I can’t upload text file as the website does not allow it.

I am using ubuntu trusty on 32 bit machine

Can you attach it somewhere and post the link then? I really can’t work with a PDF as I have tools to read the log - it doesn’t work with PDF.

can I email you the file, if you pls share email address
Regards
Parag

yes - it’s chris -at- cd-jackson.com

Got it… The duplication I saw isn’t duplication - it’s just you’re restarting the server a few times…

I really need a debug log to really see what’s happening - take a look in the wiki about how to change this (ie the zwave wiki page).

There are a lot of errors in this log though so you might like to try and resolve some of the exceptions such as address in use.

Chris,

I do not get Z WAVE logs, my logback.xml is as follows. I have enabled debug log. I am sending log file by email
best regards
Parag

<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> 
    <encoder> 
        <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern> 
    </encoder> 
</appender> 

<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> 
    <file>${openhab.logdir:-logs}/openhab.log</file> 
    <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> 
        <!-- weekly rollover and archiving --> 
        <fileNamePattern>${openhab.logdir:-logs}/openhab-%d{yyyy-ww}.log.zip</fileNamePattern> 
        <!-- maximum number of archive files to keep --> 
        <maxHistory>30</maxHistory> 
    </rollingPolicy> 
    <encoder> 
        <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern> 
    </encoder> 
</appender> 

<appender name="EVENTFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> 
    <file>${openhab.logdir:-logs}/events.log</file> 
    <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> 
        <!-- weekly rollover and archiving --> 
        <fileNamePattern>${openhab.logdir:-logs}/events-%d{yyyy-ww}.log.zip</fileNamePattern> 
        <!-- maximum number of archive files to keep --> 
        <maxHistory>30</maxHistory> 
    </rollingPolicy> 
    <encoder> 
        <pattern>%d{yyyy-MM-dd HH:mm:ss} - %msg%n</pattern> 
    </encoder> 
</appender> 

<logger name="runtime.busevents" level="INFO" additivity="false"> 
    <appender-ref ref="EVENTFILE" /> 
    <appender-ref ref="STDOUT" /> 
</logger> 



<logger name="org.openhab" level="DEBUG"/> 

<!-- this class gives an irrelevant warning at startup --> 
<logger name="org.atmosphere.cpr.AtmosphereFramework" level="ERROR" /> 

<!-- temporary workaround for https://github.com/openhab/jmdns/issues/12 --> 
<logger name="javax.jmdns" level="OFF"/> 

<!-- temporary workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=402750 --> 
<logger name="OSGi" level="OFF" /> 
 
<!-- temporary workaround to circumvent error messages with any obvious effect --> 
<logger name="org.atmosphere.cpr.AtmosphereFramework" level="OFF" /> 
<logger name="org.atmosphere.cpr.DefaultAnnotationProcessor" level="OFF" /> 
 
<root level="WARN"> 
    <appender-ref ref="FILE" /> 
    <appender-ref ref="STDOUT" /> 
</root> 
logs/zwave.log logs/zwave-%d{yyyy-ww}.log.zip 30 %d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}:%-4line]- %msg%n

logback.xml (3.0 KB)

Unfortunately the log you sent has no zwave data in it… Somehow this needs to get resolved - I would have thought updating the logback files (both debug and normal) with the data in the wiki should work?

I note though that the events log does have both open and closed entries though so I guess the state is updating at least occasionally?

2015-10-10 11:06:31 - Door_Motion state updated to OPEN
2015-10-10 11:23:17 - Door_Motion state updated to CLOSED

Chris,
if i have configuration parameter -
send sensory binary reports on open close events - on for open, off for close
I get state as OPEN

AND WHEN
send sensory binary reports on open close events - on for close, off for open
I get state as CLOSED

I changed the option , hence the event log shows both states but closing/opening of door does not trigger any chnage in state

Is this configuration change a device parameter (I assume so from your message, but just checking).

So is your problem simply that the device doesn’t send an update when it changes? If so, have you checked that the association is set correctly?

yes it is device parameter.

since i have only two nodes - controller and door sensor, i assumed i would not need association setting.
Please guide , is it required

Absolutely - associations are the mechanism zwave uses to notify the controller of changes. It doesn’t matter if you have 1, or 100 devices, if there is no association, then you won’t get updates.

Thanks a lot Chris

it works now. state is updated now

Great - glad it’s working :smile:

Chris You are very helpful . can’t thank you enough
Regards
Parag