Announcement

Collapse
No announcement yet.

.383 Manage Plugins Beta Plugins Not Populating

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

    .383 Manage Plugins Beta Plugins Not Populating

    I always run the latest betas, and the last few HS3 version 379, 382, and now 383, are not populating the beta version that I have installed; in the updater.
    For instance I have the latest .52 zwave beta plugin installed, and the updater shows .52 as the latest, but the column showing if / what version I have installed (only under beta plugins), is blank; so it doesn't show I have it installed...it is, and is working.

    The non-beta plugins show my version and the newest version and let me update.

    I have several dozen plugins that all work but 5 or 6 are beta and have the same blank column in the updater.

    #2
    I do have any "Installed" Plugins listed in plugin manager. I saw this break in .383

    Comment


      #3
      I see the same issue with Linux / HS3 / V383 and posted on the beta thread.

      Historically never paid attention or even test beta's (that is me).

      I like your saying richardo...

      the past is from where we learn....
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
      HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

      HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
      HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

      Comment


        #4
        .390 fixed these issues for me.

        Comment

        Working...
        X