Announcement

Collapse
No announcement yet.

"X10" Beta version 3.0.0.47 & 48

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

    "X10" Beta version 3.0.0.47 & 48

    I just posted v.47 to the beta page (https://forums.homeseer.com/forum/li...33#post1008133) with changes to support HS4, specifically the ability to add new devices.

    This version is compatible with both HS3 and HS4. It has only been tested under Windows 10 Pro.

    ** Ability to add new devices **
    In HS4 you CANNOT currently add a new HS3 device using the Add Device "+" button on the HS4 Devices page like we used to do in HS3.

    This version of the plugin adds a page to the 'Plugins' menu and you simply click 'Plugins' then 'X10' then 'Add a new X10 Device.' You will be presented with a new page to set the X10 parameters. Clicking the "Add Device' button will create the new device in HS and open the standard HS Device Configuration page so you can change the device name (the plugin names it with the device code and [*** NEW X10 DEVICE ***]), location, room, etc. If you click the Cancel button on the Add New X10 Device page then you will be returned to the previous page and no device is created.

    ** Updated Config Page **
    In HS3, the Com Port for the plugin was set on the Manage Plugins page and the setting was stored in the HS settings.ini file. This setting has moved to the Config page and is now stored in the X10.ini file. At startup, this version of the plugin will check for the 'ComPort' setting in X10.ini and if it isn't found it will copy the existing setting from settings.ini to X10.ini. This version of the plugin no longer reports to HS that it supports Com Ports so the Com Port selector on the Manage Plugins page is no longer displayed.

    When the Config page loads it checks for valid Com Ports on the system before displaying the page. If no ports are found it will indicate this and you will not be able to select a port, even if you had selected one in the past. If a Com Port is added while the Config page is displayed, it should detect the change, display all the ports and allow you to make a selection. This was added for systems with USB Com Ports where there is a possibility that the USB cable has become unplugged.

    When you make a change to the interface, Com Port or Baud Rate (for Ti103) you must click the Update button in order for the changes to be saved and the new setting(s) applied. All other settings on the page will be automatically updated when clicked and you should not click the update button.

    There is a new 'Debug Mode' checkbox that instantly enables or disable debug logging to the HS log. You no longer have to restart the plugin after changing this setting! Note that the 'Developer Mode' setting on the 'Manage Plugins' page in HS3 is no longer used and is ignored.

    ** Fix for X10 devices copied in HS not respecting the received X10 commands **
    Previously, when an X10 device was copied in HS the device's reference was not properly updated in the device data maintained by the plugin. This resulted in the plugin not updating teh sataus of newly copied X10 devices when X10 commands were received. The plugin now updates this in 2 places: when the device's X10 settings are changed by the user (ie; editing the new device via the X10 tab) and when the plugin starts. These changes are logged to the HS log as 'info' and should not be considered as errors, unless you are seeing constantly them when you're not copying X10 devices.


    Please post your issues, logs and comments below, but only if you are running v.47 & up. Also, please include the following info when reporting anything new:
    1) Major and minor version of HomeSeer, for example: HS 4.0.0.22 or HS 3.0.0.99
    2) Operating system and version, for example: Win 10 pro, Win 7 Home, R-Pi Stretch 9.6
    3) What you were trying to do
    3) Device code(s) (if applicable)
    4) Page the error occurs on (if applicable)
    5) Log entries (please don't post your entire log unless it's pertinent)
    Best regards,
    -Mark-

    If you're not out on the edge, you're taking up too much room!
    Interested in 3D maps? Check out my company site: Solid Terrain Modeling

    #2
    Worked like a champ! I am now able to log changes from the Powerflash unit to a device I created within the plugin - many thanks.

    Using the Powerflash unit - should I set it to appliance?

    Comment


      #3
      Thanks for the feedback, glad this is now working. Yes, appliance module is On/Off only. Standard is On/Off/Standard Dim. Preset uses Preset dim commands and Extended uses Extended X10 dim commands.

      Please let me know if you run across any issues, especially adding devices.

      ‚Äč
      Best regards,
      -Mark-

      If you're not out on the edge, you're taking up too much room!
      Interested in 3D maps? Check out my company site: Solid Terrain Modeling

      Comment


        #4
        Will do.

        so far, so good

        Comment


          #5
          Works Fine for me. Many thanks.

          Comment


            #6
            Is it possible to be able to adjust the timeout for X10 warnings as 1 second seems too short and I get quite a few warnings without actual performance problems? May be it could be adjustable in the plugin management?? I'm running your 47 beta plugin on HS4 beta 37 on a Windows 10 Laptop.

            3/13/2020 06:40:48
            Legacy-Plugin
            X10 WARNING
            1.005 seconds for CM11A to send data. Possible noise or interference on power line.
            3/13/2020 03:51:18
            Legacy-Plugin
            X10 WARNING
            Still waiting for CM11a to send data... (1.02 sec)
            3/13/2020 01:35:42
            Legacy-Plugin
            X10 WARNING
            1.018 seconds for CM11A to send data. Possible noise or interference on power line.
            3/13/2020 01:01:34
            Legacy-Plugin
            X10 WARNING
            1.027 seconds for CM11A to send data. Possible noise or interference on power line.
            3/13/2020 00:27:39
            Legacy-Plugin
            X10 WARNING
            1.13 seconds for CM11A to send data. Possible noise or interference on power line.
            3/13/2020 00:27:39
            Legacy-Plugin
            X10 WARNING
            Still waiting for CM11a to send data... (1.03 sec)

            Comment


              #7

              Thanks for testing v.47! Are you seeing this for every X10 command sent, only some of them or only specific commands? Assuming you're on a 50Hz power system, a standard X10 transmission of 'Address' + 'Command' should theoretically take 940mS, leaving 60mS for the CM11A to respond and the plugin to process the acknowledgement.

              If you would, please enable Debug Mode on the plugin config page. This will generate a lot of detail about the plugin's activities and timings. If you have a lot of X10 traffic let it run for several hours. If you only have a little X10 traffic then let it run for a few days. Then copy all of your log entries to a text file and attach them here. This will allow me to evaluate how long things are actually taking and adjust this in the code.

              For now I'd prefer to keep this value hard-coded as it's not something users should have to deal with, but if it becomes an issue that cannot be resolved then I'll consider adding this as a config page setting.

              Thanks for your help!!
              Best regards,
              -Mark-

              If you're not out on the edge, you're taking up too much room!
              Interested in 3D maps? Check out my company site: Solid Terrain Modeling

              Comment


                #8
                I'll try and get the log info that you request. There's a lot of gear around the house including Powerlne wifi so no doubt the interference is of my own making but I'll attach the log in a while. Thanks

                Comment


                  #9
                  Pickles871 Thanks! It is entirely possible that 1 sec just isn't enough time on a 50Hz system. It will be interesting to see what your log reveals.
                  Best regards,
                  -Mark-

                  If you're not out on the edge, you're taking up too much room!
                  Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                  Comment


                    #10
                    Log attached. Not too many warnings. Mostly okay. Any thoughts would be most appreciated. Many thanks.

                    Peter log.txt

                    Comment


                      #11
                      Is it time to test application on HS4 in Linux?

                      Going baby steps here with a new box for HS4. I have installed Ubuntu 18.04 and a Windows 7e instance on the box.

                      I have a few extra CM11A's to test with.

                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                      HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                      6.10.0.104
                      HS4 Lite -

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                      Comment


                        #12
                        Pete Yes, please do! Install the 'legacy' X10 plugin from the updater (currently v.46) then drop the beta HSPI_X10.exe over the installed one. I'm definitely looking forward to your feedback!
                        Best regards,
                        -Mark-

                        If you're not out on the edge, you're taking up too much room!
                        Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                        Comment


                          #13
                          Will do today.
                          - Pete

                          Auto mator
                          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                          HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                          6.10.0.104
                          HS4 Lite -

                          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                          Comment


                            #14
                            Pickles871 Thanks for the log file, I'll review it as soon as I'm able.
                            Best regards,
                            -Mark-

                            If you're not out on the edge, you're taking up too much room!
                            Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                            Comment


                              #15
                              Added X10 plugin V3.0.0.46 on new Linux HS4 box. Looks like it installed but do see an error.

                              Install/Update of package X10 failed.

                              Error, package file not found: /opt/HomeSeer/Updates3/X103.0.0.46/Help.htm

                              Interface is showing OK.

                              Shut it down and updated to V3.0.0.48

                              Click image for larger version  Name:	X10HS4-1.jpg Views:	0 Size:	69.7 KB ID:	1370355

                              Added one X10 device - X1 Chime module.

                              Works fine.

                              Click image for larger version  Name:	X10-1.jpg Views:	0 Size:	28.5 KB ID:	1370358
                              Logs look OK. Only thing I cannot clip and paste them via HS4 so did this via legacy logs.

                              Mar-16 11:07:24 AM Starting Plug-In X10 loaded in 400 milliseconds
                              Mar-16 11:07:24 AM Plug-In Finished initializing plug-in X10
                              Mar-16 11:17:41 AM Device Control Device: X10 Unknown A1 [*** NEW X10 DEVICE ***] to On (100) by/from: CAPI Control Handler
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x66
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x6A
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Success! 0.76 seconds for CM11a to send.
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0x62
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x68
                              Mar-16 11:17:41 AM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
                              Mar-16 11:17:42 AM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
                              Mar-16 11:17:42 AM X10 DEBUG CM11A.SendIt(): Success! 0.211 seconds for CM11a to send.
                              Mar-16 11:17:44 AM Device Control Device: X10 Unknown A1 [*** NEW X10 DEVICE ***] to Off (0) by/from: CAPI Control Handler
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x66
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x6A
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Success! 0.469 seconds for CM11a to send.
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0x63
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x69
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
                              Mar-16 11:17:44 AM X10 DEBUG CM11A.SendIt(): Success! 0.919 seconds for CM11a to send.



                              Disabled and enabled plugin on legacy page and see this in the logs.

                              Mar-16 11:34:50 AM Plug-In Shutting down Plug-In: X10
                              Mar-16 11:34:52 AM Info Plugin X10 with ID: and Instance: has disconnected
                              Mar-16 11:34:52 AM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object
                              Mar-16 11:35:06 AM Info Plugin X10 has connected. IP:127.0.0.1:33824
                              Mar-16 11:35:06 AM Starting Plug-In Initializing plugin X10 ...
                              Mar-16 11:35:06 AM Info Initializing CM11A/12U on COM port /dev/ttyUSB0
                              Mar-16 11:35:06 AM Starting Plug-In Plugin X10 started successfully in 88 milliseconds
                              Mar-16 11:35:06 AM Starting Plug-In X10 loaded in 300 milliseconds
                              Mar-16 11:35:06 AM Plug-In Finished initializing plug-in X10
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                              HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                              6.10.0.104
                              HS4 Lite -

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                              Comment

                              Working...
                              X