Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

@jgab Pi with NodeRed has 192.168.1.158:1880. ZBS and HC2 settings as below. Nothing special here.

 

Please login or register to see this image.

/monthly_2019_06/592147369_ZBSHC2settings.jpg.51185567eba43e0d5579308951c8d1b9.jpg" alt="592147369_ZBSHC2settings.jpg.51185567eba43e0d5579308951c8d1b9.jpg" />

 

Posted

Good morning Jan,

Something is wrong curtains does not open anymore,

 
      Rule.eval("oprit.luxsensor:lux > 105 => post(#morningMsg)")
      Rule.eval("@sunrise => post(#morningMsg)")
     Rule.eval("#morningMsg & once(05:00..09:15) =>  remote(_myNodeRed,#speak{data='de gordijnen worden geopend'}); wait(00:00:15); woonkamer.gordijnvoor:open; wait(00:00:08);woonkamer.gordijnzijkant:open; wait(00:00:05);   woonkamer.gordijnoprit:open; wait(00:00:06);  eetkamer.gordijnachter:open; wait(00:00:05);  eetkamer.gordijnzijkant:value=100")         
 
  In Debug it was posting morningMsg   >>> but I lost the copy

Please advice

Posted

mmmh

Other scene does not show it is stopped but all out side light is still on! Time now 07.17

HC2 uptime 106 hours

HC2 restartedto see tomorrow if this helps

Please login or register to see this image.

/monthly_2019_06/image.png.9ca8d913150a419c155cf80a26ec717a.png" alt="image.png.9ca8d913150a419c155cf80a26ec717a.png" />

Posted

