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


Heatit Z-TRM3 on HC3 (slave) parameters reset


Pete123

Recommended Posts

Hello,

 

I have 3 HC3, one master and two slaves.

On one of the slaves, I have about 12 Heatit Z-TRM3 thermostats.

 

1) Over the summer, I have them all off, using the climate panel. Sometime at midnight, they all turn on for no apparent reason. The climate panel does not have any actions at midnight that could trigger this. Has anyone else seen this behavior?

 

2) From time to time the parameters reset on the thermostats. This means that some of them will start heating and not stop, since I use "A2F", external room sensor and floor sensor. Default is just "A", internal temperature sensor. The thermostat it self is not in the room that is being heated in the bathrooms, hence it will never get warm enough. Has anyone else seen this behavior?

 

I was thinking about a work around to at least find out when it happens, but I am not sure if it is possible to get parameters with Lua. Anyone knows how to get that? If I can get notification that the parameters change, I can handle it, until I find a real solution.

 

Great to hear if anyone else has any experience with this?

 

Peter 

Link to comment
Share on other sites

ad1)
Have you seen on event panel if the system send the action for the device (if this is system issue then those should be visible there) or only report with new state?

 

ad2)
Probably if parameters (Configuration I assume?) reset themselves on the device gateway is not aware of it - 99% devicess on the market does not report parameters change in unsolicited report.
You will need to cyclically poll whole configuration from the device to make Gateway aware of the change, this will have major impact on network performance during the procedure.
If you would like to try this let me know - I will past you a solution in Lua to poll the configuration automatically, as for parameters value - current values (known by gateway) are stored in property "parameters" on parent device. 

Link to comment
Share on other sites

  • Topic Author
  • On 9/10/2021 at 10:59 AM, m.roszak said:

    ad1)
    Have you seen on event panel if the system send the action for the device (if this is system issue then those should be visible there) or only report with new state?

     

    ad2)
    Probably if parameters (Configuration I assume?) reset themselves on the device gateway is not aware of it - 99% devicess on the market does not report parameters change in unsolicited report.
    You will need to cyclically poll whole configuration from the device to make Gateway aware of the change, this will have major impact on network performance during the procedure.
    If you would like to try this let me know - I will past you a solution in Lua to poll the configuration automatically, as for parameters value - current values (known by gateway) are stored in property "parameters" on parent device. 

    1) I can see in the console:

    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 21, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 20, value = 60
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 18, value = 50
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 14, value = 10
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 13, value = 1
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 6, value = 270
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 2, value = 4
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 21, value = 10
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 20, value = 90
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 18, value = 60
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 14, value = 50
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 13, value = 0
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 6, value = 400
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 2, value = 1
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 21, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 20, value = 60
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 18, value = 50
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 14, value = 10
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 13, value = 1
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 6, value = 270
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 2, value = 4
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 21, value = 10
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 20, value = 90
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 18, value = 60
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 14, value = 50
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 13, value = 0
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 6, value = 400
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 2, value = 1
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 17, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 16, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 17, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 16, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 21, value = 100
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 20, value = 60
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 18, value = 50
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 14, value = 10
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 13, value = 1
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 6, value = 270
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 2, value = 4
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 21, value = 10
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 20, value = 90
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 18, value = 60
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 14, value = 50
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 13, value = 0
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 6, value = 400
    [11.09.2021] [12:20:11] [TRACE] [ZWAVE]: ID 977: Set parameter 2, value = 1

    Please login or register to see this attachment.

    All I see in the history panel for this device at this time is:

    Please login or register to see this attachment.

     

    2) The "set parameter" in the console, means it is the controller resetting the parameters, or I am wrong?

    Link to comment
    Share on other sites

  • Topic Author
  • On 9/10/2021 at 10:59 AM, m.roszak said:

    current values (known by gateway) are stored in property "parameters" on parent device. 

     

    Can I access this data using Lua?

    Link to comment
    Share on other sites

    As for the logs - it means that controller sets this parameters, normally this needs user interaction.
    Is there a possibility that you have a script which does it?

    As for getting parameters in lua - yes, without a problem. Examples below:
     

    Please login or register to see this code.


    this prints all parameters from a specific device.
     

    Link to comment
    Share on other sites

    • 2 weeks later...
  • Topic Author
  • @m.roszak I have been doing a bit of monitoring. This issue is actually not isolated to the Heatit thermostats, but also apply to Fibaro Flood Sensors (and probably more).

    It looks like that when z-wave restarts, then default parameters are randomly pushed to one or more devices on the slave.

     

    This is rather annoying, since it means that all devices on my slaves are at risk. How should we go about solving this?

    Link to comment
    Share on other sites

    Hello, this problem with random receiving parameters on the slave controller was still in 5.070. We wrote about this bug in support, and also in the thread

    point 2. This problem remains and it greatly interferes with the normal operation of the system.

    • Like 1
    Link to comment
    Share on other sites

    We will take a closer look into it.
    We have fixed a lot of issues with GC recently, I will let you know if I reproduce this.

    Link to comment
    Share on other sites

  • Topic Author
  • @m.roszak If you have any issues reproducing the issue, please let me know and I will work on a method to provoke the issue.

    Link to comment
    Share on other sites

    We have tested this on upcoming version with a lot of fixes related to Gateway Connection and we did not reproduce this.
    If you will find a way to do so please share it.

    It is possible that this is just fixed by other changes. 

    • Like 1
    Link to comment
    Share on other sites

  • Topic Author
  • @m.roszak I hope you are right. From my point of view it is easy to reproduce. Just reboot the HC3 slave and master, then at least some devices will have reset parameters.

     

    I will test it as soon as it is released. When do you expect that to be?

    Link to comment
    Share on other sites

    It should be released later next week at the latest.

    As for the issue, I have found something which in some special conditions may cause this problem but still did not reproduced this on newest package. 
    This "thing" is not as easy to be corrected (and won't be in next version) but I hope that other changes are likely to reduce the occurrence of your problem.

    Link to comment
    Share on other sites

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