Event with Fibaro Mension Sensor

Free domotica! Forums How can I …? Synology NAS Event with Fibaro Mension Sensor

This topic contains 40 replies, has 11 voices, and was last updated by  K.Rens 4 months, 3 weeks ago.

Viewing 11 posts - 31 through 41 (of 41 total)
  • Author
    Posts
  • #3861

    wtfssr
    Participant

    to answer my own question: yes, you have to reassign the device to the controller, no it is begin recognized correctly, after adjusting the xml file. thanks!

    #3889

    djandib
    Participant

    Sorry, I was away some days…

    Is your Event now detected correctly?

    #3921

    korgboll
    Participant

    Hi,

    Im having similar problems with my Fibaro Door Sensor (FGK 101).

    Input IN1 and Lifeline is associated with zwave-1 (controller) and sensor is updating ok (true/false).

    However I cannot get the Scene Event to fire.
    My scene look the same as the others in this thread (If Device Event == Event Device : Fibaro 1 Value : On
    do Log “Did this happened?”)

    I did not see the “Unhandled Command Class 0x60” in my event log.

    Below is an example of the z-wave service log.

    
    2016-11-23 20:13:20.341 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xe9f06f84
    2016-11-23 20:13:20.772 Detail, Node011,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0b, 0x03, 0x20, 0x01, 0xff, 0x24
    2016-11-23 20:13:20.772 Detail, 
    2016-11-23 20:13:20.772 Info, Node011, Received Basic set from node 11: level=255. Treating it as a Basic report.
    2016-11-23 20:13:20.773 Detail, 
    2016-11-23 20:13:20.773 Detail, Node011, Queuing (WakeUp) SensorBinaryCmd_Get (Node=11): 0x01, 0x09, 0x00, 0x13, 0x0b, 0x02, 0x30, 0x02, 0x25, 0xe2, 0x19
    2016-11-23 20:13:20.773 Detail, Node011, Refreshed Value: old value=true, new value=true, type=bool
    2016-11-23 20:13:20.773 Detail, Node011, Changes to this value are not verified
    2016-11-23 20:13:20.774 Detail, Node011, Notification: ValueChanged
    2016-11-23 20:13:20.993 Info, Notification: Value Changed - Add DB Record for device id zwave-11 and value id 48-user-bool-1-0 
    2016-11-23 20:13:21.046 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xe9f06f84
    2016-11-23 20:13:33.105 Detail, Node011,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0b, 0x03, 0x30, 0x03, 0x00, 0xc9
    2016-11-23 20:13:33.106 Detail, 
    2016-11-23 20:13:33.106 Info, Node011, Received SensorBinary report: Sensor:201 State=Off
    2016-11-23 20:13:33.106 Detail, Node011, Refreshed Value: old value=true, new value=false, type=bool
    2016-11-23 20:13:33.106 Detail, Node011, Changes to this value are not verified
    2016-11-23 20:13:33.106 Detail, Node011, Notification: ValueChanged
    2016-11-23 20:13:34.445 Info, Notification: Value Changed - Add DB Record for device id zwave-11 and value id 48-user-bool-1-0 
    2016-11-23 20:13:34.513 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xe9f06f84
    2016-11-23 20:13:37.183 Detail, Node011,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0b, 0x03, 0x20, 0x01, 0x00, 0xdb
    2016-11-23 20:13:37.183 Detail, 
    2016-11-23 20:13:37.184 Info, Node011, Received Basic set from node 11: level=0. Treating it as a Basic report.
    2016-11-23 20:13:37.184 Detail, 
    
    #3923

    djandib
    Participant

    Sorry, I don`t have the same sensor like yours.
    I have the AEOTEC. They have only one association (Report:Zwave-1)
    Check if you have something like “kind of Report”-> “Basic”, “Sensor”, “Basic and Sensor”.
    Try “Basic and Sensor”…

    Does the sensor works fine with the blockly “Comparator”?

    Greetings from Munich
    Andi

    #3943

    korgboll
    Participant

    Thanks for the tips.

    I tried to set the property “Scene activation” to enabled and after som trouble with getting it to sync i finally got an event in the zwave log.

    Though it doesnt trigger my Blockly scheme.

    The log says:
    2016-11-30 19:15:47.795 Info, Node011, Received Scene Activation set from node 11: scene id=10 via configuration. Sending event notification.
    2016-11-30 19:15:47.795 Detail, Node011, Notification: SceneEvent
    2016-11-30 19:15:47.795 Info, Notification: SceneEvent from zwave.cpp
    2016-11-30 19:15:47.797 Info, Notification: Send to scene service : php /volume1/web/PulseStation/services/core/../zwave/../core/core.php “1|zwave|scene|CHECKSCENESEVENT|zwave-11_EVENT_10”

    Or
    2016-11-30 22:20:41.114 Info, Notification: Send to scene service : php /volume1/web/PulseStation/services/core/../zwave/../core/core.php “1|zwave|scene|CHECKSCENESEVENT|zwave-11_EVENT_11”

    Should it not by zwave-11_ON / zwave-11_OFF instead of EVENT_11 / EVENT_10?

    If i test http://your.local.ip:4020/message=1|zwave|scene|CHECKSCENESEVENT|zwave-11_ON the Blockly scheme runs,
    http://your.local.ip:4020/message=1|zwave|scene|CHECKSCENESEVENT|zwave-11_EVENT10 does nothing

    • This reply was modified 1 year, 7 months ago by  korgboll.
    #3956

    Raven
    Participant

    Sorry for not having posted here about my testings, been on a business trip for some time so wasn’t able to really test what Koen sent me.

    After i’ve been back home and testing the files the error was still the same and even with the new zwave stack that was release some days ago i can’t get my motion sensor to work.
    Still “Unhandled Command Class”

    Happy to test some more if you have any new ideas Koen.
    If you need log files or screenshots of my config please don’t hesitate to ask

    Regards

    #4089

    leroymth
    Participant

    Hi,
    Still no news for solve “Unhandled Command Class 0x60” on Fibaro Mension Sensor?
    Regards.

    #11839

    LaplaceII
    Participant

    Hi,

    I have the same topic. Motion sensor is completely included. Associatoins and Blockly rules (Device Event==….) are assigned as recommended. However, I get no SceneEvent or anything else in the scene.log. Eventhough in the core.log I cannot find anything…

    Here my zwave.log:
    2018-02-12 21:41:19.384 Detail, Node028, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1c, 0x03, 0x30, 0x03, 0xff, 0x21
    2018-02-12 21:41:19.384 Detail,
    2018-02-12 21:41:19.384 Info, Node028, Received SensorBinary report: Sensor:33 State=On
    2018-02-12 21:41:19.385 Detail, Node028, Refreshed Value: old value=false, new value=true, type=bool
    2018-02-12 21:41:19.385 Detail, Node028, Changes to this value are not verified
    2018-02-12 21:41:19.385 Detail, Node028, Notification: ValueChanged
    2018-02-12 21:41:19.553 Info, Notification: Value Changed – Add DB Record for device id zwave-28 and value id 48-user-bool-1-0
    2018-02-12 21:41:19.816 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xe608a98b
    2018-02-12 21:41:50.034 Detail, Node028, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1c, 0x03, 0x30, 0x03, 0x00, 0xde
    2018-02-12 21:41:50.034 Detail,
    2018-02-12 21:41:50.034 Info, Node028, Received SensorBinary report: Sensor:222 State=Off
    2018-02-12 21:41:50.034 Detail, Node028, Refreshed Value: old value=true, new value=false, type=bool
    2018-02-12 21:41:50.034 Detail, Node028, Changes to this value are not verified
    2018-02-12 21:41:50.035 Detail, Node028, Notification: ValueChanged
    2018-02-12 21:41:50.196 Info, Notification: Value Changed – Add DB Record for device id zwave-28 and value id 48-user-bool-1-0
    2018-02-12 21:41:50.464 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xe608a98b

    Is there any workaround/solution for this?

    THX
    Michael

    #11841

    djandib
    Participant

    Hi Michael,
    i solved it with simply blocky rules:
    blocky

    Yes, I know: in worst case you have to wait 59 seconds…
    Does this help you?

    Andi

    #11845

    LaplaceII
    Participant

    Hi Andi,

    I tested it in combination with a Pushover message (Message priority: Emergency). It did not work. I changed the Priority to high -> worked!
    Nevertheless I would like to get direct message with DeviceEvent==

    Thanks for your support
    Michael

    #11851

    K.Rens
    Keymaster

    Hi Michael,

    Pushover changed their requirements for emergency priority messages.
    It’s not that easy to implement it on our side as well, but will see what I can do.

    For the device event: I agree, I have to look into that again.

    Kind regards,
    K.Rens

Viewing 11 posts - 31 through 41 (of 41 total)

You must be logged in to reply to this topic.