Announcement

Collapse
No announcement yet.

Too Many Quirks

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Too Many Quirks

    Over the last dozen or so betas and a couple of official releases, HS3 gradually messes up some devices. Unless you're really paying attention you might not notice initially. Consequently, I can't tell what changed at what update. I've posted on the board about some of these issues and other users confirmed.

    Other issues I've report a bugzilla, to no avail. Usually I don't even get a response confirming someone read the complaint.


    My Qubino micro switch with temp sensor logs the temp twice in a row about 99.5% of the time.
    My Fiabro water sensor with temp sensor does exactly the same thing.

    My GoControl outlet does not show a root and a child. It only shows what appears to be the on/off switch but it has all the root stuff in the z-wave tab. It used to show properly, weird. It does work ok, but when things should be a certain way, you expect them to remain so.

    Both my Aeotec micro switches do not show a root. They show the on/off switch with the normal root stuff in the z-wave tab. These too used to show properly. What happened?

    Devices that capture energy consumption do not display properly and some only get updated when I "reset accumulated values" rather than actually resetting.

    I regularly get status reports for an open door unless I press "reset notifications". Again, quite a few versions ago, this used to work properly.

    My aeotec outlet switches show RGB and custom color controls even though there's no such thing available.
    The same outlet switch shows a second multilevel switch with dimming control which it doesn't have.

    Then there's the issue https://forums.homeseer.com/showthre...83#post1359983 which may or may not be a HS3 issue as opposed to a z-wave issue. However since the z-wave plug-in and the hardware is all Homeseer...


    I love HS3 and all its options but this is really getting annoying. Not knowing where to turn, this is the end of my rant for now.

    #2
    Have you tried rolling back to the release versions of HS3 and the Z-Wave plugin and set your system back up? Beta testing can leave systems in a mess from all the installs and updates. I'd also not recommend testing the betas unless you are willing to have the inconveniences that comes with beta testing.
    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

    Comment


      #3
      Originally posted by Rupp View Post
      Have you tried rolling back to the release versions of HS3 and the Z-Wave plugin and set your system back up? Beta testing can leave systems in a mess from all the installs and updates. I'd also not recommend testing the betas unless you are willing to have the inconveniences that comes with beta testing.
      This is important information. You've got to be willing to put up with problems if you're going to be beta testing.
      RJ_Make On YouTube

      Comment


        #4
        I'm ok with being at the edge, rather enjoy it actually. However, I regard my issues as basic stuff, that shouldn't break.

        I'll think about rolling back to official releases but some of these issues are over a year old. I certainly don't have backups going back that far and I would lose the newer stuff.

        Basically, I would have to start from scratch or at least start excluding all the broken devices and events then including again and building. Note that one of the common questions when one posts an issue is that you're if you could install the latest beta and try again. So I feel I'm getting pulled forward and being pushed backward at the same time.

        Comment


          #5
          The only challenge I would have with that theory is that sometimes you're told to install a BETA version.

          Case in point: purchased some of the new HomeSeer (round) motion sensors. They would NOT include correctly, and I was told I needed to install the latest beta version of the Z-Wave plug-in. I did that and they included fine. I suppose I could have waited for the plug-in to move through to production, and I get the reason to require it run through beta first, but this makes me a bit uncomfortable if it happens again in the future.

          For now, my Z-Wave network is small, so it's less of a risk. However, when my network gets bigger, I may be less inclined to run beta copies if I may experience similar symptoms.

          Comment


            #6
            There're not only Betas ; official release messes up some devices : for example, the Zwave pluging 3.0.1.130 no longer allows me to change the value of the Danfoss thermostat.
            Several release had issue with S1 and S2 on Fibaro switch...

            Each new version brings new features and fixes errors. But it also systematically brings problems

            So I'm a little reluctant to update to 3.0.1.190

            Comment

            Working...
            X