Diesel

IMHO option 2 makes the most sense for a virtual dimmer, otherwise with option 1 it behaves like a switch. A virtual dimmer should function in the same way as a physical dimmer or a keypad button added as a scene controller. Holding a Dimmer or Keypad button down brightens or dims a scene. Pressing a keypad button turns a scene ON or OFF. One of the most useful applications for a virtual dimmer as a scene controller is for multi-way circuits. Consider a common 3-way lighting circuit where 2 physical dimmer switches are added to a "3way" scene, both as controllers. BUT in IoX if you control any of the 2 dimmers directly, the other isn't in sync and neither is the scene. The virtual dimmer solves this dysfunctional behaviour where everything remains in sync as it should be.

Virtual Dimmer only allows adding as a scene responder. Controller/Responder is greyed out.

@sjenkins Is a virtual dimmer not able to used as a scene controller?

Thanks so much! Loaded beta 3.1.14 into another slot. Created a virtual switch and was able to add it as a scene controller - Awesome! {"id": "10", "type": "switch", "name": "My vs Name"} Device type in AC shows as Virtual Switch Created a virtual dimmer but it only allows the option to add it as a scene responder. {"id": "30", "type": "dimmer", "name": "My vd Name"} Device type in AC shows as Virtual Generic The scene I tried adding it to is a 3-way circuit with 2 dimmers.

@sjenkins There's some really great integrations in the store, but Virtual is one of the most important. Virtual switches/dimmers as scene controller & responder solves so many issues. Thanks so much for taking the time to make this happen! 😊

from polyinterface import Node, LOGGER class VirtualSwitch(Node): """ Virtual Switch Node for PG3x that can act as a controller for a native Insteon scene. """ id = 'virtual_switch' def __init__(self, polyglot, primary, address, name, scene_id=None): super().__init__(polyglot, primary, address, name) self.scene_id = scene_id # Optional: Native Insteon scene this switch controls self.add_driver('ST', 0) # State driver: 0=off, 1=on def start(self): LOGGER.info(f"Starting Virtual Switch '{self.name}' with scene_id={self.scene_id}") # Register command handlers self.poly.on('ON', self.on_command) self.poly.on('OFF', self.off_command) def on_command(self, command=None): """Handle ON command from PG3x or scene activation""" if self.scene_id: self.send_scene_command('ON') self.set_driver('ST', 1) # Update switch state def off_command(self, command=None): """Handle OFF command""" if self.scene_id: self.send_scene_command('OFF') self.set_driver('ST', 0) def send_scene_command(self, cmd): """ Sends the ON/OFF command to the linked Insteon scene via IoX. Replace the below with actual PG3x API call to trigger a scene. """ try: LOGGER.info(f"Sending command '{cmd}' to scene {self.scene_id}") # Example pseudo-call; replace with actual API method # self.poly.iot.send_scene_command(self.scene_id, cmd) except Exception as e: LOGGER.error(f"Failed to send command to scene {self.scene_id}: {e}") def set_scene_id(self, scene_id): """Optional helper to dynamically update the controlled scene""" self.scene_id = scene_id LOGGER.info(f"Virtual Switch '{self.name}' now controls scene {scene_id}")

Hi, @sjenkins thank you so much for the work that's gone into this plugin. Any possibility to enhance it so that virtual switches can be a scene controller rather than only a responder? Taking it a step further, also be able to create a virtual dimmer? It would solve a very fundamental and fatal issue with the way IoX considers a scene state.

Thanks for taking the time to share your detailed experience with the update on Polisy. I was just about to press that upgrade button (in AC) on my Polisy when I read your post. I have no time to resurrect the dead this week so I'm going to wait for Michel to work out the upgrade bugs before I hit that upgrade button.

Hi Lee, Thanks for your help. I've created the variable and related program, and updated the email notif program as you outlined. When trying to rename the variable from Int_1 to something meaningful, it always seems to reset back to Int_1? I'm surprised that there's no simpler (or inherent) way to throttle or limit the number/interval of emails sent when motion is detected? For example: You have a motion sensor in the back yard and want to receive an email notification when there's movement, so you can have a look on your cameras to see what's going on. If the gardner shows up, your inbox gets hammered every second while cuts the grass!

Hi Michel, I just want to receive an email notification as soon as the motion sensor is triggered, but only once and then not again for X minutes, otherwise the notifications flood my inbox. I don't want the system to wait 15mins after sensing motion to notify me. For example, the sensor will detect motion when the Gardner is cutting the grass, but currently I would receive 35 emails a minute. Just once would be fine, and then if motion continues 15 or 30mins later, it can send another notification again. How do I achieve this? Thanks for your help.

Hi all, Need some help with a new 2420M ver2.0 Motion Sensor and email notification. 2420M is installed outside for night time perimeter security. All seems to work triggering the lights I've specified in the program. Next objective was to send myself an email notification when it sensed motion. So I added the program below and it works, but how do I get it to send just 1 email instead of 15-20 of them? If Control 'Outside / Outside:Motion-Sensor' is switched On Then Send Notification to 'Me' content 'Outside Rear Motion Detected' Wait 15 minutes Else - No Actions - (To add one, press 'Action') It seems like it sends an email each time the sensor detects motion, even a few seconds apart which hammers my inbox. I had hoped adding the 'Wait 15 mins' would help, but no luck. What am I missing?

Thanks for the ideas guys. The date range was particularly helpful.

Hi all, I think understand the basic concept of a Vacation/Away Mode, but could use some help establishing the best way to use it. Objective is for certain additional security lights to come on at sunset when we're away and turn off early am as well as to turn off some other lights like bedroom lamps that we normally turn off ourselves when we go to bed when we're home. Could you guys give me some examples of how you use the Vacation/Away folder and if its possible to manually "activate" this mode/programs in that folder to not have to rely only on a kpd button status. I'm concerned that if we're away for some days and the power should go out, I presume this kpd button will just reset itself to off. Maybe I'm wrong tho. Thanks for the help.

That worked ! Thanks Mike Although I needed to add a wait in there too, otherwise the kpl light turned off even if the scene it controlled was active. I guess it needed more time to evaluate if each of the devices met that condition. Now the program looks like this; If Status 'WatchTV (E)' is not Off And Status 'FamilyRm-LeftLamp' is not On Or Status 'FamilyRm-TvConsole' is not On Or Status 'FamilyRm-RightLamp' is not On Then Wait 1 second Set Scene 'WatchTVStatus' Off Else - No Actions -

Ok so I did the following; 1. Created a scene called WatchTVStatus and added only KPL (E) as a responder. 2. Created a program called WatchTVStatus If Status 'WatchTV (E)' is not Off And Status 'FamilyRm-LeftLamp' is not On And Status 'FamilyRm-TvConsole' is not On And Status 'FamilyRm-RightLamp' is not On Then Set Scene 'WatchTVStatus' Off Else - No Actions - Since On= 100%, when I press WatchMovie(F) which reduces all of those lights to 40%, the above program should trigger Status of (E) to change to Off. For some reason it doesn't work