smStatus geht nicht

Begonnen von rpeters, 12 September 2015, 22:59:04

Vorheriges Thema - Nächstes Thema

rpeters

Hallo

Entschuldigung fuer mein Nachricht auf Englisch, ich schreib nur ein bisschen Deutsch. Sie duerfen auf Deutsch antworten.

I have raspberry pi2 with razberry module, some sensors and fhem (fully updated)
Every sensor has all possible association groups set to the controller.

The sensors are:
Zipato Multi sensor duo (motion, temperature) (which is a 0109-2002-0205 Vision ZP3102 EU PIR Motion Sensor according to fhem)  (id's : 0b, 09, 05)
Fibaro multisensor (motion, temperature, luminance) (id: 03)

The sensors work fine as motion sensor. If there is motion they immediately send a message.

However:
In the zipato sensor manual it states: "Notice: The user needs to initiate temperature readings manually, from the controller, except when temperature changes 2 degrees (+/-), when sensor will automatically report readings to controller."
The automatic part works.
The manual part does not. (or I am doing something wrong)

I believe the temperature sensor is in the command class MULTILEVEL_SENSOR, so when I issue the command "get zip01 smStatus" it should report temperature when it wakes up.
The command is sent to the sensor according to the fhem logs (see below), but no answer is received.
This is the first problem.

The second problem is that the last ACK is almost always missing. That is the ACK to the 'wakeupNoMoreInformation' gets lost most of the time.


2015.09.12 22:06:49.597 4: ZWDongle_Read ZWAVE1: sending ACK, processing 0004000b028407
2015.09.12 22:06:49.598 5: SW: 06
2015.09.12 22:06:49.600 5: ZWAVE1 dispatch 0004000b028407
2015.09.12 22:06:49.601 4: ZWAVE1 CMD:APPLICATION_COMMAND_HANDLER ID:0b ARG:028407
2015.09.12 22:06:49.602 5: ZWDongle_Write 00 130b023104250b
2015.09.12 22:06:49.603 5: SW: 010900130b023104250bf7
2015.09.12 22:06:49.620 5: ACK received, removing 010900130b023104250bf7 from dongle sendstack
2015.09.12 22:06:49.621 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:06:49.621 5: SW: 06
2015.09.12 22:06:49.623 5: ZWAVE1 dispatch 011301
2015.09.12 22:06:49.706 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00130b00000a
2015.09.12 22:06:49.707 5: SW: 06
2015.09.12 22:06:49.709 5: ZWAVE1 dispatch 00130b00000a
2015.09.12 22:06:49.709 4: ZWAVE1 CMD:ZW_SEND_DATA ID:00 ARG:000a
2015.09.12 22:06:49.710 4: ZWAVE1 transmit OK for 0b
2015.09.12 22:06:50.268 5: ZWDongle_Write 00 130b023104250b
2015.09.12 22:06:50.269 5: SW: 010900130b023104250bf7
2015.09.12 22:06:50.796 5: ACK received, removing 010900130b023104250bf7 from dongle sendstack
2015.09.12 22:06:50.796 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:06:50.797 5: SW: 06
2015.09.12 22:06:50.799 5: ZWAVE1 dispatch 011301
2015.09.12 22:06:50.801 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00130b000004
2015.09.12 22:06:50.802 5: SW: 06
2015.09.12 22:06:50.803 5: ZWAVE1 dispatch 00130b000004
2015.09.12 22:06:50.804 4: ZWAVE1 CMD:ZW_SEND_DATA ID:00 ARG:0004
2015.09.12 22:06:50.804 4: ZWAVE1 transmit OK for 0b
2015.09.12 22:06:51.103 5: ZWDongle_Write 00 130b023104250b
2015.09.12 22:06:51.104 5: SW: 010900130b023104250bf7
2015.09.12 22:06:51.107 5: ACK received, removing 010900130b023104250bf7 from dongle sendstack
2015.09.12 22:06:51.111 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:06:51.111 5: SW: 06
2015.09.12 22:06:51.113 5: ZWAVE1 dispatch 011301
2015.09.12 22:06:51.165 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00130b000006
2015.09.12 22:06:51.165 5: SW: 06
2015.09.12 22:06:51.167 5: ZWAVE1 dispatch 00130b000006
2015.09.12 22:06:51.167 4: ZWAVE1 CMD:ZW_SEND_DATA ID:00 ARG:0006
2015.09.12 22:06:51.168 4: ZWAVE1 transmit OK for 0b
2015.09.12 22:06:51.470 5: ZWDongle_Write 00 130b023104250b
2015.09.12 22:06:51.471 5: SW: 010900130b023104250bf7
2015.09.12 22:06:51.474 5: ACK received, removing 010900130b023104250bf7 from dongle sendstack
2015.09.12 22:06:51.477 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:06:51.478 5: SW: 06
2015.09.12 22:06:51.479 5: ZWAVE1 dispatch 011301
2015.09.12 22:06:51.516 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00130b000004
2015.09.12 22:06:51.517 5: SW: 06
2015.09.12 22:06:51.518 5: ZWAVE1 dispatch 00130b000004
2015.09.12 22:06:51.519 4: ZWAVE1 CMD:ZW_SEND_DATA ID:00 ARG:0004
2015.09.12 22:06:51.519 4: ZWAVE1 transmit OK for 0b
2015.09.12 22:06:53.527 5: ZWDongle_Write 00 130b028408250b
2015.09.12 22:06:53.528 5: SW: 010900130b028408250b4e
2015.09.12 22:06:53.530 5: ACK received, removing 010900130b028408250b4e from dongle sendstack
2015.09.12 22:06:53.534 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:06:53.535 5: SW: 06
2015.09.12 22:06:53.536 5: ZWAVE1 dispatch 011301
2015.09.12 22:06:58.633 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00130b0101fe
2015.09.12 22:06:58.634 5: SW: 06
2015.09.12 22:06:58.635 5: ZWAVE1 dispatch 00130b0101fe
2015.09.12 22:06:58.636 4: ZWAVE1 CMD:ZW_SEND_DATA ID:01 ARG:01fe
2015.09.12 22:06:58.636 2: ZWAVE1 transmit NO_ACK for 0b




Now if I request battery instead of smStatus, it works:  (first smStatus is send, then battery)


2015.09.12 22:38:27.753 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00040005028407
2015.09.12 22:38:27.753 5: SW: 06
2015.09.12 22:38:27.755 5: ZWAVE1 dispatch 00040005028407
2015.09.12 22:38:27.756 4: ZWAVE1 CMD:APPLICATION_COMMAND_HANDLER ID:05 ARG:028407
2015.09.12 22:38:27.757 5: ZWDongle_Write 00 13050231042505
2015.09.12 22:38:27.758 5: SW: 01090013050231042505f7
2015.09.12 22:38:27.776 5: ACK received, removing 01090013050231042505f7 from dongle sendstack
2015.09.12 22:38:27.777 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:38:27.777 5: SW: 06
2015.09.12 22:38:27.779 5: ZWAVE1 dispatch 011301
2015.09.12 22:38:28.007 4: ZWDongle_Read ZWAVE1: sending ACK, processing 001305000019
2015.09.12 22:38:28.008 5: SW: 06
2015.09.12 22:38:28.009 5: ZWAVE1 dispatch 001305000019
2015.09.12 22:38:28.010 4: ZWAVE1 CMD:ZW_SEND_DATA ID:00 ARG:0019
2015.09.12 22:38:28.011 4: ZWAVE1 transmit OK for 05
2015.09.12 22:38:28.313 5: ZWDongle_Write 00 13050280022505
2015.09.12 22:38:28.313 5: SW: 0109001305028002250540
2015.09.12 22:38:28.316 5: ACK received, removing 0109001305028002250540 from dongle sendstack
2015.09.12 22:38:28.320 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:38:28.320 5: SW: 06
2015.09.12 22:38:28.322 5: ZWAVE1 dispatch 011301
2015.09.12 22:38:28.460 4: ZWDongle_Read ZWAVE1: sending ACK, processing 00130500000e
2015.09.12 22:38:28.461 5: SW: 06
2015.09.12 22:38:28.462 5: ZWAVE1 dispatch 00130500000e
2015.09.12 22:38:28.463 4: ZWAVE1 CMD:ZW_SEND_DATA ID:00 ARG:000e
2015.09.12 22:38:28.463 4: ZWAVE1 transmit OK for 05
2015.09.12 22:38:28.585 4: ZWDongle_Read ZWAVE1: sending ACK, processing 0004000503800364
2015.09.12 22:38:28.586 5: SW: 06
2015.09.12 22:38:28.587 5: ZWAVE1 dispatch 0004000503800364
2015.09.12 22:38:28.588 4: ZWAVE1 CMD:APPLICATION_COMMAND_HANDLER ID:05 ARG:03800364
2015.09.12 22:38:30.381 5: ZWDongle_Write 00 13050284082505
2015.09.12 22:38:30.382 5: SW: 010900130502840825054e
2015.09.12 22:38:30.384 5: ACK received, removing 010900130502840825054e from dongle sendstack
2015.09.12 22:38:30.388 4: ZWDongle_Read ZWAVE1: sending ACK, processing 011301
2015.09.12 22:38:30.389 5: SW: 06
2015.09.12 22:38:30.390 5: ZWAVE1 dispatch 011301
2015.09.12 22:38:36.534 4: ZWDongle_Read ZWAVE1: sending ACK, processing 001305010267
2015.09.12 22:38:36.535 5: SW: 06
2015.09.12 22:38:36.537 5: ZWAVE1 dispatch 001305010267
2015.09.12 22:38:36.537 4: ZWAVE1 CMD:ZW_SEND_DATA ID:01 ARG:0267
2015.09.12 22:38:36.538 2: ZWAVE1 transmit NO_ACK for 05


The fibaro sensor has the same problem, it does not respond to my smStatus request. It does have more options to report automatically at smaller temperature changes, so this is less of a problem, but still strange?

Is it mandatory for multilevel sensors to report all values from all sensors when you send "get sensorname smStatus" ?



rudolfkoenig

No need to apologize for english.
I have no answer to your first question, I also have a sensor which won't answer a documented config request, by simply ignoring it.

In your first log the smStatus ist sent more then once (4-times?), each after less than a second. Did you queued 4 requests?
The device seems to drop the requests, and the ZWDongle notifies FHEM after receiving no ACK from the device.

ZitatIs it mandatory for multilevel sensors to report all values from all sensors when you send "get sensorname smStatus" ?
No idea, you should ask this in some official ZWave forum and report the answer here :)

rpeters

Zitat von: rudolfkoenig am 13 September 2015, 11:29:48
In your first log the smStatus ist sent more then once (4-times?), each after less than a second. Did you queued 4 requests?
Yes, I should have written that down more clearly. I queued some get requests. It does however make no difference if there is only one or multiple.

Zitat von: rudolfkoenig am 13 September 2015, 11:29:48
The device seems to drop the requests, and the ZWDongle notifies FHEM after receiving no ACK from the device.
If I read the logs correctly it receives the smStatus request (and ACK's it) and the only thing it does not ACK is the last command (wakeupNoMoreInformation).
This happens most of the time, but not always.

I am wondering if anyone has seen this problem before?

Do you know of a brand of sensor that have a better/nicer implementation?

rudolfkoenig

No, I am by no means a device expert.