FBoucher Posted May 17, 2022 Posted May 17, 2022 Ok, the title is probably not great, but I wasn't sure how to describe my problem. I have an Insteon On/Off Outlet (2663-222) that is linked with two seperate scenes dedicated to outdoor lights. The top part is with scene A and bottom part with scene B. I've created two programs (one for scene A and one for scene B ) where the scenes are turned on 30 minutes before sunset and turned off at midnight. So, both scenes operate at the same time, except for scene B that can be triggered manually via an Insteon Keypad button. During my tests, I sucessfully turned on and off the scenes via the admin console nodes. If I use the keypad, scene B turns on and off like clockwork. The problem is when the programs run, only one of the node gets turned on. The status of the nodes show that both are turned on, but when I issue a query, the status of the off node is reset to off. I thought that the Insteon device was not able to handle both requests at the same time, so I introduced a 2 seconds wait time for scene B. It doesn't seem to be enough. Should I increase the delay or is there another solution? Thanks,
Solution MrBill Posted May 17, 2022 Solution Posted May 17, 2022 Right click either outlet at pick “restore device” and let the ISY rewrite the links. You can also try factory resetting the device then use the same procedure to rewrite the links to the device, right click and pick “restore device” also try a 15 second delay. you can also overlap scenes. Scene b can have the remote in it to just control that half the outlet. Scene A can have both outlets, and the timing then only needs one program controlling one scene.
FBoucher Posted May 17, 2022 Author Posted May 17, 2022 Thanks again MrBill. It is as I expected. Sending two requests to the same Insteon device in a short time is unreliable (it may or may not work). So I increased the delay to 10 seconds and it seems to work. I'll let the program run for a few nights and see if it's consistent.
lilyoyo1 Posted May 17, 2022 Posted May 17, 2022 7 minutes ago, FBoucher said: Thanks again MrBill. It is as I expected. Sending two requests to the same Insteon device in a short time is unreliable (it may or may not work). So I increased the delay to 10 seconds and it seems to work. I'll let the program run for a few nights and see if it's consistent. Why not simply create a separate scene, put everything in that scene together as responders and trigger that. No need for a wait
MrBill Posted May 17, 2022 Posted May 17, 2022 Just now, FBoucher said: Thanks again MrBill. It is as I expected. Sending two requests to the same Insteon device in a short time is unreliable (it may or may not work). So I increased the delay to 10 seconds and it seems to work. I'll let the program run for a few nights and see if it's consistent. Insteon network speed is very slow by nature.... I don't know if you're old enough to remember 300 baud dial-up modems but the actual speed the signal travels from PLM to device over the powerline is really slow, mostly likely something like 300 baud was. And yes there's not much traffic management, especially with links controlling scenes (as opposed to direct device control). Each device in a scene doesn't answer back... it either hears the signal and responds, or doesn't hear and thus doesn't respond. My advice would be to take advantage of the feature that Scene's can overlap, and simply have one timing sequence for scene A with all the devices that need to be timed, have a Scene B that repeats the device that may need manual control. That's an Insteon feature, scene's aren't rigid.
FBoucher Posted May 17, 2022 Author Posted May 17, 2022 Well ... I guess I qualify for old enough. My first taste of remote access was Kermit over a regular phone handset inserted in a modem interface ... Thanks for the tip. I'll keep it in mind if I need to adjust the programs.
larryllix Posted May 17, 2022 Posted May 17, 2022 3 hours ago, FBoucher said: Well ... I guess I qualify for old enough. My first taste of remote access was Kermit over a regular phone handset inserted in a modem interface ... Thanks for the tip. I'll keep it in mind if I need to adjust the programs. Oh Gawd! I remember Kermit. Wasn't it one of the first that could continue after a comm interruption, like nothin' happened? I played text golf on the University computer (Honeybun) over my ear muffin modem. I can still hear the modem tones well enough to whistle them and confuse many FAX machines. People just love the garbage that comes out all over their pages.
Recommended Posts