kzboray

Have you looked over the following information? This post contains working instructions for both 4.x and 5.x software families. https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration#Firmware_5.x The other possibility is that the FAN you are using, is being powered off by the remote and simply can't be used until it is first sent a power on commend from the remote. For fans being controlled by a FanLinc you would preferably only use a dumb fan, no remote controller. Just the old pull cords version; and I remove the pull cords because the same thing can happen. If someone where to pull the light chain, the light would no longer work via Alexa or the 6-button switch since it has been powered off at the fan itself. So until someone pulls that chain one more time, the light will not work.

Make a scene with just the 6-button light switch in it. If Light 1 ctrl is on or ight 2 ctrl is on or etc for all the switches you have then scene 6-button on

Reset Mini Remotes Turn off Mini Remote by sliding the power switch to the right Press and hold the set button while sliding the power switch to the left Continue holding the set button until the beep stops Release the set button. You should hear two beeps confirming that your Mini Remote has been reset

So one of the biggest changes with PG3 is that the developers, people like you and me, can now be compensated for all the work they put in building first the PG2 node servers and now the PG3 node servers. The money you pay goes directly to the developer, not UDI. Personally I'm happy to give something back, and they ask for very little. Plus they not only developed the node servers, but often provide amazing support for free. It's a hard deal to beat. Glad you are liking your Polisy!

Insteon HW is selling very well on ebay, and you can post it here as well. Stuff usually gets sold within hours.

I'm wondering if something is amiss with your Polisy OS install. Have you tired doing the front button one push update?

Two scenes, All Basement, Laundry + Hallway Program one: If Laundry ctrl on or Hallway ctrl ON Or 6-button light switch ctrl ON Then Laundry + Hallway scene on Program two: If 6-button ctrl OFF Then All Basement Lights OFF

@jkraus I think I did indeed misunderstand. Thank you for being kind about it! If you want the KPL status lights to agree with the z-wave status. just write a program to update the KPL with changes to the z-wave switch. I know I made that sound simple and I share your pain. I miss Insteon more everyday. Sometime the z-wave device doesn't support pushing changes and you have to create a program to poll its current state and update a variable or what ever you decide to do. Then you use this variable to force the update to the KPL. I hope that made sense.

@abartello I just asked about this about a week ago and Michel said, "Definitely going to do this." No time line. Great minds think alike!

@Chris Jahn, @JimboAutomates See above please

Ring is supported via the currently off line cloud polyglot server. It was taken off line due to security concerns. The Ring Node server did not have support for cameras, but that might have changed over time. For camera support you might take a look at the BlueIris Node server.

Here's the advanced setting for the Zen34. It seems like you might be able to set the LED indicator function from here to what you want. Otherwise, using a program will definitely do the trick. Here is a full list of advanced settings (parameters) for the ZEN34 Remote Switch VER. 1.03 firmware: LED indicator mode Parameter 1: Choose if you want the LED indicator to turn on anytime a trigger is activated (normal model) or to remain always on or off. Values: 0 – LED indicator always off; 1 – normal mode (default); 2 – LED always on in the color specified in parameter 2; 3 – LED always on in the color specified in parameter 3. Size: 1 byte dec Top paddle LED indicator color Parameter 2: Choose the color of the LED indicator to light up in normal mode when the top paddle (scene 1) is triggered. Values: 0 – white; 1 – blue (default); 2 – green; 3 – red; 4 – magenta; 5 – yellow; 6 – cyan. Size: 1 byte dec Bottom paddle LED indicator color Parameter 3: Choose the color of the LED indicator to light up in normal mode when the bottom paddle (scene 2) is triggered. Values: 0 – white (default); 1 – blue; 2 – green; 3 – red; 4 – magenta; 5 – yellow; 6 – cyan. Size: 1 byte dec Wake-up time Parameter 4: Choose how long the ZEN34 will stay awake for when manually woken up (with 7 tap up on paddle). Values: 0 – short wake-up until it receives the wake up no more command from the hub (default); 1 – longer 30-second wake-up time (to make it easier to change multiple parameters at a time). Size: 1 byte dec ASSOCIATIONS: Group 1: Basic set lifeline to hub Group 2: Basic for on (top paddle) and off (bottom paddle) Group 3: Multilevel start level change (held) and stop level change (released) The ZEN34 Remote Switch can be updated via OTA firmware updates, here is how to do that. You can request a firmware update file here, please include your order number for verification!

