Announcement

Collapse
No announcement yet.

Example usage - MultiSwitch

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

    #31
    Originally posted by pseudocode View Post
    avpman yes just uninstall the beta and reinstall the current non-beta version, but it would really also help if you provided your system information.
    Here ya go:

    Date/time=5/17/2023 5:47:55 PM EDT
    Version=HS4 Standard Edition 4.2.18.8 (Linux)
    MONO Version=
    License=Registered
    Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
    Uptime=0 Days 20 Hours 15 Minutes 39 Seconds
    Lan IP=192.168.1.78 (lenovo-homeseer)
    Device Count=947
    Event Count=145
    Plugins Enabled=drhsIpPlugIn:,IR Plugin:,EasyTrigger:,BLBackup:,NetCam Plugin:,Big5HS4:,UltraTivo3:,Z-Wave Parameters:,BLLock:,BLLAN:,BLLED:,Shark Robot:,MeiKu:,Ring:,Device History:,SonyTV:,Arduino:,SDJ-Health:,Blue-Iris:,AK Weather:,ScreenLogic:,BLRussound:,Z-Wave:,Controls Plus:,UPBSpud:
    Modules/Threads=137 Modules, 141 Threads
    Available Threads=799
    HomeSeer Memory Used=293 Mbytes
    Plugins Installed=AK Bond 4.0.5.4,AK Remootio 4.0.5.0,AK Weather 4.0.5.77,Arduino 4.0.2.20,Big5HS4 3.7.0.0,BLBackup 2.0.63.0,BLLAN 2.0.45.0,BLLED 2.0.1.0,BLLock 3.0.39.0,BLOccupied 2.0.28.0,BLRussound 4.0.5.0,Blue-Iris 3.1.3.33206,Controls Plus 1.3.2.0,Device History 4.4.2.2,drhsIpPlugIn 0.0.0.31,EasyTrigger 3.0.0.78,IR Plugin 4.0.0.6,Manage Voice Devices 3.0.0.0,mcsMQTT 6.3.1.0,MeiKu 3.2.0.11,NetCam Plugin 1.0.0.6,OMNI 3.0.2.23,Pushover 4.0.12.0,Pushover 3P 0.0.0.52,RaspberryIO 3.0.0.21,Ring 1.0.0.32,rnbWeather 4.4.2.0,ScreenLogic 2.1.3.0,SDJ-Health 3.1.1.4,Shark Robot 1.0.8068.17222,SonyTV 3.0.0.6,Ultra1Wire3 3.0.7364.22993,UltraTivo3 3.0.7956.26531,UPBSpud 3.0.0.54,Zigbee 4.0.11.0,Z-Wave 3.0.11.0,Z-Wave Parameters 4.0.55.0​

    Comment


      #32
      @pseudocode​ - Will you be adding the ability to list individual device status in the 'multi' HS Device? I use this functionality (via my Composite Devices script) for tons of stuff: Events, Pushover notifications, dashboards, etc. Its essential for me to know/see what devices are Open (Doors, Windows, Garages, locks, etc). I really like the direction you are going on this plugin!

      Comment


        #33
        Originally posted by Ltek View Post
        @pseudocode​ - Will you be adding the ability to list individual device status in the 'multi' HS Device? I use this functionality (via my Composite Devices script) for tons of stuff: Events, Pushover notifications, dashboards, etc. Its essential for me to know/see what devices are Open (Doors, Windows, Garages, locks, etc). I really like the direction you are going on this plugin!
        I'm not sure what you mean - the idea of the multiswitch is really to simplify a group of other switches and just provide a summary, so I don't want to make it too much more complex.

        My priority for major enhancements at the moment is a more generic multi control, which will do the same as the switch but for devices with multiple features and non-binary controls - so I can group my shutters which have position + tilt settings, and group my Velux to have blind, awning and window all on one device.

        Comment


          #34
          avpman could you do a test for me - I can't see any cause for the problem you're seeing.

          Run the following Script Command (access from the tools menu) to switch the device on:

          hs.SendControlForFeatureByValue(600, 100)

          It takes a second to compile, then the device should change or you'll get an error in the log like the plugin sees. For example, when I try to control one of my switches that needs 255 as the on value:

          5/20/2023 09:00:13 Plugin Warning Error during SendControlForFeatureByValue - Exception during fDEBUG_PI_CALLS for 153 : 100 - Object reference not set to an instance of an object.
          5/20/2023 09:00:05 HomeSeer System Control Panel Immediate Script: &hs.SendControlForFeatureByValue(153, 100)​

          Comment


            #35
            Originally posted by pseudocode View Post
            avpman could you do a test for me - I can't see any cause for the problem you're seeing.

            Run the following Script Command (access from the tools menu) to switch the device on:

            hs.SendControlForFeatureByValue(600, 100)

            It takes a second to compile, then the device should change or you'll get an error in the log like the plugin sees. For example, when I try to control one of my switches that needs 255 as the on value:

            5/20/2023 09:00:13 Plugin Warning Error during SendControlForFeatureByValue - Exception during fDEBUG_PI_CALLS for 153 : 100 - Object reference not set to an instance of an object.
            5/20/2023 09:00:05 HomeSeer System Control Panel Immediate Script: &hs.SendControlForFeatureByValue(153, 100)​
            The script doesn't turn on the lamp, and I get the same error in the logfile. Hope this helps?
            5/20/2023 8:50:01 AM
            Plugin
            Warning
            Error during SendControlForFeatureByValue - Exception during fDEBUG_PI_CALLS for 601 : 100 - Object reference not set to an instance of an object

            Comment


              #36
              avpman that shows the 100 value is definitely wrong, it isn't recognised as a valid control setting.

              Please provide a screenshot of the Status/Graphics page from that device (not the MultiSwitch), i.e. this view:

              Click image for larger version

