official forum

v2.2.4-rc17 . I use this version beause It fix the problem with Fibaro Motion Sensor v3.2

Hi all, I have a problem with Fibaro Window/Door sensor v3.2. Inclusion failed and device is ON permanently and notifications aren't captured. Exclude and re-include same result: [2016-10-04 23:17:51.637] [I] [core] Creating device battery ZWayVDev_zway_11-0-128 [2016-10-04 23:17:51.657] [I] [core] ...

Any news? I can't get the motion detection to work with my sensor either (3.2). Have you messed around with associations for the device at all? Read somewhere here that someone claimed to have made it work properly by configuring associations for the motion group. The problem has been confirmed fro...

I have a same problem: viewtopic.php?f=3422&t=20393&start=40#p62963

Ok, thank you pz1.

Wikibear wrote:Via Webpage or try github.com.

Ok, thank you.

Wikibear wrote:This setting was not delivered. OK there is something strange. Contact support of RaZberry think it's the best way now.

Ok, thanks so much.

What is the best way to contact them?

OK, ok did you try to get closer to your controller? You can show via expert Ui queue of messages. Check this please. Yes, I checked at 1 meter to controller. https://s31.postimg.org/7fh66vror/queue_log.jpg share image z-way-server.log: [2016-07-20 15:06:11.669] [D] [zway] RECEIVED: ( 01 07 00 13 4...

Wikibear wrote:Can you show Screenshot of configuration page via expert Ui?

Parameter 26 is don't saved. I try to awake device but never saved.

subir imagenes gratis

No 2.7 after 3m get Network error. That's why I ask you to put this device direct in range to controller for testing. Did you get any log entry's? Did you send all settings to device? The problem is with 3.2 version (Node 15), I have other device 2.7 (Node 2) version and work fine. https://s32.post...