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


Guest Message by DevFuse

Search the Community

Showing results for tags 'radio issue'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

Facebook

Google+

Skype

Website URL

WhatsApp

Country

Gateway/s

Interests

Found 1 result

  1. pos
    Hi I have a scene that start with the HC2 and then runs permanently. It is a simple scene for outdoor lights. I have three different outdoor sections. - All outdoor light sections start 5 min before sunset - Two of them I turn of att 23:00 every evening except the nights fri-sat and sat-sun when these two sections instead turn of at 02:00. - 5 min after sunrise everything that was on is turned off The question is if my problem is related to z-wave radio issues or if there is a HC2 bug. I have a very strong Z-wave mesh and many gen5 devices with constant power near the one that sometimes fails. The thing is that sometimes (could be 3-5 days between the errors) only 2 out of three sections are light up at sunset. I have nothing that explains why. This can be seen in the debug log below. Idéas of what can cause this would be very much appreciated. I have marked the problems in bold text. The log is for 9 days and contains two errors... [DEBUG] 00:36:17: Scene trigger - autostart. [DEBUG] 03:00:52: Shutoff selected light as configured Saturday. Value after execution: 0 [DEBUG] 03:00:52: Shutoff selected light as configured Saturday. Value after execution: 1 [DEBUG] 05:55:55: It is 300 sec after SunRISE time! Time is: 05:55 [DEBUG] 05:55:56: outdoorLight1 after execution. Value: 0 [DEBUG] 05:55:56: outdoorLight2 after execution. Value: 0 [DEBUG] 05:55:56: outdoorLight3 after execution. Value: 0 [DEBUG] 19:42:58: It is 300 sec before SunSET time! Time is: 19:42 [DEBUG] 19:42:59: outdoorLight1 after execution. Value: 1 [DEBUG] 19:42:59: outdoorLight2 after execution. Value: 1 [DEBUG] 19:42:59: outdoorLight3 after execution. Value: 1 [DEBUG] 03:00:37: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 03:00:37: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 05:52:43: It is 300 sec after SunRISE time! Time is: 05:52 [DEBUG] 05:52:44: outdoorLight1 after execution. Value: 0 [DEBUG] 05:52:44: outdoorLight2 after execution. Value: 0 [DEBUG] 05:52:44: outdoorLight3 after execution. Value: 0 [DEBUG] 19:45:41: It is 300 sec before SunSET time! Time is: 19:45 [DEBUG] 19:45:42: outdoorLight1 after execution. Value: 1 [DEBUG] 19:45:42: outdoorLight2 after execution. Value: 1 [DEBUG] 19:45:42: outdoorLight3 after execution. Value: 0 [DEBUG] 23:00:26: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 23:00:26: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 05:49:32: It is 300 sec after SunRISE time! Time is: 05:49 [DEBUG] 05:49:33: outdoorLight1 after execution. Value: 0 [DEBUG] 05:49:33: outdoorLight2 after execution. Value: 0 [DEBUG] 05:49:33: outdoorLight3 after execution. Value: 0 [DEBUG] 19:47:25: It is 300 sec before SunSET time! Time is: 19:47 [DEBUG] 19:47:26: outdoorLight1 after execution. Value: 1 [DEBUG] 19:47:26: outdoorLight2 after execution. Value: 1 [DEBUG] 19:47:26: outdoorLight3 after execution. Value: 1 [DEBUG] 23:00:12: Shutoff selected light as configured Monday. Value after execution: 0 [DEBUG] 23:00:12: Shutoff selected light as configured Monday. Value after execution: 0 [DEBUG] 05:46:21: It is 300 sec after SunRISE time! Time is: 05:46 [DEBUG] 05:46:22: outdoorLight1 after execution. Value: 0 [DEBUG] 05:46:22: outdoorLight2 after execution. Value: 0 [DEBUG] 05:46:22: outdoorLight3 after execution. Value: 0 [DEBUG] 19:50:08: It is 300 sec before SunSET time! Time is: 19:50 [DEBUG] 19:50:09: outdoorLight1 after execution. Value: 1 [DEBUG] 19:50:09: outdoorLight2 after execution. Value: 1 [DEBUG] 19:50:09: outdoorLight3 after execution. Value: 1 [DEBUG] 23:00:57: Shutoff selected light as configured Tuesday. Value after execution: 0 [DEBUG] 23:00:57: Shutoff selected light as configured Tuesday. Value after execution: 0 [DEBUG] 05:43:09: It is 300 sec after SunRISE time! Time is: 05:43 [DEBUG] 05:43:10: outdoorLight1 after execution. Value: 0 [DEBUG] 05:43:10: outdoorLight2 after execution. Value: 0 [DEBUG] 05:43:10: outdoorLight3 after execution. Value: 0 [DEBUG] 19:52:50: It is 300 sec before SunSET time! Time is: 19:52 [DEBUG] 19:52:51: outdoorLight1 after execution. Value: 1 [DEBUG] 19:52:51: outdoorLight2 after execution. Value: 1 [DEBUG] 19:52:51: outdoorLight3 after execution. Value: 0 [DEBUG] 23:00:42: Shutoff selected light as configured Wednesday. Value after execution: 0 [DEBUG] 23:00:42: Shutoff selected light as configured Wednesday. Value after execution: 0 [DEBUG] 05:41:56: It is 300 sec after SunRISE time! Time is: 05:41 [DEBUG] 05:41:57: outdoorLight1 after execution. Value: 0 [DEBUG] 05:41:57: outdoorLight2 after execution. Value: 0 [DEBUG] 05:41:57: outdoorLight3 after execution. Value: 0 [DEBUG] 19:54:34: It is 300 sec before SunSET time! Time is: 19:54 [DEBUG] 19:54:35: outdoorLight1 after execution. Value: 1 [DEBUG] 19:54:35: outdoorLight2 after execution. Value: 1 [DEBUG] 19:54:35: outdoorLight3 after execution. Value: 1 [DEBUG] 23:00:28: Shutoff selected light as configured Thursday. Value after execution: 0 [DEBUG] 23:00:28: Shutoff selected light as configured Thursday. Value after execution: 0 [DEBUG] 05:38:45: It is 300 sec after SunRISE time! Time is: 05:38 [DEBUG] 05:38:46: outdoorLight1 after execution. Value: 0 [DEBUG] 05:38:46: outdoorLight2 after execution. Value: 0 [DEBUG] 05:38:46: outdoorLight3 after execution. Value: 0 [DEBUG] 19:57:17: It is 300 sec before SunSET time! Time is: 19:57 [DEBUG] 19:57:18: outdoorLight1 after execution. Value: 1 [DEBUG] 19:57:18: outdoorLight2 after execution. Value: 1 [DEBUG] 19:57:18: outdoorLight3 after execution. Value: 1 [DEBUG] 03:00:11: Shutoff selected light as configured Saturday. Value after execution: 0 [DEBUG] 03:00:11: Shutoff selected light as configured Saturday. Value after execution: 0 [DEBUG] 05:35:34: It is 300 sec after SunRISE time! Time is: 05:35 [DEBUG] 05:35:35: outdoorLight1 after execution. Value: 0 [DEBUG] 05:35:35: outdoorLight2 after execution. Value: 0 [DEBUG] 05:35:35: outdoorLight3 after execution. Value: 0 [DEBUG] 19:59:01: It is 300 sec before SunSET time! Time is: 19:59 [DEBUG] 19:59:02: outdoorLight1 after execution. Value: 1 [DEBUG] 19:59:02: outdoorLight2 after execution. Value: 1 [DEBUG] 19:59:02: outdoorLight3 after execution. Value: 1 [DEBUG] 03:00:56: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 03:00:56: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 05:32:22: It is 300 sec after SunRISE time! Time is: 05:32 [DEBUG] 05:32:23: outdoorLight1 after execution. Value: 0 [DEBUG] 05:32:23: outdoorLight2 after execution. Value: 0 [DEBUG] 05:32:23: outdoorLight3 after execution. Value: 0 [DEBUG] 20:02:43: It is 300 sec before SunSET time! Time is: 20:02 [DEBUG] 20:02:44: outdoorLight1 after execution. Value: 1 [DEBUG] 20:02:44: outdoorLight2 after execution. Value: 1 [DEBUG] 20:02:44: outdoorLight3 after execution. Value: 1 [DEBUG] 23:00:44: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 23:00:44: Shutoff selected light as configured Sunday. Value after execution: 0 [DEBUG] 05:29:11: It is 300 sec after SunRISE time! Time is: 05:29 [DEBUG] 05:29:12: outdoorLight1 after execution. Value: 0 [DEBUG] 05:29:12: outdoorLight2 after execution. Value: 0 [DEBUG] 05:29:12: outdoorLight3 after execution. Value: 0 [DEBUG] 20:04:26: It is 300 sec before SunSET time! Time is: 20:04 [DEBUG] 20:04:27: outdoorLight1 after execution. Value: 1 [DEBUG] 20:04:27: outdoorLight2 after execution. Value: 1 [DEBUG] 20:04:27: outdoorLight3 after execution. Value: 1 [DEBUG] 23:00:30: Shutoff selected light as configured Monday. Value after execution: 0 [DEBUG] 23:00:30: Shutoff selected light as configured Monday. Value after execution: 0 Thanks in advance /Peo
×
×
  • Create New...