Things with Battery do not react


(Reinhard Müller) #1

Raspi 3B
Installation: Openhabian
openHAB 2.4.0 Build #1378
Aeotec Z-Stick Gen5
13 Things with 220V
3 Things with Fliers
6 Things with Battery

2 weeks ago I installed openhabian new on SD and had a lot of problems with Rules and the battery devices.
To limit the errors, last week I reinstalled everything on a new SD, without any rules.
The system is now running properly.
All 220Volt things and the fliers devices work.
Everyone, including the battery things are online.

Problems:
The door sensors Fibaro FGK101 zwave_version 2.5
Example Item:


Contact Tuersensor_SA "Saunatür ist[MAP(tuer.map):%s]"   <door>    {channel="zwave:device:512:node15:sensor_door1"}

Number Temperatursensor_SA "Pooltemperatur [%.1f °C]" <temperature>  {channel="zwave:device:512:node15:sensor_temperature2"} 

Number Batterie_SA "Batterie Türsensor [%d %%]" <battery-level> {channel="zwave:device:512:node15:battery-level"}

The flood Sensor Fibaro FGFS101 zwave_version 25.25
Example Item:


Switch Wassermelder_HR_Alarm "Wassermelder Heizung [MAP(wasser.map):%s]" <water {channel="zwave:device:512:node13:sensor_flood"}

Number Temperatursensor_HR "Temperatur Heizraum [%.1f °C]" <temperature>  {channel="zwave:device:512:node26:sensor_temperature2"}

Number Batterie_HZ  "Batterie Wassermelder HZ [%d %%]"   <battery-level>    { channel="zwave:device:512:node26:battery-level" }

The motion detector Fibaro FGMS001 zwave_version 2.7
Example Item:


Switch Bewegungsmelder_TE "Bewegung Terrasse [MAP(bew.map):%s]" <Motion> {channel="zwave:device:512:node22:alarm_motion"}

Number Temperatursensor_TE  "Terassentemperatur [%.1f °C]"  <temperature>   {channel="zwave:device:512:node22:sensor_temperature"}

Number Helligkeit_TE    "Helligkeit [%s Lux]"   <sun>                       {channel="zwave:device:512:node22:sensor_luminance"}

Number Batterie_TE  "Batterie Bewegungsmelder [%d %%]"   <battery-level>    { channel="zwave:device:512:node22:battery-level" }
 

are recognized after several wakes as known things.
In the properties all data incl.Hersteller and zwave version appear.
The BasicUI displays a status, a temperature, a battery level and so on.
But then there are no more status changes or sometimes very sporadic ones.

I’ve already ex- and includiert all things, The zwave binding deleted and reinstalled, but all to no avail.

Need urgent help.
In the German forum came so far no solution.
Thank you
reinhard


(Vincent Regaud) #2

Please use the code fences


(Markus Storm) #3

Delete and re-discover/re-create your things.
See this thread.


(Reinhard Müller) #4

I already did that, without success.


(Markus Storm) #5

Check the device associations to controller. Check wakeup times on your devices.
Re-initialize battery devices and watch the zwave log. Remember It can require many wakeups for reinitializations to work out.

Approach your problem in a systematic way, one device at a time:
enable zwave debugging, extract log entries for that ID and eventually use chris’ log viewer to get the communication flow displayed.


(Reinhard Müller) #6

How do I get to the var / log / openhab2 level in the zwave-log-viewer under “search for a file to add”?
This is not a problem in the terminal, but in the Finder (MAC) I come via “Go to > Connect to Server > 192.168.xxx.xx” only on the Openhabian level.


(Markus Storm) #7

How about copying it to your Mac first ?


(Reinhard Müller) #8

I have already thought of that, but I have been looking for a long time for a way to access the / var / directories via the Finder.


(Markus Storm) #9

Sorry but this forum is not a hotline. If you know how to access a Pi from a terminal, you should know how to copy files, too. And if you do not there’s G**gle.


(Reinhard Müller) #10

Sorry, I was not looking for a solution to copy, I was looking for a way in the Finder or in the zwave-log-viewer directly to the directory / var / log / openhab2 and G ** gle did not help me unfortunately.


(Reinhard Müller) #11

Why do I get the current time when copying the openhab.log file in the terminal, but in the Chris-Log viewer are the last entries about 70 minutes back?

What I have noticed so far, in the Log View are the Chris Log Viewer for all nodes no neighbors available.

Example Node 22 Motion Sensor:

Knoten 22
Benachrichtigungen
Nachrichten abgebrochen 0
Nachrichten NAKed 0
Nachbarn 0 gesamt, 0 hörend, 0 unbekannt
Gesendete Nachrichten 21
Nachrichten abgeschlossen nicht definiert
Zeitüberschreitung der Nachrichten 15 (72%)
Reaktionszeit 0/199/4056
Nachrichten empfangen nicht definiert

For the HABmin properties, Node 22 displays five neighbors

Here is the last entry in the Log Viewer (frontail) at http: // openhabianpi: 9001 from Node 22 after triggering a movement.

2018-10-02 16:23:00.187 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 16 03 20 01 00 C6 
2018-10-02 16:23:00.191 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 03 20 01 00 
2018-10-02 16:23:00.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 03 20 01 00 
2018-10-02 16:23:00.194 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-02 16:23:00.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:DONE)
2018-10-02 16:23:00.198 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: resetResendCount initComplete=true isDead=false
2018-10-02 16:23:00.200 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2018-10-02 16:23:00.201 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY not supported
2018-10-02 16:23:00.203 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2018-10-02 16:23:00.205 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 22: Basic report, value = 0
2018-10-02 16:23:00.207 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-02 16:23:00.209 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 0
2018-10-02 16:23:00.212 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:device:512:node22:alarm_tamper to OFF [OnOffType]
2018-10-02 16:23:00.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.
2018-10-02 16:23:00.217 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@f295a5.
2018-10-02 16:23:00.218 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-02 16:23:00.220 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-02 16:23:00.222 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-02 16:23:00.224 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

(Reinhard Müller) #12

I could solve that with the time problem. Copy error from me.


(Reinhard Müller) #13

By the motion detector, I found the following problem:
The channels are no longer correct.
When I connect the item of the motion detector to the alarm_tamper channel it reacts to movement (without touching)


(Reinhard Müller) #14

The door sensor comes with the following log at door opening:

2018-10-02 19:26:16.267 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 0E 03 20 01 FF 21

2018-10-02 19:26:16.271 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=14, callback=0, payload=00 0E 03 20 01 FF

2018-10-02 19:26:16.274 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=14, callback=0, payload=00 0E 03 20 01 FF

2018-10-02 19:26:16.276 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2018-10-02 19:26:16.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 14: Application Command Request (ALIVE:DONE)

2018-10-02 19:26:16.280 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: resetResendCount initComplete=true isDead=false

2018-10-02 19:26:16.282 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Incoming command class COMMAND_CLASS_BASIC, endpoint 0

2018-10-02 19:26:16.284 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: SECURITY not supported

2018-10-02 19:26:16.286 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Received COMMAND_CLASS_BASIC V1 BASIC_SET

2018-10-02 19:26:16.288 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 14: Basic report, value = 255

2018-10-02 19:26:16.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2018-10-02 19:26:16.293 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 255

2018-10-02 19:26:16.295 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 14: Commands processed 1.

2018-10-02 19:26:16.297 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 14: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@9850f6.

2018-10-02 19:26:16.299 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-10-02 19:26:16.301 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-10-02 19:26:16.303 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-02 19:26:16.305 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

In the Flood sensors appears neither in vibration, or contact with water, an entry in the log