BamBamF16

Folder auto opening is fixed. Clicking on Node column to sort does not. Just a random sort order. Consistently the same incorrect order.

Control is an event caused by actuation of a device only (not from a program or the AC). It may not necessarily cause a status change (switch is already on and you turn it on again). So it really depends do you want the program fired on an actuation event or only when status changes. So in this case the motion actuation is a control event and you want the program firing on the motion control is appropriate.

Post the actual program from the AC.

The admin console is correct. The eisy ui has the correct value options in the drop downs. But the upper status display is only showing True/False.

For i3 Paddles (and i3 Dial) on the flag node the options are: Mode - Relay or Dimmer Program Lock, Resume Dim, Relay at Full On, Key Beep, Disable RF and Error Blink are all On or Off. The selection drop downs are correct with the right options. It is only the current status on the top half of the screen that show True/False incorrectly.

I can't attach SS for some reason. But in the AC there is "Move to Temperature", "Move Temperature" and "Step Temperature". In the new UI "Move to Temperature" is not present.

Also, one of the flags, Relay at Full On, has incorrect data. It shows as True/False but should be On/Off. This is for an i3 paddle on the flag node. See SS. Also, the Mode should be showing "Relay" not True.

4.2 fixed my insteon node issues. Except I don't have any scenes. I don't see any option to "Move to Temperature" like the AC has. And it works fine in the AC.

Hue bulbs added via zigbee direct have some issues. There is no way to direct set a color temperature. Also the stepping is backwards (to me). If you set it to step "Down" in temp, the K increases (4000K to 4016K). "Up" does the opposite.

Add one more to the tally of users that have nodedef issues for insteon only items. ZWave and zigbee things seem to work OK.

It should have added more than 1 node. I got 4 for each bulb. One didn't do anything and I deleted it. The other three were groupable. The 2 sub groups allow color changes etc.

My direct connect hue bulbs work fine. Can set any parameter.

So I upgraded as per the directions. I am on 5.9.1 now but the OS did not upgrade. Not sure what to do now.

I have factory reset them multiple times. Then restore device. They actually work better PRIOR to the restore device. And the devices work great when the scene is activated by the AC.

Here ya go Also of note, these keypads have no loads attached. Just using them for scenes.

Does anyone use these with IoX that can give me.some.advice? They have been a hot.mess for me.to get working correctly. They seem to program fine but then don't work as expected. Mostly the indicator lights. But sometimes other things as well. With some scenes the indicator lights are perfect. Other scenes and the indicator light flashes when pressed a couple of times then off. Now all the buttons are set as toggle on so Tha shouldn't happen I have yet to figure out the backlight settings. They don't appear to do anything. It's like the isy thinks the devices are programmed but in reality they aren't fully programmed.

It's been a while since I've programmed an ISY ad we moved and were in a rental for a while. Now trying to setup new house. Am I just missing it or did they remove the scene Copy function to copy between controllers within a scene? I'm stumped and setting up scenes is God awful without it. And don't get me started but I tried programming in the app. That was beyond miserable. I hope something better is planned once the AC is deprecated.

The card snaps at that dotted line. Then it fits like butter. Scared the crap.outta me when I did it but it was intended to be that way.

I would consult with @Scottmichaelj. Just installed an M1 purchased through his company Alpha Concepts. Great working with him. Prompt shipping and great communication.

Can you set is init value at the same time to the variable value?

@MrBill said it much more eloquently than I. When a scene functions as expected from AC or Alexa but NOT from another controller it is almost always the controller version of the scene is not set as desired.

In the scene tree click on Rec Rm 4D.3D.6B.C so that it has a blue reverse highlight like LWR All On does in the last picture. Then evaluate the off/on status of each d3vice from there.

Show pic of the scene with the A button highlighted. That is what happens when you press the button. When using AC or alexa it's what'listed under the scene title. There arw multiple scene controllers and each needa to be setup.

I would goto PG3 the click details on node server page. Then configuration. Nodeservers should provide setup instructions. Most likely youll need a station ID or location.

Every night my NS fails, then disconnects, then reconnects. It happens at midnight and takes less than a minute. This just started after upgrade to PG3x. Additionally the NS functionally is very spotty. Plugs won't always be connected or function. Thoughts? Thanks , Jeff