IndyMike

Good sleuthing, I'm guessing this isn't your 1st rodeo. I didn't understand that the On/Off commands work but the dim commands don't. That is odd. I don't know of any theory that supports loss of dim/brt because of noise or loading. I'm thinking I sent you down a bad path there. I do vaguely remember having problems with Leviton dimmers on my old CM11a. If I remember correctly, it had something to do with the resume dim feature. Do you have a idea of which model dimmers work and which models don't? I can remember some of the higher end ACT, PCS, and Leviton dimmers had programmable features. Some could be set to emulate a traditional switch.

@Bladerunner, I have tried both the A10 and X10 generic types on the ISY994. I don't see a difference. One curious thing that I do NOT see in your event viewer - a response from the PLM. If you look at my log below, you'll see the "X10-RSP" from the PLM confirming the command. This could be a difference between your EISY and my old ISY994, but it's something to check out. Sat 11/09/2024 09:53:48 AM : [ X10] M3 Sat 11/09/2024 09:53:48 AM : [X10-RSP ] 02 63 02 00 06 Other than the fact that there is no PLM response, the commands look correct. You stated that the F2 command works but the G14 doesn't. If these are difference end devices, I would suspect communication issues. I'm assuming you've been using X10 in your system for some time. Any chance you lost your phase coupling/repeater. Any new signal absorbers - it is the season when all the Christmas decorations start coming out, wreaking havoc on us HA types.

After a little looking, I found an old LM465 lamp dimmer in the spare parts bin. Added it to the ISY as a Generic A10 device @address M3. Home Assistant brought the device in as a Switch - HOWEVER, it does allow me to send brighten/dim commands to the ISY node. The following script correctly brightens the LM465 (as shown by the ISY event monitor). So much for my educated guesses - always test Home Assistant script: alias: X10 Bright sequence: - action: isy994.send_node_command target: entity_id: switch.a10_device data: command: brighten description: "" ISY Event Monitor: Sat 11/09/2024 09:53:48 AM : [ X10] M3 Sat 11/09/2024 09:53:48 AM : [X10-RSP ] 02 63 02 00 06 Sat 11/09/2024 09:53:48 AM : [ X10] M3/Bright (7) Sat 11/09/2024 09:53:49 AM : [X10-RSP ] 02 63 05 80 06