07.22 restarted and supervisor reports all scenes are alive

  • Topic Author
  • Posted
    30 minutes ago, Sjakie said:

    Good morning Jan,

    Something is wrong curtains does not open anymore,

     
          Rule.eval("oprit.luxsensor:lux > 105 => post(#morningMsg)")
          Rule.eval("@sunrise => post(#morningMsg)")
         Rule.eval("#morningMsg & once(05:00..09:15) =>  remote(_myNodeRed,#speak{data='de gordijnen worden geopend'}); wait(00:00:15); woonkamer.gordijnvoor:open; wait(00:00:08);woonkamer.gordijnzijkant:open; wait(00:00:05);   woonkamer.gordijnoprit:open; wait(00:00:06);  eetkamer.gordijnachter:open; wait(00:00:05);  eetkamer.gordijnzijkant:value=100")         
     
      In Debug it was posting morningMsg   >>> but I lost the copy

    Please advice

     

    I assume the rule has worked and just stopped working?

    I have tried it myself and it is working well for me. (It's not that sunrise if before 05:00? Here in Sweden it is now sunrise at 03:30  )

    If you are sure it posts the message (within the time limits) it should trigger the third rule.

     

    The other scene that didn't turn off the outside lights, do you see logs of fibaro:call(X,"turnOff") ?

  • Topic Author
  • Posted
    13 hours ago, FrankT said:

     

    13 hours ago, FrankT said:

    @jgab Pi with NodeRed has 192.168.1.158:1880. ZBS and HC2 settings as below. Nothing special here.

     

    Please login or register to see this link.

     

     

     

    I don't recognise the dialogue for ZBS (Return immediately - don't wait for reply) - What version of node-red are you running?

    For HC2 I guess you have "Use authentication" checked and provided?

    Posted
    1 hour ago, jgab said:

     

    I assume the rule has worked and just stopped working?

    I have tried it myself and it is working well for me. (It's not that sunrise if before 05:00? Here in Sweden it is now sunrise at 03:30  )

    If you are sure it posts the message (within the time limits) it should trigger the third rule.

     

    The other scene that didn't turn off the outside lights, do you see logs of fibaro:call(X,"turnOff") ?

    Yes on both scenes.

    It was posting morningMsg further no action

    The same with the lights it posted sunrise and no action .

     

    Posted
    9 hours ago, jgab said:

    I don't recognise the dialogue for ZBS (Return immediately - don't wait for reply) - What version of node-red are you running?

    For HC2 I guess you have "Use authentication" checked and provided?

     

    The dialog for ZBS is set to 'Never-keep connection open' and for HC2 it is set to 'Basic authentication' with my login and password for the HC2. The screen dump was only to show the IP-settings. Node.js is 10.16.0 and Node-Red version is 0.20.5

    Posted

    Ok found that I have to set HC2 return to 'a binary buffer' to get something returned to my HC2. But still no response back to ZBS.

    Posted

    Good morning Jan,

    This morning curtains where open as normal!So I am confused why the last two days it did not work.

    Please login or register to see this image.

    /monthly_2019_06/image.png.6d8641a4bd53f69e4def4ddc7ce786f9.png" alt="image.png.6d8641a4bd53f69e4def4ddc7ce786f9.png" />

  • Topic Author
  • Posted
    12 hours ago, FrankT said:

    Ok found that I have to set HC2 return to 'a binary buffer' to get something returned to my HC2. But still no response back to ZBS.

    That should not be needed - UTF-8 string works for me.

    I upgraded to Node.js 10.16.0 and Node-Red  0.20.5 as you but it still work as before for me.

    It seems like you receive the events from ER ok, and that node-red is trying to send back responses ("Outgoing payload" debug msg)

    My ZBS node (http request node) look like this (IP of my laptop is 192.168.1.18)

    Please login or register to see this attachment.

    Posted
    41 minutes ago, jgab said:

    That should not be needed - UTF-8 string works for me.

    I upgraded to Node.js 10.16.0 and Node-Red  0.20.5 as you but it still work as before for me.

    It seems like you receive the events from ER ok, and that node-red is trying to send back responses ("Outgoing payload" debug msg)

    My ZBS node (http request node) look like this (IP of my laptop is 192.168.1.18)

    Please login or register to see this attachment.

    

    I imported your flow from your post on January 18 and it shows a tcp request node as output to ZBS?

    Please login or register to see this attachment.

  • Topic Author
  • Posted

    AH, it 

    6 minutes ago, FrankT said:

    I imported your flow from your post on January 18 and it shows a tcp request node as output to ZBS?

     Ah, it may be an old flow.

    Try the one in

    In "Reveal hidden content" under the flow picture.

    Posted
    42 minutes ago, jgab said:

    Ah, it may be an old flow.

    Try the one in

    Thank you Jan. Great, working again. I think I must have used this flow before the crash and when that happened I used your february flow and just added my mod for Openweathermap. Thanks once again and have a nice day in Stockholm.

    Posted
    On 6/13/2019 at 7:10 AM, jgab said:

     

    Ok, fixed the bug with ICal and multiple alarms. Pushed a new version B11, but you can patch your current version if that's quicker

    Line 315:

    Change

    Please login or register to see this code.

    to

    Please login or register to see this code.

     

    @jgab your changes did not work, at least not for my wife :D

     

    Please login or register to see this attachment.

  • Topic Author
  • Posted
    3 hours ago, jompa68 said:

    @jgab your changes did not work, at least not for my wife :D

     

    Please login or register to see this attachment.

     

    This was difficult. I pushed a new version B12 that fixed it. Fingers crossed.

    Posted

    Hello Jan,

    What I am doing wrong?

     

     Rule.eval("alarmapp.alarmrelais:isOff => post(#AlarmStateUit); postRemote(1626,#AlarmStateUit); 1631:start;  signalisation:off; $Telegram='AlarmToeters worden uitgeschakeld'")--????

        --just for testing Rule.eval("@08:20 =>  $Telegram='Alarm Toeters worden uitgeschakeld'")

    1626 is the scene to receive

    gives error:

    Please login or register to see this image.

    /monthly_2019_06/image.png.02f52f85b10c459a3e613811ca7fd55c.png" alt="image.png.02f52f85b10c459a3e613811ca7fd55c.png" />

    Please advice

  • Topic Author
  • Posted
    22 minutes ago, Sjakie said:

    Hello Jan,

    What I am doing wrong?

     

     Rule.eval("alarmapp.alarmrelais:isOff => post(#AlarmStateUit); postRemote(1626,#AlarmStateUit); 1631:start;  signalisation:off; $Telegram='AlarmToeters worden uitgeschakeld'")--????

        --just for testing Rule.eval("@08:20 =>  $Telegram='Alarm Toeters worden uitgeschakeld'")

    1626 is the scene to receive

    gives error:

    Please login or register to see this link.

    Please advice

     

    Sorry, I gave you the wrong advice previously. The command is 'remote', not 'postRemote'.

     

     

    Posted

    Hello Jan,

    hehehe I am glad! I started to doubt on myself.

    This is more fun>>> the command comes in at the other scene. Temporary I have used a relais to for fill the task but now it is as it should be. Thanks.

    In my alarm scene disable the alarm lights goes out and I want to switch on some other lights  (it should not become dark in the house by alarm). So I made  a rule to switch on between sunset and sunrise.

    This rule I want to use to switch off, if alarmStateUit is present for 30 minutes switch off lights. Remark those lights are also used in other scenes but not together with AlarmStateUit

    is this correct?

    Please advice

            Rule.eval("once(for(00:30, #AlarmStateUit)) => {woonkamer.spotbeeldrechts, woonkamer.spotschilderijrechts, woonkamer.spotstoelsjaak}:off")
      

  • Topic Author
  • Posted
    32 minutes ago, Sjakie said:

    Hello Jan,

    hehehe I am glad! I started to doubt on myself.

    This is more fun>>> the command comes in at the other scene. Temporary I have used a relais to for fill the task but now it is as it should be. Thanks.

    In my alarm scene disable the alarm lights goes out and I want to switch on some other lights  (it should not become dark in the house by alarm). So I made  a rule to switch on between sunset and sunrise.

    This rule I want to use to switch off, if alarmStateUit is present for 30 minutes switch off lights. Remark those lights are also used in other scenes but not together with AlarmStateUit

    is this correct?

    Please advice

            Rule.eval("once(for(00:30, #AlarmStateUit)) => {woonkamer.spotbeeldrechts, woonkamer.spotschilderijrechts, woonkamer.spotstoelsjaak}:off")
      

     

    No, you can't use an #event to test for that. An event happens once and have no extension in time. You need something that is stateful (like a device or a GV) to test against. 

    There is a type of ER variable that start with '_' that can be used to keep a state and use as rule trigger. However, you need some  event that signals that #AlarmStateUit is not valid anymore.

    Ex. (I'm not sure if this is the best in your case)

    Please login or register to see this code.

     

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...