Installation Problem

[pofs]

I think you need to replace your RaZberry card. It seems to have wrong firmware loaded.

[PoltoS]

It seems you have one of the deffective boards manufactured last year 2013. We thought we have revoked all of them. Please ask for RMA with your supplier to exchange it.

[marih]

I've similar problems on an existing installation after update to 1.7.0 (and following downgrade 1.5.0.rc3)

I've a Razberry board which worked fine for several months. When I updated to version 1.7.0. z-way-server wouldn't start anymore and the logging is reporting the "Device is not compatible. Terminating…" issue.

Reboot wouldn't fix the issue, so I decided to rollback to version 1.5.0.rc3. But this version which has run stable for several weeks now, has become unstable as well.

After a successful start, with the 'expected correct values" in the logging:
==================
[2014-06-05 21:17:21.112] SETDATA controller.data.APIVersion = "04.02"
[2014-06-05 21:17:21.112] SETDATA controller.data.manufacturerId = 327 (0x00000147)
[2014-06-05 21:17:21.112] SETDATA controller.data.manufacturerProductType = 2 (0x00000002)
[2014-06-05 21:17:21.113] SETDATA controller.data.manufacturerProductId = 3 (0x00000003)
[2014-06-05 21:17:21.128] SETDATA controller.data.vendor = "RaZberry by Z-Wave.Me"
[2014-06-05 21:17:21.128] Supported Function Classes:
[2014-06-05 21:17:21.128] ---------------------------
[2014-06-05 21:17:21.128] 0x02 SerialAPIGetInitData
[2014-06-05 21:17:21.129] 0x03 SerialAPIApplicationNodeInformation
[2014-06-05 21:17:21.129] 0x04 ApplicationCommandHandler
[2014-06-05 21:17:21.129] 0x05 GetControllerCapabilities
…..
[2014-06-05 21:17:21.160] ---------------------------
[2014-06-05 21:17:21.161] Job 0x07 (Get controller info and supported function classes): success
[2014-06-05 21:17:21.161] Adding job: Set Serial API timeouts
[2014-06-05 21:17:21.161] Adding job: WatchDog Start
[2014-06-05 21:17:21.161] Adding job: Get home id and controller node id
=============
within 24 hours the system stops working and is again reporting the incompatible device message, the logging shows then:
=============
[2014-06-05 21:51:28.282] SETDATA controller.data.APIVersion = "00.00"
[2014-06-05 21:51:28.282] SETDATA controller.data.manufacturerId = 0 (0x00000000)
[2014-06-05 21:51:28.282] SETDATA controller.data.manufacturerProductType = 0 (0x00000000)
[2014-06-05 21:51:28.282] SETDATA controller.data.manufacturerProductId = 0 (0x00000000)
[2014-06-05 21:51:28.288] SETDATA controller.data.vendor = "Sigma Designs"
[2014-06-05 21:51:28.288] Supported Function Classes:
[2014-06-05 21:51:28.288] ---------------------------
[2014-06-05 21:51:28.288] 0xd2 WatchDogStart
[2014-06-05 21:51:28.288] 0xf0 UNKNOWN
[2014-06-05 21:51:28.288] 0xf1 UNKNOWN
[2014-06-05 21:51:28.289] 0xf2 ZMEFreqChange
[2014-06-05 21:51:28.289] 0xf3 ZMERestore
[2014-06-05 21:51:28.289] SETDATA controller.data.capabilities = int[5]
[2014-06-05 21:51:28.289] [00] 210
[2014-06-05 21:51:28.289] [01] 240
[2014-06-05 21:51:28.289] [02] 241
[2014-06-05 21:51:28.289] [03] 242
[2014-06-05 21:51:28.290] [04] 243
[2014-06-05 21:51:28.290] ---------------------------
[2014-06-05 21:51:28.290] Initialization done
[2014-06-05 21:51:28.290] Job 0x07 (Get controller info and supported function classes): success
[2014-06-05 21:51:28.290] Device is not compatible. Terminating…
=============

