Announcement

Collapse
No announcement yet.

X10 CM11A HS2 Plugin Broken since 2005

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

    #16
    Actually; there were issues with the first revision of the HS3 CM11A combo plugin.

    I tested the current HS3 CM11A plugin and there is no serial com timeout errors.

    Here:

    http://board.homeseer.com/showpost.p...2&postcount=15

    11:31:00 PM HSPI_X10.exe IRP_MJ_CREATE VCP0 SUCCESS Options: Open
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_PROPERTIES VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_MODEMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_BAUD_RATE VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_LINE_CONTROL VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_CHARS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_HANDFLOW VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_BAUD_RATE VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_LINE_CONTROL VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_CHARS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_HANDFLOW VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_BAUD_RATE VCP0 SUCCESS Rate: 4800
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_RTS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_CLR_DTR VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_LINE_CONTROL VCP0 SUCCESS StopBits: 1 Parity: NONE WordLength: 8
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_CHAR VCP0 SUCCESS EOF:1a ERR:0 BRK:0 EVT:1a XON:11 XOFF:13
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_HANDFLOW VCP0 SUCCESS Shake:0 Replace:40 XonLimit:1024 XoffLimit:1024
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_BAUD_RATE VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_LINE_CONTROL VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_CHARS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_HANDFLOW VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_BAUD_RATE VCP0 SUCCESS Rate: 4800
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_RTS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_CLR_DTR VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_LINE_CONTROL VCP0 SUCCESS StopBits: 1 Parity: NONE WordLength: 8
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_CHAR VCP0 SUCCESS EOF:1a ERR:0 BRK:0 EVT:1a XON:11 XOFF:13
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_HANDFLOW VCP0 SUCCESS Shake:0 Replace:40 XonLimit:1024 XoffLimit:1024
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_CLR_DTR VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_BAUD_RATE VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_LINE_CONTROL VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_CHARS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_HANDFLOW VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_BAUD_RATE VCP0 SUCCESS Rate: 4800
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_CLR_RTS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_CLR_DTR VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_LINE_CONTROL VCP0 SUCCESS StopBits: 1 Parity: NONE WordLength: 8
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_CHAR VCP0 SUCCESS EOF:1a ERR:0 BRK:0 EVT:1a XON:11 XOFF:13
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_HANDFLOW VCP0 SUCCESS Shake:0 Replace:0 XonLimit:1024 XoffLimit:1024
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_CLR_RTS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_TIMEOUTS VCP0 SUCCESS RI:-1 RM:-1 RC:-2 WM:0 WC:0
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_WAIT_MASK VCP0 SUCCESS Mask: RXCHAR RXFLAG CTS DSR RLSD BRK ERR RING
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_WAIT_ON_MASK VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_SET_QUEUE_SIZE VCP0 SUCCESS InSize: 4096 OutSize: 2048
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_PURGE VCP0 SUCCESS Purge: RXABORT RXCLEAR
    11:31:00 PM HSPI_X10.exe IRP_MJ_WRITE VCP0 SUCCESS Length 1: 8B
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_WAIT_ON_MASK VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IRP_MJ_READ VCP0 SUCCESS Length 1: FF
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_PURGE VCP0 SUCCESS Purge: RXABORT RXCLEAR
    11:31:00 PM HSPI_X10.exe IRP_MJ_WRITE VCP0 SUCCESS Length 7: 9B 00 5B 0B 50 40 60
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_WAIT_ON_MASK VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IRP_MJ_READ VCP0 SUCCESS Length 1: 50
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_PURGE VCP0 SUCCESS Purge: RXABORT RXCLEAR
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_WAIT_ON_MASK VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_WAIT_ON_MASK VCP0 SUCCESS
    11:31:00 PM HSPI_X10.exe IOCTL_SERIAL_GET_COMMSTATUS VCP0 SUCCESS
    - 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


      #17
      Originally posted by Pete View Post
      Actually; there were issues with the first revision of the HS3 CM11A combo plugin.

      I tested the current HS3 CM11A plugin and there is no serial com timeout errors.

      Here:

      http://board.homeseer.com/showpost.p...2&postcount=15
      That's good news.
      💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

      Comment


        #18
        Originally posted by Rupp View Post
        It's not dead if you using HS3 but odds are the same issue is in the HS3 plugin.
        ...but it is dead if you're still using HS2. So why not release the source code, so those users who give a sh$t may be able to fix it?
        Last edited by langenet; March 27, 2014, 08:58 PM.
        HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

        Comment


          #19
          The code has been available for a few years here:
          http://store.homeseer.com/store/Plug...Code-C213.aspx
          💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

          Comment


            #20
            I agree that a little co opting on pieces of suspect code from the "current version" of HS for many with established systems would be welcomed.
            An NDA would cover it and I bet the many advanced programmmers/users of HS2 would offer up their services to get the benefits for their systems. Most of these users have probably already purchased HS3, but until it is widely accepted as "production system" ready. HS2 should be supported in some way...
            3.0.0.548: HS3PRO - 3.0.5.10: AIAlert - 2.1.1.0: APIWeather - 2.0.64.0: BLBackup - 2.0.45.0: BLLAN - 2.0.37.0: BLRoombaWifi - 1.0.0.3: DevLog - 1.2.5.15: KeyPad - 3.0.2.25: NetCAM - 0.0.0.52: Pushover 3P - 3.0.0.5: SendVFD - 1.0.0.3: Tiles - 3.0.11.0: Z-Wave

            Comment


              #21
              Originally posted by langenet View Post
              but it would be nice if HST could take a peek.
              My preference is that HST would focus on the items missing in HS3 such as HS Phone and some of the ASP web page issues that are preventing me from migrating 100% and not worry about HS2. Yes, there's a bug, but it's existed since 2005 and no one's noticed before, so IMHO who gives a ... HS2 has many architectural issues, so I fully support leaving it behind and moving on. The stability issues that I had with HS2, I've been able to attribute to the use of the SSL (https) version of the web server and if I don't use it, HS2 will run for months without rebooting.

              Cheers
              Al
              Last edited by sparkman; March 27, 2014, 09:36 PM.
              HS 4.2.8.0: 2134 Devices 1252 Events
              Z-Wave 3.0.10.0: 133 Nodes on one Z-Net

              Comment


                #22
                Yup; a bug that was there since 2005 is a bad thing.

                Most folks gave up on the unexplainable and runaway memory utilization such that they went to rebooting every few days.

                Some folks went to faster computers. I personally have kept X10 use to a minimum.

                I purchased the Zee and HS3 Pro licenses.

                That said I will be sticking to HS2 for a while (might be over a year or two or three now) before I get that functionality if ever that I have with HS2.

                Yup; here went from HS1 to HS2 very painlessly and I did get more function.

                The HS2 to HS2 Pro was painful; but still functional.

                The HS2 to HS3 was to date most expensive and so far totally not to my benefit.

                I don't mind waiting for a solid HS3 with what was promised when I updated.

                I am PO'd at myself for not catching this issue and just would rather utilize my energies not spinning my wheels testing these days and will let the youngsters go full boat with the HS3 testing and will catch up when the time comes.

                That said I want to be rewarded for the time and effort so far relating to my patience in the purchase of a product that was released way before it was ready; such that right now my total investment is not usable; but my legacy investment is still usable and should be corrected relating to a better customer satisfaction index

                Right now its really low.

                Maybe its my age but I am not as enthusiastic right now about vaporware as I used to be.
                Last edited by Pete; March 28, 2014, 06:21 AM.
                - 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


                  #23
                  Originally posted by Rupp View Post
                  The code has been available for a few years here:
                  http://store.homeseer.com/store/Plug...Code-C213.aspx
                  So help me understand.... I buy HS2/HS2PRO, then discover there's a problem with it and then I'm suppose to buy the plugin and fix it because it's broken, all on my expense and time. What a great returning customer model.

                  At-a-boy HomeSeer!
                  HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

                  Comment


                    #24
                    Yup; here I am very enthusiastic about HS3; especially the fact that I am moving to using HS3 on Linux.

                    I am not right now (even into March, 2015) seeing my same functionality (HS2) in HS3.

                    Honestly can't even guesstimate a date that I will have same functionality.

                    I am seeing too that many companies today now see that Automation can be done cheap / paid for by the month and folks will start to flock to something easier when they start playing with this stuff. (it is now in every big box hardware store and even at office supply stores - in your face type of distribution).

                    I will remain here with Homeseer; mostly because I have used it since 1998. (1998-2014 = 16 years eh?)
                    Last edited by Pete; March 28, 2014, 09:05 AM.
                    - 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


                      #25
                      A bug that was there since 2005 is a bad thing.

                      Most folks gave up on the unexplainable and runaway memory utilization such that they went to rebooting every few days.
                      - 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


                        #26
                        Odd as my HS 2.5.0.81 version has been up for 57 Days 10 Hours 22 Minutes 27 Seconds using a CM11A. And the server is only using ~500mb of memory. So I'm not seeing the issue here.
                        Attached Files
                        💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                        Comment


                          #27
                          Yup; my HS2 goes and goes with no issues using the CM11A.

                          That said I do not utilize X10 extensively.

                          This should not be seen in the serial com logging and can cause issues relating to memory leakage and CPU utilization over time.

                          0.07897400 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          0.07890528 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          0.07783531 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          0.07881616 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          0.07785263 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          0.07884438 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          0.07685670 HomeSeer.exe IRP_MJ_READ EdgeSer26 TIMEOUT Length 0:
                          Now, why is this happening? Well, a few possibilities:

                          1) Less likely -- the serial driver that was provided to you doesn't
                          strictly implement the MS-provided serial timeout semantics, and the
                          application is expecting it to do so (which is risky), and thus it
                          occasionally chokes when there is a deviation.

                          2) More likely -- some combination of timing (on the device) and
                          scheduling (on the PC) causes two "reports" to be buffered up, and the
                          application doesn't know to handle it when it consumes both.

                          When trying to "continuously read" from a serial port, I find that's
                          easiest just to set up the read loop using code like the below, and
                          then just using a state machine to keep track of where I am as I read
                          the data, rather than relying on the size of my read request to
                          properly delineate the data for me. That way, data is never
                          "missed" (and provides for easier logging also).
                          ----

                          Code:
                          void process_data(unsigned char *buf, DWORD dwLen);
                          
                          unsigned char buf[4096];
                          DWORD dwBytesRead;
                          COMMTIMEOUTS c;
                          ZeroMemory(&c, sizeof(COMMTIMEOUTS));
                          
                          c.ReadIntervalTimeout = -1;
                          c.ReadMultiplierTimeout = -1;
                          c.ReadConstantTimeout = 500;
                          
                          while (ReadFile(h, buf, 4096, &dwBytesRead, NULL))
                          {
                             process_data(buf, dwBytesRead);
                          }
                          https://groups.google.com/forum/#!to...rs/qQLEbVIMh3g

                          Setting Read and Write Timeouts for a Serial Device

                          http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx
                          - 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


                            #28
                            I agree but it doesn't seem to be hurting anything as I'm about 50% X10 and 50% Z-Wave and have a ton of X10 traffic. I'd say Rich and crew aren't going to spend too much time on this issue considering the list of bugs in Bugzilla on more important issues. Having said that if you haven't you should put in a Bugzilla ticket on this issue.
                            💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                            Comment


                              #29
                              Thank-you Rupp.

                              I will open up a Bugzilla ticket on said issue.

                              Bugzilla ticket #1724 opened at around 23:13C, April 5, 2014
                              - 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


                                #30
                                No ACKs yet on my Bugzilla Ticket #1724.
                                - 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

                                Working...
                                X