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

  • Topic Author
  • Posted

    Can someone tell me the meaning of this notification. By who is it generated. How to possibly correct Thank you

    Please login or register to see this attachment.

    Posted

    This is generated by the system software. There is an error in the syntax so it is not clear in the error what it is.

    Just to clear your doubt that it is something other than a system generated error.

    A brief explanation of what a "watchdog" is in a software environment.

     

    Quote

    Watchdog timers are widely used in computers to facilitate automatic correction of temporary hardware faults, and to prevent errant or malevolent software from disrupting system operation. During normal operation, the computer regularly restarts the watchdog timer to prevent it from elapsing, or "timing out".

     

     

    So this does not explain the error, and why it is reported as a faulty message. Maybe someone can clarify that

    Posted

    Mój polski nie jest zbyt dobry :) Ale myślę, że to samo zostało powiedziane w tym drugim wątku.

    Posted
    19 hours ago, tinman said:

    it is an error "a serious problem has been detected", the system normally checks itself, if something underneath it, then HC3 starts again and displays this error. If you've made a lot of changes, one by one, some reconfiguration or recent migrations, something like this can come in handy and you can ignore it. If it keeps appearing, then you have either a damaged system (switchboard or some module), or something so badly programmed that you undercut the switchboard.


    With a small addition one could ignore it when made a lot of changes, reconfiguration or migration. Otherwise you may have a damaged system. 

     

    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...