after some restarts/reboots and register clean with the echo command: echo -ne "x01x04x00x42x01xB8" > /dev/AMA0
it will run again for some hours. But after a while the whole story repeats.

Is this due to a defective board or is this something else?
I see in my logging many errors with a Meter get (v2) command:
===========
2014-06-05 06:26:11.308] Executing script: OpenRemote("/MeterValue/4/0/2", { ...
[2014-06-05 06:26:11.318] Adding job: Meter get (v2)
[2014-06-05 06:26:11.321] Adding job: Meter get (v2)
[2014-06-05 06:26:11.322] SENDING (cb 0x49): [2014-06-05 06:26:11.326] Executing script: OpenRemote("/MeterValue/4/0/0",
{ ...
( 01 0A 00 13 04 03 32 01 00 25 49 BE )
[2014-06-05 06:26:11.336] RECEIVED ACK
[2014-06-05 06:26:11.340] Adding job: Meter get (v2)
[2014-06-05 06:26:11.340] Job 0x13 (Meter get (v2)): removing duplicate
[2014-06-05 06:26:11.345] Executing script: OpenRemote("/SwitchBinaryStatus/17/1", { ...
[2014-06-05 06:26:11.353] RECEIVED: ( 01 04 01 13 00 E9 )
[2014-06-05 06:26:11.354] SENT ACK
[2014-06-05 06:26:11.356] Job 0x13 (Meter get (v2)): Could not be delivered to Z-Wave stack
[2014-06-05 06:26:11.362] Executing script: OpenRemote("/SwitchBinaryStatus/23/1", { ...
[2014-06-05 06:26:11.369] SENDING (cb 0x4a): ( 01 0A 00 13 04 03 32 01 00 25 4A BD )
[2014-06-05 06:26:11.393] RECEIVED ACK
[2014-06-05 06:26:11.393] Executing script: OpenRemote("/SwitchBinaryStatus/20/2", { ...
[2014-06-05 06:26:11.404] RECEIVED: ( 01 04 01 13 00 E9 )
[2014-06-05 06:26:11.404] SENT ACK
[2014-06-05 06:26:11.405] Job 0x13 (Meter get (v2)): Could not be delivered to Z-Wave stack
[2014-06-05 06:26:11.417] SENDING (cb 0x4b): ( 01 0A 00 13 04 03 32 01 00 25 4B BC )
[2014-06-05 06:26:11.427] RECEIVED ACK
[2014-06-05 06:26:11.438] RECEIVED: ( 01 04 01 13 00 E9 )
[2014-06-05 06:26:11.438] SENT ACK
[2014-06-05 06:26:11.439] Job 0x13 (Meter get (v2)): Could not be delivered to Z-Wave stack
[2014-06-05 06:26:11.439] Job 0x13 (Meter get (v2)): Removing job due to too much retransmitions
[2014-06-05 06:26:11.439] Job 0x13 (Meter get (v2)): fail
[2014-06-05 06:26:11.439] Removing job: Meter get (v2)
============
I'm not sure whether this is the cause of the z-way-server crash or a result of a failing z-way-server.

[PoltoS]

Your RaZberry seems to be dying... Maye be static discharge or something else killed it. sometimes it reports you wrong data:

[2014-06-05 21:51:28.288] Supported Function Classes:
[2014-06-05 21:51:28.288] ---------------------------
[2014-06-05 21:51:28.288] 0xd2 WatchDogStart
[2014-06-05 21:51:28.288] 0xf0 UNKNOWN
[2014-06-05 21:51:28.288] 0xf1 UNKNOWN
[2014-06-05 21:51:28.289] 0xf2 ZMEFreqChange
[2014-06-05 21:51:28.289] 0xf3 ZMERestore

This means device have not compatible functions to send packets and recieve them. This is a UART problem or chip problem. Try to clean your RaZberry with a 95% spirit. May be it will help. Or it was broken by ESD...