Announcement

Collapse
No announcement yet.

HS4 Beta 4.2.0.5 is available

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

    #16
    Originally posted by rjh View Post
    It works when I test it so I am missing something. Can someone who knows Linux run HS from ssh and monitor the update? You might see what is not working.


    The update file is downloaded correctly to the HomeSeer directory. But it apparently never gets unzipped. Nothing in the logs. P.S. HS is running as a service as described in one of the docs.

    Comment


      #17
      rjh I have the same issue. From my Debian10 Linux system running HS4, I can go https://homeseer.com without issues. I get the same error trying to download the tar.gz file.
      Code:
      root@HS4:/usr/local# wget https://homeseer.com/updates4/linux_4_2_0_5.tar.gz
      --2021-09-09 19:33:13-- https://homeseer.com/updates4/linux_4_2_0_5.tar.gz
      Resolving homeseer.com (homeseer.com)... 149.28.228.84
      Connecting to homeseer.com (homeseer.com)|149.28.228.84|:443... connected.
      ERROR: The certificate of ‘homeseer.com’ is not trusted.
      ERROR: The certificate of ‘homeseer.com’ doesn't have a known issuer.
      If I change the wget to use http instead of https, I can download the beta software.

      Comment


        #18
        You can also add this switch to wget:
        --no-check-certificate

        I don't know why wget has this issue, but we have seen it before. It must use a different cert chain then MONO or a browser.

        Originally posted by kennesaw10 View Post
        rjh I have the same issue. From my Debian10 Linux system running HS4, I can go https://homeseer.com without issues. I get the same error trying to download the tar.gz file.
        Code:
        root@HS4:/usr/local# wget https://homeseer.com/updates4/linux_4_2_0_5.tar.gz
        --2021-09-09 19:33:13-- https://homeseer.com/updates4/linux_4_2_0_5.tar.gz
        Resolving homeseer.com (homeseer.com)... 149.28.228.84
        Connecting to homeseer.com (homeseer.com)|149.28.228.84|:443... connected.
        ERROR: The certificate of ‘homeseer.com’ is not trusted.
        ERROR: The certificate of ‘homeseer.com’ doesn't have a known issuer.
        If I change the wget to use http instead of https, I can download the beta software.
        💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

        Comment


          #19
          Originally posted by avpman View Post

          The update file is downloaded correctly to the HomeSeer directory. But it apparently never gets unzipped. Nothing in the logs. P.S. HS is running as a service as described in one of the docs.
          Same here. This has been the same behavior I've experienced when attempting to update from the GUI, for the last couple of months. Click image for larger version

Name:	2021-09-09 (1).png
Views:	334
Size:	21.0 KB
ID:	1494789

          Comment


            #20
            Originally posted by rjh View Post
            You can also add this switch to wget:
            --no-check-certificate

            I don't know why wget has this issue, but we have seen it before. It must use a different cert chain then MONO or a browser.


            This may well be why the buttons on the setup screen to update HS4 never seem to work on Linux machines. It didn't work for me and that is why I took the wget route in the first place.

            Comment


              #21
              Originally posted by rjh View Post
              What kind of system are you using? We had to renew the SSL cert on homeseer.com and I know it has issues on some versions of Linux. Linux needs to have it's certs updated. Only guessing that this is what you are seeing. If you go to https://homeseer.com with a browser the cert checks out ok.


              I use a Raspberry Pi 4 (HomeSeer) that's where the https is not working but that link you posted works on my Windows Desktop.

              I even tried to disable the use SSL in Labs setting with no effect

              Click image for larger version  Name:	SSL.png Views:	0 Size:	11.8 KB ID:	1494806

              And yes, I tried again after installing the 4.2.0.5


              Eman.
              TinkerLand : Life's Choices,"No One Size Fits All"

              Comment


                #22
                Originally posted by randy View Post
                How would the system know the name of a device that is no longer there?
                when a devices is deleted it could by written in a file , and removed from that file when all the events that reference that name have been changed/ deleted

                Comment


                  #23
                  Originally posted by rjh View Post
                  You can also add this switch to wget:
                  --no-check-certificate

                  I don't know why wget has this issue, but we have seen it before. It must use a different cert chain then MONO or a browser.


                  The error occurs with both curl and wget.This on Ubuntu and RaspberryOS.

                  Check here: https://www.digicert.com/help/

                  Click image for larger version