One of the most common reason the restore doesn't work is because you have installed NS on PG3 manually in different slots. If you are careful to use the same slots they were in on PG2 the restore should go off without a hitch. I only mention it because you had said you have a lot of NS's. It might be easier to delete the ones you have installed on PG3 and just do a restore from PG2.

That is correct. But once you have deleted the NS form PG2, the ISY will have no communications from those devices. It will be up to the IoP and your PG3 NS to take over.

PG2 and PG3 are entirely different Polyglot servers. You can have them both running and servicing ISY's or IoP's. Each Polyglot server PG2 or PG3 can run multiple Node Servers. For example I have an ISY994 that uses a PG2 Harmony Hub NS, but I also have the PG3 version running and it talks to my IoP. Both run on my Polisy. The problem would be if you have both PG2 and PG3 trying to modify or control the same device. I'm careful not to overlap. Once you have things to your liking on PG3 and there are no dependencies like an ISY then you can simply delete the NS from PG2.

Sometimes a picture is better than words.

Jumping here and I may not fully understand, but couldn't you use "fast_OFF" which is a double tap as a separate program to turn off all the lights. Otherwise it works normally on the Landry light?

Screen shots don't tell much as it's hard to see whats happening. But from the last screen shot I can tell you that the device at 192.168.1.94 is sending a SYN on port 23 to 192.168.1.232. This is basically the start of a conversation between .94 and .232. Then .232 sends it's own SYN acknowledgement. Here's how a basic conversation should look. The first devices sends a SYN packet to another device requesting that a connection be established between them. If the SYN is received by the second device, an SYN/ACK is sent back to the address requested by the SYN. finally, if the original computer receives the SYN/ACK, a final ACK is sent. FIN is sent by a device when it wants to terminate the connection; the TCP protocol requires both endpoints send the termination request. Welcome to layer 3!

What you are most likely seeing is multicast / broadcast traffic from those other devices. If your NIC supports promiscuous mode you could listen to all traffic that way or put one of your switch ports into mirror mode and mirror the port your projector is attached to. I would also say, you are doing great. Teaching yourself packet capture and how to analyze what you are seeing in Wireshark is way beyond the average persons ability.

I've been running a Polisy IoP in tandem with my existing ISY994i for about 6 months. Each has it's own PLM and they are both always plugged in and active. As long as you don't duplicate links I don't foresee any issues. The problem is if you have both ISY's trying to control the same device. Bad mojo.

@bpwwer Thank you. I was having some issues with PG3 last night and thought I had corrected them before I posted this. You are correct those attributes are exposed by the NS. Sorry to bug ya. Thank you for being so responsive and for all the work you have done on some many things!

http://IP_Addr/api/v1/commands/?cmd=next http://IP_Addr/api/v1/commands/?cmd=prev Thank you!

Deleted original post. I found that the AC not updating was happening with all node servers. I'm trouble shooting now.

@lilyoyo1 Thanks for your confirmation on the "change_no_pon" not working! As far as the variable, yes the light comes on if I run that program. That's what I'm trying to avoid using the "change_no_pon" setting. I want to be able to set different colors / brightness over a 24hr period. So in the morning when you switch on the lights I want bright blue light. In the evening I want orange / mellow brightness. But I'm trying to track the circadian cycle so the value for brightness and color will change every 6 minutes throughout the day. Step one is to stop the lights form coming on when I change their color / brightness. Then I'll build the program to increment a variable that will be added or subtracted from the current color / brightness. That value will then be used to set the current brightness / color. In the past I have hard coded 20 different settings for all the different times of the day. I'm trying to improve upon that.

I know there are a few others here that use the Volumio Primo. There was an update on 2/28/2022 to version 3.233 that broke the auto update routine. You will need to open a ticket for support HERE with Volumio and have them TeamViewer into your computer so that they can force a patch. It took about 5 minutes and the person driving knew what they were doing. No wasted effort. My Primo is now running on version 3.251 4/5/2022