Coyote

Toutes mes réponses sur les forums

15 sujets de 1 à 15 (sur un total de 52)
  • Auteur
    Messages
  • en réponse à : pushover not working #2569
    Avatar
    Coyote
    Membre

    As K.Rens said, we have issues with this block.

    You’re like Guillaume (Fibaro smoke sensor post), like Leroymth (janvier 21, 2016 at 11:39) , like Coldbringer and like me..

    Mika knows and is working on association problem..He has an access to my system.
    We have to wait to find the solution 😉

    JMarc

    en réponse à : pushover not working #2565
    Avatar
    Coyote
    Membre

    Now you’re face on the same problem we have for the moment with the ‘device event block’ …

    en réponse à : pushover not working #2560
    Avatar
    Coyote
    Membre

    Try to remove the ’emergency mode’ in the ‘pushover’ bloc.. Leave the ‘normal mode’ in the priority box.

    JM

    en réponse à : pushover not working #2558
    Avatar
    Coyote
    Membre

    ok,

    1) ‘add log’ block is at the end of the ‘util’ panel, and will add a text in the scene.log (if the loop is correct)
    2) You have to add PushOver on your cellphone (PlayStore for exemple), and check that your device is added on your PushOver acount on the web (In ‘Your devices’ list)
    3) Get your USER Key and API Token key from your PushOver account
    3) Make sure that pushover service is started in PulseStation, and that you’ve put the right token and user key caracters in the property tab.
    4) Your simple rule seems to be great.. It should work if you do all this steps before..

    Good luck 😉

    JMarc

    en réponse à : pushover not working #2556
    Avatar
    Coyote
    Membre

    Hi,

    I think this is not a pushover problem. To see that, try to make a rule with only pushover (If time = xx: xx then … Pushover)… and maybe you’ll receive your notification.
    Put ‘Add log’ block in your scene too, and you’ll see if the loop is oki or not.

    I think that your problem comes from ‘Device event’ block.. Many people have problem with this block that stop well working with the last version of PulseStation.
    Try to watch your ‘scene.log’ and ‘core.log’ to see if you can find something with ‘event’ inside …

    I think that Mika is aware about this. 😉

    JMarc

    en réponse à : Virtual url bug? #2394
    Avatar
    Coyote
    Membre

    Hi,

    If I can advise you, let PuseStation makes all the dashboard alone with the ‘generate pannels’ button, and make your modifications after that.
    If you do that, you’ll have the specific line to activate your VDevice in the action property of the button.

    Here is a screenshot with my config. I use it to send commands to a Teracom controler, and it works well :

    http://upandpost.com/image/view/7/9fc166f2ad86c764848fd39fc7bd89e.jpg

    JMarc

    en réponse à : Aeotec Z-Stick not working with either USB-Port #2373
    Avatar
    Coyote
    Membre

    Hi,

    Maybe you can try with /dev/ttyACM1 (or /dev/ttyUSB1).

    With my DS213j, I have to switch between ttyACM1 and ttyACM0 at each reboot of the NAS.

    JMarc

    en réponse à : Make a 'fast' bocky rule #2314
    Avatar
    Coyote
    Membre

    Oki, I’ve sent links in your email Contact.

    Many thanks

    JMarc

    en réponse à : Problem with Scene and random timer #2311
    Avatar
    Coyote
    Membre

    Hi Mika,

    I’ve tried to put a timer in a timer, but there is still a problem in the second loop.
    You can’t use any other block in the second timer, otherwise the scene stop running (no launches with scene service).

    There is a problem with virtual device new value (blue) block, Zwave device new value (blue) block, and pushOver block.
    For the moment, it only works with “add log blocks”, or “set item variable block” inside the second loop..

    So I’m still blocked.. 🙂

    JMarc

    en réponse à : Problem with Scene and random timer #2301
    Avatar
    Coyote
    Membre

    Hi,

    Thanks a lot for your help, I’ll try again with timers.

    Just another thing about the timer block : You can’t also put a ‘set variable block’ inside it.
    If you do that, scene service doesn’t execute blocks inside the timer….

    JMarc

    en réponse à : Make a 'fast' bocky rule #2290
    Avatar
    Coyote
    Membre

    Hi,

    Oki, but what’s your advise ? Should I wait because it’s a bug ?
    Is there something I can test ? (Is this the new scene service, or the new Zwave library ? Can I put an old version of PS to see something ?)
    I’ve already done many associations,installations and put news associtations in the new “association tab” with my Gen 5 stick… But there is no changes.

    I was used to use this “Device Event” block with this sensors before, and I’ve not changing my hardware..

    What can I do ?

    Many thanks

    JMarc

    en réponse à : Problem with Scene and random timer #2289
    Avatar
    Coyote
    Membre

    Hi,

    There are many problems with timers.

    1) If I want to use the “sleep block” in a timer (manual or random) block, it makes bugs with the scene service. Here a simple example :

    http://upandpost.com/image/view/7/5f8f4b8cceebbd1a99a41f83ac4faf2.jpg

    In this case, it makes a loop in the timer block during the sleeping time, and after that, scene service is totaly lost with the scene, and redo it many times each minute. Here is the associated log :

    2016-01-01 21:11:00 Periodic : Start
    2016-01-01 21:11:00 Periodic : End
    2016-01-01 21:11:01 Boucle1
    2016-01-01 21:12:00 Periodic : Start
    2016-01-01 21:12:00 Periodic : End
    2016-01-01 21:12:01 Boucle1
    2016-01-01 21:12:01 Boucle2
    2016-01-01 21:13:00 Boucle3
    2016-01-01 21:14:00 Boucle3
    2016-01-01 21:15:00 Boucle3
    2016-01-01 21:16:00 Boucle3
    2016-01-01 21:16:00 Periodic : Start
    2016-01-01 21:16:01 Periodic : End
    2016-01-01 21:16:01 Boucle1
    2016-01-01 21:17:00 Periodic : Start
    2016-01-01 21:17:00 Periodic : Start
    2016-01-01 21:17:01 Periodic : End
    2016-01-01 21:17:01 Periodic : End
    2016-01-01 21:17:02 Boucle1
    2016-01-01 21:17:02 Boucle1
    2016-01-01 21:18:00 Periodic : Start
    2016-01-01 21:18:00 Periodic : End
    2016-01-01 21:18:01 Boucle1

    2) If I want to use multiple timers (Timer in a timer) like this example :

    http://upandpost.com/image/view/3/e609c4869b6656e1bec3b6a14a61a9c.jpg

    I have two options :
    2-1) Scene service stop to run this scene, with nothing at all in the log file
    2-2) The scene works, but makes a infinite loop.. here is the log :

    2016-01-01 21:55:00 Periodic : Start
    2016-01-01 21:55:01 Periodic : End
    2016-01-01 21:55:01 Boucle 0
    2016-01-01 21:56:01 Periodic : Start
    2016-01-01 21:56:01 Periodic : End
    2016-01-01 21:56:01 Boucle 0
    2016-01-01 21:57:01 Periodic : Start
    2016-01-01 21:57:01 Periodic : End
    2016-01-01 21:57:01 Boucle 0
    2016-01-01 21:57:01 Time ok
    2016-01-01 21:58:01 Time +1 min
    2016-01-01 21:59:01 Time +1 min
    2016-01-01 22:00:02 Time +1 min
    2016-01-01 22:01:01 Time +1 min
    2016-01-01 22:02:01 Time +1 min
    2016-01-01 22:03:01 Time +1 min
    2016-01-01 22:04:01 Time +1 min
    2016-01-01 22:05:01 Time +1 min
    2016-01-01 22:06:02 Time +1 min
    2016-01-01 22:07:01 Time +1 min
    2016-01-01 22:08:02 Time +1 min
    2016-01-01 22:09:00 Time +1 min
    2016-01-01 22:10:00 Time +1 min
    2016-01-01 22:11:00 Time +1 min

    … Not easy to find a working solution… I’ll try with a test on the real time..

    JMarc

    en réponse à : Problem with Scene and random timer #2278
    Avatar
    Coyote
    Membre

    Hi,

    Here is my scene with “add log” comments to see what Scene service do :

    http://upandpost.com/image/view/4/328fc8ebd22555c093d70ae840b6f28.jpg#code_forums

    And the results are very strange :

    2015-12-30 17:30:01 Periodic : Start
    2015-12-30 17:30:01 Periodic : End
    2015-12-30 17:30:02 Avant boucle
    2015-12-30 17:31:01 Periodic : Start
    2015-12-30 17:31:02 Periodic : End
    2015-12-30 17:31:02 Avant timer
    2015-12-30 17:31:02 Avant boucle
    2015-12-30 17:32:01 Periodic : Start
    2015-12-30 17:32:02 Periodic : End
    2015-12-30 17:32:02 Avant boucle
    2015-12-30 17:33:01 Periodic : Start
    2015-12-30 17:33:02 Periodic : End
    2015-12-30 17:33:02 Avant boucle
    2015-12-30 17:34:01 Periodic : Start
    2015-12-30 17:34:01 Periodic : End
    2015-12-30 17:34:02 Avant boucle
    2015-12-30 17:35:01 Periodic : Start
    2015-12-30 17:35:01 Periodic : End
    2015-12-30 17:35:02 Avant boucle
    2015-12-30 17:36:01 Periodic : Start
    2015-12-30 17:36:02 Periodic : End
    2015-12-30 17:36:02 Avant boucle
    2015-12-30 17:37:01 Periodic : Start
    2015-12-30 17:37:01 Periodic : End
    2015-12-30 17:37:02 Avant boucle
    2015-12-30 17:38:02 Avant sleep2
    2015-12-30 17:39:02 Avant sleep2
    2015-12-30 17:40:02 Apres sleep2
    2015-12-30 17:40:03 Avant sleep6
    2015-12-30 17:40:04 Avant sleep2
    2015-12-30 17:41:01 Avant sleep2
    2015-12-30 17:41:02 Apres sleep2
    2015-12-30 17:41:03 Avant sleep6
    2015-12-30 17:42:01 Avant sleep2
    2015-12-30 17:42:04 Apres sleep2
    2015-12-30 17:42:05 Avant sleep6
    2015-12-30 17:43:01 Avant sleep2
    2015-12-30 17:43:01 Apres sleep2
    2015-12-30 17:43:02 Avant sleep6
    2015-12-30 17:44:01 Apres sleep2
    2015-12-30 17:44:02 Avant sleep2
    2015-12-30 17:44:03 Avant sleep6
    2015-12-30 17:45:01 Apres sleep2
    2015-12-30 17:45:01 Avant sleep2
    2015-12-30 17:45:02 Avant sleep6
    2015-12-30 17:46:01 Avant sleep2
    2015-12-30 17:46:02 Apres sleep2
    2015-12-30 17:46:03 Apres sleep6
    2015-12-30 17:46:03 Periodic : Start
    2015-12-30 17:46:03 Avant sleep6
    2015-12-30 17:46:03 Periodic : End
    2015-12-30 17:46:04 Avant boucle
    2015-12-30 17:47:00 Periodic : Start
    2015-12-30 17:47:01 Periodic : End
    2015-12-30 17:47:01 Avant boucle
    2015-12-30 17:47:01 Apres sleep2
    2015-12-30 17:47:02 Avant sleep6
    2015-12-30 17:47:03 Apres sleep6
    2015-12-30 17:47:03 Periodic : Start
    2015-12-30 17:47:03 Periodic : End
    2015-12-30 17:47:03 Avant boucle
    2015-12-30 17:48:00 Periodic : Start
    2015-12-30 17:48:01 Periodic : End
    2015-12-30 17:48:01 Apres sleep2
    2015-12-30 17:48:01 Avant boucle
    2015-12-30 17:48:02 Avant sleep6
    2015-12-30 17:48:05 Apres sleep6
    2015-12-30 17:48:05 Periodic : Start
    2015-12-30 17:48:05 Periodic : End
    2015-12-30 17:48:05 Avant boucle

    I avoid you all the notifications I get with my loops… 🙂

    JMarc

    en réponse à : Make a 'fast' bocky rule #2276
    Avatar
    Coyote
    Membre

    Hi,

    I’ve done several totaly new installations of PS, and several new zwave associations (With services restarts)… And I think I haven’t got zwave problem.

    Here is the Zwave log when the sensor detect something :

    2015-12-31 11:00:10.384 Info, Node004, Received SensorBinary report: Sensor:57 State=On
    2015-12-31 11:00:10.384 Detail, Node004, Refreshed Value: old value=false, new value=true, type=bool
    2015-12-31 11:00:10.384 Detail, Node004, Changes to this value are not verified
    2015-12-31 11:00:10.384 Detail, Node004, Notification: ValueChanged
    2015-12-31 11:00:10.550 Info, Notification: Value Changed – Add DB Record for device id zwave-4 and value id 48-user-bool-1-0
    2015-12-31 11:00:10.666 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xc7539fad
    2015-12-31 11:00:11.488 Detail, Node004, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x30, 0x03, 0xff, 0x39

    And as I wrote before, I can see changes on the dashboard, and with ImperiHome also.
    My only problem is with the “device event”. I can’t trigger a scene with any sensors,

    It’s like that the scene service doesn’t send the event to the core service.I have nothing about “1|HUB|scene|CHECKSCENESEVENT|” in the scene log, but also nothing in the core log.
    I only can find “1|scene|scene|CHECKSCENESPERIODIC|” in the core log.

    Moreover, when I make a blocky rule with the sensor, without using the device event, but using [ {device: FGMS /value : sensor} = “true”], on the peridic check, the rule works well…

    I was showing the same problem as ColdBringer (post before). I don’t know if this is always true from him.

    Am I alone with this problem ? You told us that you have reproduce this once…

    Thanks a lot

    JMarc

    en réponse à : Make a 'fast' bocky rule #2270
    Avatar
    Coyote
    Membre

    Hi,

    I’ve added ZWave-1 association in the Basic Report, but there is no improvement.
    All is oki for the detection, only the “Device Event” that still not working..

    PS : I’m using Aeotec Gen 5 USB Stick.. But I’ve not changed my hardware config.

    Other ideas ?

    Thank you 😉

    JMarc

15 sujets de 1 à 15 (sur un total de 52)