apostolakisl

@Michel Kohanim Doesn't appear to be a problem with 2477S. Just 2477D.

OK, it works. A bit of a cludge, but whatever. If you have an old ISY 99i with IR. 1) Factory Reset 2) Boot it up with a plm plugged in 3) Open admin console http://your.isy.ip.address/admin.jnlp 4) Delete PLM 5) Go to the IR tab and load the default 40 codes 6) Setup network resources in your 99i to trigger your IoP pointing to the program/node/etc you desire the IR button to act on. https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface 7) Write a program on 99i If IR 'IR_003' is Pressed Then Resource 'Name.1' Else - No Actions - (To add one, press 'Action')

I can't believe I'm the only one with this issue. I have rebooted polisy and that didn't fix it. If a switch is the responder to a scene and you turn the scene on, the status properly updates. But the below program runs correctly. tes - [ID 008E][Parent 0093] tes - [ID 008E][Parent 0093] If 'Kitchen / Kitchen Intercom-Island L' is switched On Then Wait 3 seconds Set 'Kitchen Puck S' On Else Set 'Kitchen Puck S' Off So ISY does recognizes that it is receiving the on command from the switch, it just isn't updating the status.

Well this isn't going anywhere. I'm going to hook up my old isy99i and use it as an IR to Rest converter and get my 40 isy codes back.

You can check the event viewer and set it to device communication mode (3). When you click on paddles you should see things pop up with the device addresses. If not, you have communication issues. In my case, I am having issues where the communications are showing up in event viewer, but Polisy isn't updating device status'.

The program is working correctly based on its understanding of the state of the device. The problem is the program is being told the incorrect state of the device. The program thinks the light is off even though it is on. The reason it thinks it is off is because IoP seems to be ignoring "DON" communications. It is receiving the DON, but it is not updating the device state. EDIT: And this is the case for every device I have tested so far.

I have narrowed the problem down to IoP processing error. I watch event viewer, click "on" paddle, I get a "DON" along with the correct Insteon address, but no change to lights status in the admin console. @Michel Kohanim EDIT: Here is a query result. It does register 100% after a query.

Don't see how this could be a link issue. Links are between Insteon devices. Nothing was changed between Insteon devices. The PLM is just another Insteon device. In addition, I have seen no Insteon to Insteon comm failures. All scenes are working as expected at all switches. I also tried doing a query of the one representative switch. I clicked "on", the light turned on, but ISY control panel still shows off. I do a query, and it still shows off with no errors reported on the query. I then click and hold a dim up on the switch that is already 100%, and now IoP shows "100%". Something weird here.

This is an issue not of ISY program processing but rather ISY (IoP) acknowledging the correct state of the device. Based on the displayed status of devices, IoP programs are behaving correctly. As it is, this is a much bigger problem than that program type. It is just the very first program type I found to have the issue and I jumped to the wrong conclusion about the cause based on the fact that I have seen that style go wonky twice before over the past 10 years or so. I tried doing a restore on that one device, but no dice, same thing. IoP still not showing an "on" command. But reports other commands. Dim up, dim down, off, etc. This is not a comm issue. I have tested about a dozen devices now and all have issues. There were zero issues prior to the IoP update. My comm has been rock solid for years. I made no changes to the PLM or devices, just switched serial cables and plugged into IoP instead of 994i. Perhaps a "restore plm" will help, but I don't know why it would.

I looked into this further. The program is working correctly. But IoP is not registering the status of the light correctly. I have tested many switches and the are all having issues. For example, my bedroom closet. ISY seems to always register an "off" command as well as dim and and dim down. But never recognizes on "on". So the light is off, I turn it on, but IoP still says it is off. So when I shut if off, the program incorrectly triggers. Something like this or similar is true for just about every switch in my house I have tested. This problem started after IoP was installed. I had virtually perfect correlation between ISY status and actual status prior to the switch and it has been that way for years through many ISY firmware updates.

Possible. I don't recall that when it happened with previous firmware that it only happened from higher starting levels. I think at those times the only way to get the light off was to do a fast off.

That works, but I'm not a huge fan of the Insteon double click. Often times you don't get the click rate right, especially if you are kind of moving quickly or have stuff in your hands.

I could, but I have a bunch of these. This problem has happened with other firmware versions and UD has always been able to fix it.