Name:	image.png
Views:	56
Size:	81.7 KB
ID:	1615756

              Comment


                #37
                Originally posted by pseudocode View Post
                avpman that shows the 100 value is definitely wrong, it isn't recognised as a valid control setting.

                Please provide a screenshot of the Status/Graphics page from that device (not the MultiSwitch), i.e. this view:

                Click image for larger version  Name:	image.png Views:	0 Size:	81.7 KB ID:	1615756
                100 is correct for this device 600

                Click image for larger version

Name:	image.png
Views:	44
Size:	100.7 KB
ID:	1615776

                Comment


                  #38
                  Your log entry was for device 601:

                  Error during SendControlForFeatureByValue - Exception during fDEBUG_PI_CALLS for 601 : 100 - Object reference not set to an instance of an object

                  But I'm guessing this is a double switch with 599 being the master and 600+601 being the features for the two relays? And they both definitely us 0 & 100 as the values?

                  Unfortunately I have no idea why that isn't working - the script call should work, it's just looking up the control based on the value you give and then triggering that control. The plugin does the same thing, so as the script doesn't work either it shows it's not a problem in the plugin.

                  Does anyone else on the forum have any ideas?

                  Comment


                    #39
                    Originally posted by avpman View Post

                    100 is correct for this device 600

                    Click image for larger version  Name:	image.png Views:	0 Size:	100.7 KB ID:	1615776
                    UPDATE: I changed the range of values of device 600 to 0 and 255. That works with your script command if I use 0 and 255 as off and on, respectively. Since this is a switched plug, I guess it's only going to respond to 0 and 255.
                    Awesome!

                    Comment


                      #40
                      Originally posted by pseudocode View Post
                      Your log entry was for device 601:

                      Error during SendControlForFeatureByValue - Exception during fDEBUG_PI_CALLS for 601 : 100 - Object reference not set to an instance of an object

                      But I'm guessing this is a double switch with 599 being the master and 600+601 being the features for the two relays? And they both definitely us 0 & 100 as the values?

                      Unfortunately I have no idea why that isn't working - the script call should work, it's just looking up the control based on the value you give and then triggering that control. The plugin does the same thing, so as the script doesn't work either it shows it's not a problem in the plugin.

                      Does anyone else on the forum have any ideas?
                      100 didn't work for the 601 device either. They needed to be 0 and 255 in the status values and use 0 and 255 for Off and On respectively.

                      Comment


                        #41
                        Originally posted by avpman View Post

                        100 didn't work for the 601 device either. They needed to be 0 and 255 in the status values and use 0 and 255 for Off and On respectively.
                        That's weird - I'm surprised the controls would work with the values set to 100 if the actual device needs 255. I guess it's possible pressing the button isn't exactly the same as calling that function, although it should be.

                        Great that it's working!

                        Comment


                          #42
                          Originally posted by pseudocode View Post

                          That's weird - I'm surprised the controls would work with the values set to 100 if the actual device needs 255. I guess it's possible pressing the button isn't exactly the same as calling that function, although it should be.

                          Great that it's working!
                          Neither device worked when called at 100. I had to ensure both had 0 and 255 as the range values and use 255 for on. Even when the device had range values of 0 and 100, the 100 still gave the error. Must be some built-in logic that non-dimming devices must use 0 and 255.

                          Comment


                            #43
                            Originally posted by pseudocode View Post

                            I'm not sure what you mean - the idea of the multiswitch is really to simplify a group of other switches and just provide a summary, so I don't want to make it too much more complex.

                            My priority for major enhancements at the moment is a more generic multi control, which will do the same as the switch but for devices with multiple features and non-binary controls - so I can group my shutters which have position + tilt settings, and group my Velux to have blind, awning and window all on one device.
                            I get the use case design, the question is not about that. Its about will you enable the vDevice to 'show' the status of any on/open devices? I do it like the below screenshot.

                            In the screenshot if multiple real devices are open/on/offline/etc, it will list each on a separate line in the device status. I then have a default status text for each, which can be different... for Windows when all are closed it shows "All Closed", for motion "No Motion" or "None" for locks "All Locked" or "All Secure". Cameras are an is the exception where it shows cams that are Offline, not on/open as with the others. So in this example, Kitchen cam is offline. When all cams are online it shows "All Online". I see your pluging shows 2 of 5, or such. But that doent provide the information I need to know what is open/close/triggering/ect. I can watch the motion composite device and see in near real time movement in my home - for example.

                            Click image for larger version  Name:	image.png Views:	0 Size:	219.1 KB ID:	1615833

                            Comment

                            Working...
                            X