LeeG
-
Posts
12943 -
Joined
-
Last visited
Everything posted by LeeG
-
That is the expected KPL action for non-toggle On mode. Triggering a Program that turns the button Off is one approach. The other approach is to use non-toggle Off mode which triggers a Program that issues a Set Scene On for the Scene that now has the KPL button as a Controller. That way the KPL button blinks twice and turns Off. The possible issue is the slight delay in triggering a Program to turn the Scene On. If no delay is wanted use approach 1 that triggers a Program to turn the KPL button Off is best.
-
You're welcome. Happy to help.
-
"Is that because 640pm and 940 am are not in the same day?" Yes. By using (same day) the To: 9:40AM is before the From: time making the Time range check always False.
-
Change To: field from (same day) to (next day) If Status 'Front Door-Opened' is On And From 6:40:00PM To 9:40:00AM (next day)
-
There are additional options for suspending updates to devices and RF only devices (updates queued for node) for better control when the updates are sent. Scenes are included in the additional devices. Additional levels of Network Security in the Pro version. Suggest looking at the sales page for the 994i as I have done this from memory.
-
It is a common mistake. Setting the Scene name values affects using the Scene name in a Program, from the Admin console, etc. Each Controller has a separate set of Responder values. Also common to have different Responder values for each Controller. There is a button that is available when working with a Controller to copy the current Responder values to all the Controllers if they should all have the same Responder values. Glad things are working.
-
In Insteon every Controller has a unique set of Responder values. When using the Scene name the PLM is the Controller. When pressing the KPL button it is the Controller with a unique set of Responder values. Click the Red KPL button below the Scene name. Set the desired On Level and Ramp rate values.
-
Glad things are back. Should the PLM ever need replacing follow the Wiki instructions exactly. That sequence should give good results.
-
You need to do a Restore Modem (PLM) which will rebuild the PLM link database and should rebuild the devices link databases as well. There was a step missed or done in the wrong sequence (or maybe a Delete Modem (PLM) was done) during the process of replacing the PLM. If PLM and ISY were not powered down during the PLM change problems like this can happen. First do a Restore Modem (PLM) If a device Show does not have multiple new PLM links then do a Restore Device. If that resolves the device link table then do a File | Restore Devices to rebuild the other devices. If you intend to go back to non Insteon devices please post so we don't waste time finding a solution to the PLM replacement activity.
-
There are 4 link records with 00.00.00 address that are probably old PLM entries that were updated with the 00.00.00 address. Try another Restore Modem (PLM) followed by another Show to see if the 00.00.00 addresses were changed.
-
I would expect more link records with either the old or new PLM address. Can you post an image of the Show display with type of device, with old and new PLM address. This is a Scene that is invoked from a Program?
-
Do a Show Device Links Table on a device that is not responding to a Scene and see if it has the new PLM address in some of the link records.
-
kaveh Jimbo is correct, as a Responder to a Scene it can be set to 0% On Level. The Responder On Level is located in the Responder (A2) link record. An ISY Program can issue a Set Scene 'xxxxx' On where Scene 'xxxxx' has the Responder On Level of 0%. The device itself does not support a Local On Level of 0% which would effectively disable the function of the On Paddle. SmartLabs has to consider how the device paddle should function without all this great automation or even with automation should someone press the device On paddle.
-
Following the Wiki is important. Having the ISY powered down when powering up the new PLM is most important. The PLM has no message sequence when it powers up. The only way the ISY knows there is a new PLM is when it asks the PLM for information during the ISY boot up. Should not have problems during the PLM replacement. It does take time to change every device link database entry that has the old PLM address. Plus the small time for the RF device updates to fail and be queued for later updates.
-
The RF devices will all fail during the initial Restore Modem (PLM) processing. When the Restore is complete the RF devices will have the updates queued. Put one RF device in linking mode, right click on device primary node and select Write Updates to Device. When that device update completes, take it out of linking mode and move to the next RF device.
-
Exactly where are you reading all RF only devices should be placed into linking mode at the same time? They have to be done one at a time, completing one and taking it out of linking mode, before moving to the next.
-
"I'm trying to adjust the scene's current brightness level" There is no such thing in Insteon as a "Scene's current brightness level". There are Scene Responder On Levels and Scene Responder Ramp Rates, all of which can be specified when the Scene is defined and can be changed dynamically with Adjust Scene Program statements. The Scenes current brightness as you have defined cannot be changed as it does not exist today. You can certainly request SmartLabs add new Scene function but nothing like that exists today.
-
The All On/Off Scene must have all three KPL buttons defined as Contrrollers SceneAllOnOff KPL1 - A - Controller KPL2 - A - Controller KPL3 - A - Controller any other controllers that are controlled by this Scene any other responders that are controlled by this Scene If other KPL buttons should be On (such as button C) those buttons should be added to this Scene as a Responder. Insteon DOES NOT chain Scenes. All the devices that are affected by AllOnOff must be included in the All On/Off scene, either as a Controller that turns ON/Off the AllOnOff Scene or as a Responder.
-
Okay. Then set the local device levels as you want them. I would think someone would expect the devices to move up/down from current displayed level but that is just my opinion. If the phone changes should be ignored certainly do not change Scene levels.
-
"Doesn't that require a write back to the switch's link database in order to update it?" Yes, the Adjust Scene does that. Changing the On Levels (Brightness) of the responders leaves the Scenes unchanged. As soon as any of the On paddles/buttons is pressed all the responders go to the original Scene definition.
-
Device 11.B0.A7 did not respond to three commands sent from the ISY PLM. Time 12:38:43 marks the first of three commands sent from PLM. Suggest moving the RemoteLinc near the PLM assuming it is an 2413 Dual Band PLM.
-
The ISY has this function. What you are referring to as Scene Brightness, Insteon refers to as Scene Responder On Level. This change in Responder On Level is done with Adjust Scene statements. Done this way all Responder On Levels are set as needed and the status LEDs stay in sync.
-
The Low Batt message from the Motion Sensor occurs once and it happens before the Motion Sensor battery is too low to function correctly. Because it is a single message, having RF comm issues can interfere with receiving the Low Batt message. The suggestion about querying the Motion Sensor for current battery level may work but it reduces the life of the battery asking for that information on every motion sensed.
-
The On Level and Ramp Rate for the Responders of a Scene are located in the Responder link record for each Responder. The link record(s) have to be changed. This can be done using the Admin Console, and in a Program with Adjust Scene statements. Will have to do some searching to see if there is a REST command that updates the responder link records.
-
Run Tools | Diagnostics | Event Viewer at LEVEL 3 Press DIM/BRIGHT buttons until LED flashes. Make sure RemoteLinc near Dual Band device such as 2413S PLM. Attempt to add RemoteLinc. Post the Event Trace. What ISY Firmware and UI is being used? Help | About I just added a RemoteLinc using 4.2.23.