Curious. How "on" was the light. I have found it works correctly when the light starts off at 25%. But when it is closer to 100%, it does not. It is one of my favorite programs. At night, you might get up to go to the bathroom. Instead of pushing and holding to get the light to just turn on a bit, you just click "off" and you get a nice dim night light. Also the WAF on this program is very high. (wife acceptance factor).

I tried that last night, no dice. This has happened with past firmware updates which they have corrected.

After migrating to IoP, the following program style no longer works. It is supposed to be true only when you click the off paddle when the light is already off. But it is running true when you turn the light off from on. Curiously, does not run true when you click off the second time from 25%. Bath Night Lt. Can - [ID 0076][Parent 0083] If 'Master Bedroom / Master-Bath Cans L' Status is Off And 'Master Bedroom / Master-Bath Cans L' is switched Off And Program 'Dark Outside' is True Then Set 'Master Bedroom / Master-Bath Cans L' On 25% Else - No Actions - (To add one, press 'Action')

No, ud mobile does the same thing the http user interface does, it gives an error. You can't do anything with it.

Nope. Gives the same error "requires uuid" Also, doesn't let you enter a uuid

I have exactly the same problem.

Well this is not going well at all. The only thing that went to plan was getting Insteon working. The node servers are not working. PG3 is totally messed up and PG2 only works from PG2 to ISY. If I try to send a command from ISY to the node server, it says "busy" and then times out with an error. PG3 won't accept me changing settings. I try editing the ISY and it says "updateisyparameters invalid". I tried adding it as a second, and that sort of works, but just has all kinds of issues. Nodelink has the same problem. I can't send commands to it, it populates the admin console, but I can't send any commands to my DSC alarm without an error. PG3 images below when I edit current isy UPdate; I have discovered the nodelink is getting commands from ISY, however, ISY doesn't think it is working. ISY says busy and then gives an error, even though the command went through. Other polyglot does not do anything. Also tried restoring backup of pg3, and it doesn't do anything. No nodes, no configuration. The ISY setup page has no uuid and no way to enter a uuid. Only if I add a second ISY can I get a uuid, but the nodes I installed aren't there. UPdate: OK, figured out some of the issues. Upon moving to IoP, I moved polisy's IP address to the IP that used to be for my ISY. This of course moved the node servers as well. ISY however held onto the old IP address for polisy even though polisy from its side logged into ISY, ISY did not update that IP. However PG3 still is dead.

A node server that supports keyboard input through a polisy usb port would totally do the trick. You could use those 40 insteon ir codes or you could program the lirc to recognize, I assume, just about any ir signal. I assume you program lirc then, upon detecting the ir signal of your choice, to produce a key stroke equivalent. If ISY had a node server that recognized keyboard input, then a simple program "if keystroke A" then set lights to x.

You mean to get the 40 IR codes ISY has built in? I have done that if that is what you mean. Though I only use a few of them. I basically have on, off, and 15% for the room light. Nothing else Insteon enabled in there.

@Athlon @xlurkr I have a routine setup in my Harmony 900. I push one button and it does everything. Turns on projector, turns on receiver, turns on (whatever input device I selected), it pauses for 15 seconds, then dims the lights. The only thing I need ISY for is the lights. I am all over having the buttons to watch TV or change the volume. I will often start watching a football game or whatever an hour or so after it starts and zoom through the commercials. Pretty much only a button thing. Changing the volume is also not very voice command oriented. You have to do it in stepwise fashion with voice unless your receiver is capable of going direct to a volume level by some API (mine is not). And I get to leave my hand wherever since it is all rf. And at the end, 1 button and it shuts everything down and brightens the lights. I can push a button way faster than I can say a word and it never mis-understands me or does that swirly thing for 5 seconds before responding. Plus, the remote just has a comfortable feel in my hand.

Yes, that looks like it would work. But, I think I already have everything I need in my old 99i. I only need this for my theater room to let the handheld IR from my Harmony 900 control the lights in the room. Like 3 commands at most. The GC-IRE looks like it would be overkill. Good to know it exists, though. What I don't understand is all the people going to these touch screen devices (phones). What a terrible way to control things. You have to look at the screen, you usually have to push a button to turn on the screen first, and if you accidentally brush your finger on the wrong spot it starts doing the wrong thing. Regular remotes are so nice, especially the ones that use rf to a base station so you can hold the thing in your hand under a blanket or pointed completely the wrong way or whatever. No look, you can feel the button once you get to know the remote.

maybe I can use my old 99i as an ir receiver. Have the ir trigger a network command to ISYoP. Knew I kept it for a reason.