ZWay start error

[holzemile]

I got this error on boot, ZWay is not running -.-[2013-11-17 16:37:05.001]   [78] 188[2013-11-17 16:37:05.001]   [79] 193[2013-11-17 16:37:05.002]   [80] 196[2013-11-17 16:37:05.002]   [81] 251[2013-11-17 16:37:05.002]   [82] 252[2013-11-17 16:37:05.002]   [83] 253[2013-11-17 16:37:05.002]   [84] 254[2013-11-17 16:37:05.002]   [85] 255[2013-11-17 16:37:05.002]   [86] 0[2013-11-17 16:37:05.003] ---------------------------[2013-11-17 16:37:05.003] Job 0x07 (Get controller info and supported function classes): success[2013-11-17 16:37:05.003] Device is not authorized. Terminating...[2013-11-17 16:37:05.003] Failed to join worker thread: 35[2013-11-17 16:37:05.003] Error returned from zway_fc_serial_api_set_timeouts(zway, 10, 10, NULL, NULL, NULL): Function class not supported by the hardware (-4)[2013-11-17 16:37:05.004] Error returned from zway_fc_watchdog_start(zway, NULL, NULL, NULL): Function class not supported by the hardware (-4)[2013-11-17 16:37:05.004] Adding job: Get home id and controller node id[2013-11-17 16:37:05.004] Removing job: Get controller info and supported function classes[2013-11-17 16:37:05.023] Worker thread exit pointfailed to discover ZWay: -9Z-Way version v1.3.1 from 2013-05-19 23:54:27 +0400 (build e717f1057ab76a00fa02d9e6546e360ad3390f36)Using default configuration file config.xmlStarting Z-Way for device /dev/ttyAMA0...Would be awesome if you could help me fix this, sorry for the lack of a spoiler, don't know how to put one here.Thanks

[mrlele]

I think you have a z-way from a bad batch. Did you just got it, the z-way?

[holzemile]

No, it was working for months… I just rebooted, and the error came up…

[holzemile]

EDIT: Sorry for double post…

[pz1]

Do a complete reinstall ? I know it is an awkward suggestion. I did it once with success in a similar situation.
On some cheaper SD cards RPi on uncontrolled reboot reportedly could cause errors.

[holzemile]

Rebooting (via "sudo reboot") doesn't help, but somehow it works now again after i shut it down ("sudo shutdown -h now") and unplugged and replugged power in again...
This is good, but it's not the first time that this failure came up, would be great if there's a way to solve the problem, because I'm not sure if it works this way next time.