Your X10 dimmers are most likely 1-way (receive only) devices. There is no "status" or "query" available. There were very few X10 2-way units produced. Again - I do not have any X10 dimmers to verify. I did code a quick script for one of my Insteon Dimmers using the Visual Editor in HA. Two tricks in the following: For action, you need to select "Perform action ....." Do not use the "Device" or "Light" entries that are available. For Target - Select "entity". This will present a list of ISY entities on your system. Choose your X10 unit Command will bring up a list of commands available for your device. I chose "Brighten" The following works for Insteon devices. The Yaml code generated by the visual editor is shown below. There are some differences from your code (I'm not a Yaml master). The most significant item may be that your entity is labeled as a "switch". Chances are it will be On/OFF only. Not sure if there is a way for the X10 devices to come over as a "light" which would allow dimming. Yaml code generated: alias: Brighten sequence: - action: isy994.send_node_command target: entity_id: light.bsmt_fam_rm_sconce data: command: brighten description: ""

@Bladerunner, I do not have any X10 dimmers to verify, but Insteon dimmers do show "levels". Your logs will only reflect on/off. However there is an entity associated with Insteon dimmers that will show the current on level. Go to Settings/Devices and Services/Universal Devices ISY xxxx. Click on Entities and search for a dimmer on your system. The following is what I have for one of my 2477D's. Note that the dim # is 102 (102/255 = .4). You can use the dimmer level in automations as a trigger or a qualifier.

@CoolToys, Have a look at your motion sensor for the guest area. It can disable/interrupt your bedtime program if it fires at the wrong time. I just recently replaced batteries on two MS I sensors that were behaving badly (no low battery set). Aside from that, when programs fire without a trigger or re-enable themselves I start thinking about SDcards and the like. A program should Never spontaneously enable itself (you can enable a program with another program). I have no experience with the Eisy, so I will bow to others who do.

@gempro, not sure if you have been able to resolve your issues. Your event log did show an interesting detail that was not part of the scene test. After the test completed, the ISY attempted to write an update to your 46.2F.CA device (RemoteKP.F). This update failed with a Nack response from the KPL. The Nack indicates that your new PLM is not currently linked to this device. It looks like with update may have been automatically triggered after you performed the scene test. In a system that is having communication issues, that can complicate things. Try turning OFF the automatic writes (screen capture below) and restoring this device. If the restore completes successfully, perform a link table read/compare to double check. Continue in this manner with your other devices. If the restore does not work, come on back and we can develop a plan B. <html><font color="red">----- Keypad LED F Test Results -----</font></html> <html><font color="red">[Failed]</font> KeypadF (44 7D D7 6)</html> <html><font color="red">[Failed]</font> RemoteKP.F (46 2F CA 6)</html> <html><font color="red">----- Keypad LED F Test Results -----</font></html> Wed 10/23/2024 07:18:32 PM : [INST-TX-I1 ] 02 62 00 00 12 CF 13 00 Wed 10/23/2024 07:18:32 PM : [INST-ACK ] 02 62 00.00.12 CF 13 00 06 LTOFFRR(00) Wed 10/23/2024 07:18:32 PM : [Ext MH ] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Wed 10/23/2024 07:18:32 PM : [46 2F CA 1 ] Link 27 : 0F20 [A22A711973FF1F01] *Failed Writing [A22A711973FF1F01] Wed 10/23/2024 07:18:32 PM : [All ] Writing 8 bytes to devices Wed 10/23/2024 07:18:32 PM : [INST-SRX ] 02 50 46.2F.CA 71.19.73 AB 2F FF (FF) Wed 10/23/2024 07:18:32 PM : [Std-Direct Nack] 46.2F.CA-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 10/23/2024 07:18:32 PM : [D2D EVENT ] Event [46 2F CA 1] [ERR] [1] uom=0 prec=-1 Wed 10/23/2024 07:18:32 PM : [ 46 2F CA 1] ERR 1

@CoolToys, the program you posted above has the variable $sOccupied_Guest_Edit is 0 as a qualifier. I'm not sure where this is controlled, but if it is altered it could cause your program to exit prior to completion. The waits in your program will allow this. Some lights could be left in the incorrect state, and the variable $sBedtime = 1 might not be set.

@CoolToys, as others have indicated, a program that uses ONLY the condition "Time is XXXX" will show true until it triggers false. Unfortunately, it will Never trigger false. As a result, you can't use the program status as an IF condition in another program (it will always be true). As a workaround, you could use the "From XX to XX" clause that would evaluate to a false after the time period. The following program will evaluate to false 1 minute after sunset. This becomes difficult if you have embedded "waits" within your program (which you do). You wind up with a race condition between the program and the If statement. It's far better to separate the Trigger (if statement) and program (then clause) into two separate programs so the IF statement won't terminate your running program. Outside Sunset - [ID 0015][Parent 0002] Outside Sunset - [ID 0015][Parent 0002] If From Sunset For 1 minute Then Set 'Outdoor / SC Outside Sunset' On Else - No Actions - (To add one, press 'Action') I'm not sure that's the answer to you issues as nothing that you've posted above would results in your variables both being true ("sEarly_Morning" and "sNight") Please do review your code for any programs that use a program "true" status as a condition.

@SimonK, thanks for taking the time to post back the results of your ticket with UD. It sounds like this problem may have been frustrating users for some time. Curious whether it applies to the Polisy and possibly the ISY994. In the meantime, celebrate by spinning up some Queen "another bug bites the dust"

@Guy Lavoie, thanks for the clarification. Looks like I added 2 + 2 and came up with 22. One question regarding your eisy/Zstick configuration - does it support S2 security? The link that I referenced above (@lilyoyo1) indicated that S2 security was only supported for the Zmatter board. Wasn't sure if that had changed.

Ouch! When did UD UNSUPPORT the Zooz 700 stick? That's a rather major new item and a big departure from previous statements. Did I mis-understand? https://forum.universal-devices.com/topic/34826-zwave-700-series-tips-and-tricks/

@ELA, Nice Photo. That's a failure that I have yet to encounter. I am worried that you may have voided your warranty 😉. Like you, I am on the fixed income plan. When Smartlabs closed their doors I began playing with Z-Wave devices. When Insteon restarted. it was their prices that kept me away. For future planning, you may want to visit the Zooz site (Zen51 Dry contact). They have a number of innovative products that make some financial sense. Unfortunately, if you are still using a ISY994, you will need to upgrade to take advantage of the 700/800 series Zwave features. Zooz plusses: Inexpensive relays, dimmers, and embedded (typically 50% less) Select relay and dimmer devices can be used in N-way configurations with standard mechanical switches (additional cost savings). EX - I had a 5 way insteon setup (4 insteon switches) that I replaced with 1 Zen77 and 3 mechanical switches. Very nice rocker feel. As good or better than Insteon. Smooth dimming performance. I replaced some 2477D's I had controlling 2 chandeliers. The 2477D's produced "herky jerky" dimming with the 45W candelabra LED bulbs. The Zen77's were very smooth even with a slow ramp rate. Responsive customer support - reported an issue with what I termed "excessive communication" using a power monitoring plug-in. Customer service responded, we conversed, and 3 months later they informed me of a firmware update that they had developed to address the issue. OTA firmware updates of devices. No issues with all-on (Insteon issue that still plagues some devices). Full disclosure - I really like these guys. I want to make sure they stay afloat.

I'm thinking that the IF clause is re-evaluating to false after you have run the "Then section" of the program. Your 20 second waits will allow the program to exit. Try separating into two programs (1 program for IF and 1 for Then).

You are correct that you cannot see KPL secondary button status in Home Assistant by istself. If you create a scene with the secondary button as member, Home Assistant will create a "Switch" using the scene name. You can track the KPL button status and control it (On/Off) through the scene name. As an example, I had an unused button C on one of my KPL's (BSMT KPL Game - C). I created a scene (SC BSMT KPL Game - C) with the KPL button as the only member. Re-loaded the ISY integration on Home Assistant, and the Scene (SC BSMT KPL Game - C) shows up as a Switch. It is both observable and controllable.