Sirmeili

Thanks! sorry I didn't think to search for it first I just ran across it while looking into another issue (separate thread posted)

I will check that out. The ISY setup is new. I just migrated from HomeSeer back to the ISY (and into Home Assistant). To be clear, the rest calls manually triggered in HA are instant. They happen in about 80ms. It's whenever an Automation is triggered in HA where there is an action calling back to the ISY. For instance, I have some rooms where if you fast off the main light, it turns off the TVs, lights, etc. I like to keep all that pretty much in the same place for easier maintenance. So as part of those automations I call a scene in the ISY to turn off all the Insteon stuff (again, I know I COULD do this part in the ISY, but I like it all in one place). Calling that scene manually from HA is instant, but when the automation calls it based on the fast off trigger, it is delayed 1.5-2 seconds. Every. Single. Time. Again, I don't know if it's HA, the integraiton or the ISY. I will check out the level 3 event viewer Thanks!

I am running a polisy with an integration into home assistant (HA) . I've noticed in HA when I add an insteon device to an automation triggered by another isy device, then the control often has a 2 second delay in the rest response from the ISY. I can no say for sure that this is on the ISY side at all, but I'm just covering my bases here. Is there anything on the ISY to prevent throttling on the rest API or that would cause a 1-2s delay right after an outgoing message? For instance, as a test when my utility closet opens or closes, I trigger the light in that room to turn on/off (i know this can be done solely in the ISY, but this is merely a test to isolate the issue to the ISY or it's integration in HA). When the automation is triggered by the isy event, there is a 1-2 second delay in the rest call to the ISY (call and response denoted by the lines surrounded by **) 2023-07-29 22:12:30.246 DEBUG (MainThread) [homeassistant.components.isy994] Sensor None turning On via the Primary node sending a DON command 2023-07-29 22:12:30.248 DEBUG (MainThread) [homeassistant.components.isy994] Heartbeat timer starting. Now: 2023-07-30 02:12:30.247908+00:00 Then: 2023-07-31 03:12:30.247869+00:00 2023-07-29 22:12:30.248 DEBUG (MainThread) [pyisy] ISY Node Control Event: NodeProperty(control='DON', value=1, prec='0', uom='', formatted=None, address='32 86 20 1') 2023-07-29 22:12:30.249 DEBUG (MainThread) [pyisy] ISY Updated Node: 32 86 20 1 **2023-07-29 22:12:30.262 DEBUG (MainThread) [pyisy] ISY Request: http://10.0.0.172:8080/rest/nodes/50%20D1%207F%201/cmd/DON** **2023-07-29 22:12:31.873 DEBUG (MainThread) [pyisy] ISY Response Received: /nodes/50%20D1%207F%201/cmd/DON** 2023-07-29 22:12:31.873 DEBUG (MainThread) [pyisy] ISY command on sent to 50 D1 7F 1. 2023-07-29 22:12:32.186 DEBUG (MainThread) [pyisy] ISY Updated Node: 50 D1 7F 1 If I call the automation directly (not triggered by a ISY event) the call to turn on/off the light is not delayed, it's almost instantaneous (call and response denoted by the lines surrounded by **) **2023-07-29 22:21:17.173 DEBUG (MainThread) [pyisy] ISY Request: http://10.0.0.172:8080/rest/nodes/50%20D1%207F%201/cmd/DON** **2023-07-29 22:21:17.181 DEBUG (MainThread) [pyisy] ISY Response Received: /nodes/50%20D1%207F%201/cmd/DON** 2023-07-29 22:21:17.182 DEBUG (MainThread) [pyisy] ISY command on sent to 50 D1 7F 1. 2023-07-29 22:21:17.496 DEBUG (MainThread) [pyisy] ISY Updated Node: 50 D1 7F 1 Again, I'm not saying it's the ISY or the Polisy, but just covering my bases. I have run tests where I just turn on/off a device from HA in rapid succession and am not able to reproduce the delay there either, making me think it's HA, but again just checking. Is there anywhere in the ISY/Polisy to see the Rest API call logs? I would like to see if the outgoing response matches the timestamp of the one in HA. My working theory is that HA is for some reason throttling it, but I can't say this for sure without logs on the ISY side.

Should I be worried about he large amount of reported bad memory in the ISY interface of my Polisy?

Quick update: So air gapped it today and that seemed to work. I will monitor it and see if it happens again. Have other scenes though where I explicitly set buttons off (like a turn the whole room off scene) and in those the whole scene triggers, but the buttons don't, which is odd. I did not try to air gap those but will if I see it again. Thanks all!

I don't do use scenes like this but in HomeAssistant o prefer to not use scenes to control fans because it would take either 4 buttons or scripting to mimic a fan to control the 3/4 scenes. I would rather control the fan directly which is why I need the programs to keep the kpls in sync. Fanlincs My kpls differ from room to room. For instance the living room kpl (8-button) controls lights, I few outlets and 4 fans (each only one button). I use the 4 button in rooms where I really don't have a need for the buttons for something else. In one room I only ose 2 buttons for the fan (on/off). I know it could be one but I don't have a use for the other button so why not.

I don't either, but I do use Home assistant and automations over there to combine multiple technologies. I only use the polisy for insteon. I will give that try tomorrow and if that doesn't work I'll try resetting the devices and restoring them. Thanks!

How do you do this? If I control the fanlinc directly in the isy the kpl buttons till be out of sync. Yes I could only use scenes but in other systems it's nice to be able to control one device instead of controlling 4 scenes. My concern about the programs is why do they all "run" at once when only one meets the conditions? Is it the wait?

back again. I turned on the diagnostics and used my mini remote to turn on the fan and this is what I got: 44:8E:4D is the MiniRemote (fan is button 2) 47:EB:8C is the fanlink (correctly set to high) 50:EE:D2 is the KPL (button 3 is "off" and button 6 is "high") Looking in the admin, it says that the High LED is in fact on (6), and the LOW is off (3), but looking at the KPL, that is reversed. I can even see the programs ran again..... but not all 4 ran again for some reason. Here are the Programs (seems I missed this room when updating them all to a 2 second wait, but I dont' think the wait should even be necessary): Off: Low: Medium: High: And this is a scene which jsut shows what ISY thinks the LEDs status is here is a picture of the KPL (excuse the dusty switch plate..LOL)

I should also note that the ISY actually shows the correct state of the buttons. I.e. I turned off the fan the ISY (polisy) shows that A is ON and the other 3 are off, but if it was on High, the KPL still shows D lit (I use 4 buttons for my KPLs for fans in a few locations, but I've even seen this on a KPL that has 1 button for Off/High)

Not sure if this is the best place, but I am on a polisy. I have set up my fanlinc's and KPLs to control them. I have the same setup as described here: https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration. However, sometimes, not all times, when I turn off a fan from another device or integration (Remote or Home Assistant for instance), the KPLs LEDs to no show the correct state. What I notcied was that if I look in programs, all 4 of my programs run to keep the KPLs in Sync. Why is this? My Biggest difference i can see is that in my programs I added a wait before each action. The reason for this is I found if I didn't, the problem was worse. I'm now up to a 2 s delay. I was previously using HomeSeer's insteon plugin to control my KPLs and didn't seem to have this issu. I've also noticed, in perhaps a related issue, sometimes when I initate a scene not from the device itself (say from the ISY dashboard) that the KPL buttons that are part of that scene don't always end up in the correct state. I'm sure i'm missing lots of details, so if you let me know I'll grab whatever logs/details needed to help solve the issue. It tis a bit intermittant, but it's greatly affecting the WAF.

I unlinked the KPL from the ISY, completely reset the KPL, and started over, and as of right now, I think it's doing what I want it to do. I should have probably tried this before. I really wish the dimmer would show up as a different device (A-H and a dimmer), but I suppose in a non-ISY environment, if you did that, you might not be able to re-link it to the A button, so I guess it makes sense. I'm gonna keep messing with this and see what I come up with.

Ok, so I have a 8 button KPL and a Fanlinc. Due to the LEDs in my ceiling fan, the Fanlinc's dimmer does not work, but the KPLs dimmer does. So the fan is controlled by the FanLinc and the lights by the KPLs dimmer. So, what I did was assign key C, D, E, and F to the fan's Off, Low, Med, and High settings respectively and it works great. What I'm having an issue with is that I would like to use the A button (All On/Off) as just an "All On" Button instead, however, I can not for the life of me get it to NOT toggle the light it is connected to. I have it set to Non-Toggle [On], but it still toggles the light! What is worse is that if I make it a controller for a scene, it still toggles the scene on and off as well. If I set it up as Non-Toggle [Off], it does in fact work as only an "off" button. So I tried setting button B as the All On, but when I do that the LED for A turns on because the light is on. A few questions: 1) Is it possible to decouple the LED light for Button A from the actual Dimmer? 2) Is what I'm looking to do even possible? Should I just give up on using the A button for an All On and just use it as an On/Off for the dimmer switch? 3) I sometimes get it to work as expected (only as an on button), but then it reverts (After me creating a scene or adjusting another button) I'm highly confused. The rest of the buttons work as I expect, but the A button has me thoroughly confused!