korgboll

Aangemaakte reacties

5 berichten aan het bekijken - 1 tot 5 (van in totaal 5)
  • Auteur
    Berichten
  • In reactie op: Event with Fibaro Mension Sensor #3943
    korgboll
    Bijdrager

    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

    • Deze reactie is gewijzigd 4 jaren, 12 maanden geleden door korgboll.
    In reactie op: Event with Fibaro Mension Sensor #3921
    korgboll
    Bijdrager

    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, 
    
    In reactie op: How to update PulseStation #3918
    korgboll
    Bijdrager

    Thank you,

    I was only testing the raspberry Pi for fun. Probably made something wrong during the setup.
    Did notice however that the permissions, which I changed with chmod 777 was reset after the failed update.

    I have a setup working on my Synology so I put the Raspberry Pi back in the drawer.

    Best regards
    /Thomas

    In reactie op: How to update PulseStation #3900
    korgboll
    Bijdrager

    Tried it on Raspbian but still unable to upgrade from 1.2.

    Though replaced the path with /usr/share/PulseStation/*

    In reactie op: device properties are not kept #1371
    korgboll
    Bijdrager

    I had the same problem when adding/changing Sonos devices. Could not save new parameters or delete the devices (just add new sonos).

    Installing MariaDB on my Synology solved the problem for me!

    Thanks
    /Thomas

5 berichten aan het bekijken - 1 tot 5 (van in totaal 5)