Name:	cert.PNG
Views:	318
Size:	375.6 KB
ID:	1494816

                  Comment


                    #24
                    Upgraded last evening from my phone sitting on the patio! Too cool! This morning everything works!
                    Nice Job!!


                    Date/time=9/10/2021 7:06:30 AM CDT
                    Version=HS4 Standard Edition 4.2.0.5 (Linux)
                    MONO Version=Mono JIT compiler version 5.18.0.240 (tarball Wed Jan 16 09:11:44 UTC 2019)

                    License=Registered
                    Confguration File=/usr/local/HomeSeer/Data/SEL Dec 2020.json
                    Uptime=0 Days 11 Hours 30 Minutes 52 Seconds
                    Lan IP=127.0.0.1 (HomeTrollerSELv2)
                    Device Count=305
                    Event Count=164
                    Plugins Enabled=Z-Wave:,Z-Wave UI:
                    Modules/Threads=88 Modules, 59 Threads
                    Available Threads=199
                    HomeSeer Memory Used=92 Mbytes
                    Plugins Installed=BLDenon 2.0.57.0,ImperiHome 3.0.0.40,Z-Wave 3.0.7.0,Z-Wave UI 1.0.0.0

                    Comment


                      #25
                      Originally posted by rjh View Post
                      It works when I test it so I am missing something. Can someone who knows Linux run HS from ssh and monitor the update? You might see what is not working.


                      rjh
                      Hi Rich I found the root cause for my system (during extensive testing 0n 4.2.0.0). Although I have no idea to fix.

                      I repeated the steps in this post

                      https://forums.homeseer.com/forum/ho...01#post1491401

                      also on 4.2.0.5 with identical results.

                      So the behavior of situation 1 and 2 differs

                      1. Upgrade after starting HomeSeer usig ./go PASS
                      2. Upgrade after starting Homeseer as a service FAIL

                      By the way In case of situation 1 when I do a reinstall of HomeSeer after the first successful upgrade it will alos fail. So my hypothesis is that during the upgrade process the instance is rebooted. In case you can confirm this we will know the root cause for sure.

                      ---
                      John

                      Comment


                        #26
                        rjh I think I've hit a major issue with this beta. When my plugin create a device with a set of features, some of the features do no longer show up in the device list (but they do when looking at /deviceutility). I have triple checked that the relationship status is correct (Root vs Child) and the Associated devices looks fine too (device/root and feature/child point to each other).

                        This is what seems to happen, but is it difficult to find a rhythm to it...
                        - Create the device - shows correctly
                        - Create first feature - no features are shown
                        - Create second feature - only the first feature is shown
                        - Create third feature - first and third features are shown
                        - Create fourth feature - first, third and fourth features are shown
                        - Create fifth feature - first, third, fourth and fifth features are shown
                        - etc

                        Going back to 4.2.0.0 and all of the above works correct again.
                        stefxx

                        Comment


                          #27
                          rjh Kudos where they are due....I like the event broken tagger and the manage plugin page improvements very much.

                          thanks
                          HS3 Pro Edition 3.0.0.435 (Windows 10 vmware)
                          BLOccupied:,UltraNetCam3:,weatherXML:,RFXCOM:,Current Cost 3P:,UltraGCIR3:
                          DMMQTT:,Kodi:,Z-Wave:,BLRadar:,EasyTrigger:,MySensors:,BLBackup:

                          Comment


                            #28
                            I’m curious, I’ve noticed that there is a button in HS 4.2 Setup>General> Install Beta. Is it actually possible now to just click that install Beta button and have HS update properly?

                            It used to be that I had to remote into my Windows computer, shutdown HS and then on restart it would start the install but you had to make sure to shutdown HS first before it could install the update.


                            Sent from my iPad using Tapatalk
                            HS4 4.2.6.0 &HSTouch Designer 3.0.80
                            Plugin's:
                            BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee, Nest, AK Bond
                            EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
                            weatherXML, Jon00 Alexa Helper, Network Monitor, MyQ, Z-Wave

                            Comment


                              #29
                              HS-1400 Feature display order is not saved in device properties
                              this has no impact on RoomMe plugin feature order, nor on smartthings plugin devices feature order. matter of fact on RoomMe while all feature are on the tile, when trying to edit the order only 2 of 3 features show up. Except one room has all three in the feature edit area. haven't tried changing a Wave device.

                              Comment


                                #30
                                Yes that works. But it does restart your computer.... Which is not needed nor what I want. So I keep doing it the "old" way.
                                stefxx

                                Comment

                                Working...
                                X