MrBill

I have a bunch of programs for a specific need. (Specifically being able to set specific dim levels of a Scene from Alexa). I found that if the Dim Level was set or subsequently changed manually from a scene controller the ISY never actually would get the changed value % correct. I worked for awhile at getting it correct (my Insteon system doesn't generally have noise issues). In the end I decided for my programs purposes I didn't care of the ISY knew the exact correct value, instead when my programs see Fade Stop they store the value 101 in a variable which I call "ON, specific level unknown). (value 0=off, 1-100 = dim level that Alexa wants to set). I did discover that you could add a Wait for a few seconds (to pause and wait for the powerline to settle down), then add a query to the program to update the ISY, which would get the value corrected in the ISY. I didn't use that method in the end however.

If it works sometimes it doesn't sound like a bad iolink, it sounds like line noise. When I trouble shoot line noise I turn off the majority of the circuits in my panel and test. With Insteon tho all but those two circuits (ISY and Iolink) might be too many at once. Keep in mind if those are on opposite phases, you'll also have to leave on enough dual band devices for the signal to jump to the other phase. When looking for a new noise generating object, that just started causing issues, I tend to identify the ISY circuit and the problem circuit, (and the circuit with the router if different that the ISY circuit). Then unplug or airgap everything else on those two circuits. Then I turn off every remaining breaker on half the panel. Noise still there? Turn that half back on, turn off the other half. Noise gone, turn back on half of the breakers that are off? Noise gone or present... continue until you find the offending circuit. Then go on a hunt of devices on that circuit. .... of course before you do all that, ask yourself if you've plugged in or installed anything new around the time the problem started. (in my case that recently was a new cordless vacuum charger.)

I looked for the specs on Intermatic's site, they don't list a minimum load but that would be my concern. I'm thinking about a case where we replaced a photocell for a customer many years ago. The total wattage in the fixture was like 25W, but the replacement turned out to have a 40W minimum--- we figured that out after several days of head scratching. Unless you already have those parts laying around, for the price of the photocell and micro module you might consider something different, like a motion sensor with a light sensor, or a (CAO) WirelessTag with a lumen sensor.

According to the Wiki V4.3.26 is the minimum version for the portal. As noted use The Launcher to ensure that your firmware and UI versions match. I'm not familiar with that message: did you follow the instructions here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions Launcher instructions are here: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop or here:

You need the serial version. And at the moment they are out of stock everywhere. Rumor has it the first of the year they should be back, but I've not seen that offically posted anywhere.

I believe that total nodes also includes scenes: 79+294+0+74+3=450 BTW, thanks much for creating this nodeserver... I never could count this stuff accurately before.

Which brings up a good question, since program folders do count towards total number of programs (300 for non-pro, 1024 for pro) are they included in the program count?

I upgraded to 0.1.1 this morning. I closed admin before upgrading. Numerous tries of Restart, query, rediscover, update profile, closing re-opeing the admin console never got Folders to populate. Finally uninstalled the nodeserver and reinstalled and it finally populated.

Are you aware that the Ramp Rate and On level are different for each controller? That is, when defining the scene setting the Ramp Rate and On level at the root level are the values that will be used when controlled by the ISY or an ISY programs. Also click each Controller listed with a RED name within the scene and set the Ramp Rate and On Level that occur when that specific controller is used. As for the program, 'Control' would be the feature you would want to use. however, if there are multiple controllers you must OR them all together and realize that "Switched On" (single tap) is different that fast on(double tap), or hold button to dim. At the bottom of this post is an example that catches all the possibilities from two different KPL buttons. With 'Status' I have the most luck using "is Not Off" and "is Off" in an If statement. ---- Manual.on - [ID 00A5][Parent 00A7] If 'DN Back Door Recessed+# / {hide}Lamp 4' is switched On Or 'DN Back Door Recessed+# / {hide}Lamp 4' is switched Fast On Or 'DN Back Door Recessed+# / {hide}Lamp 4' is switched Fade Stop Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched On Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched Fast On Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched Fade Stop Then $Dim.Lamp4 = 101 Else - No Actions - (To add one, press 'Action')

I wonder if you've reached the maximum number of nodes? Do you have a pro or non-pro ISY? Max nodes non-pro = 254, pro=1023 There is a ISY Inventory node server that will count for you, but if you can't load new nodeservers that's not going to help. If non-pro, you can upgrade to pro version, its a soft upgrade, no new hardware required.

Waits are interrupted anytime an event happens that causes the IF to be re-evaluated. If you always want the wait and action to occur another method is: Program 1 IF some condition Then Run Program 2 (then) Else (none) Program 2 If (none) then Disable Program 1 wait 2 minutes turn off Enable Program 1 Else (none) Or if you want the time to always be extended, that is 2 minutes from the last activity in program 1 then omit the Disable and enable in program 2.... which will cause the timer to be restarted, by program 1 with more switch activity, but will always eventfully end the 2 minute wait and turn off the device.

This is how I dim scene's via Alexa: I'd do the Launcher First, that way it always starts the admin console with the correct version, both before and after upgrade. Note: If you have an older Z-wave board, do not upgrade to version 5.3.1, or for that matter any version past version 5.0.16C. How do you know if you have an older 300 series Z-wave firmware? Look at the back of your ISY, next to Port A If you see a BLUE LED or round dot then shine the flashlight on your phone at the round dot, is it a BLUE LED? If YES, the farthest you can upgrade firmware wise is 5.0.16C. If you wish to move to 5.3.1 you need to upgrade your Z-wave daughter board first, UDI has special pricing based on the age of your ISY.

Glad you worked out your issue. Note however that Firmware and UI versions should match. While there are various ways to run the Admin console the best method is to use The Launcher which will ensure that you start the correct version of the UI... Follow the instructions here to begin using The Launcher:

Factory reset and Reset UserId and password are very similar procedures. Effectively what you did was hold the button too long and perform a factory reset. Then you reloaded a backup which in turn reloaded the unknown username and password again. What you need to do is let go of the button at the point for username and password reset.

The motion sensor also has a light sensor, the program is using it as a heartbeat, its assumed that at least twice a day the dusk to dawn light sensor will change states to either on or off.

As others have said.... you need Pro for them to show up what others haven't said is that Pro is a software upgrade, no new hardware required, pay the fee and you're upgraded. Here's a chart, with the differences, largely you get the ability for more nodes, and more programs, and the ability to use batch mode which are the two buttons mentioned.

Since I don't use that nodesever I don't know but lets tag @bpwwer since he wrote the nodeserver.

Disclaimer: I'm not using that particular node server so I didn't double check that the temp is available to set as a variable. Generally however, variables can be set to numeric values available from Node Servers: Set the first drop down to "Variable", then the Variable you wish to set then use the arrow to the right of = to cycle until you reach the node view, then select the node and which value you want to save from the node. (make certain the precision (number of decimal places) of the variable matches the value being stored.)

You can also "compare links"...caveat tho, unless you understand the results it may flag a false positive. Click a device name in the tree, then right click it, Choose Diagnostics > Show Device Links table. When that table is done populating click Compare. This causes a comparison between the links table in the device and what the ISY thinks the link table in the device should be. If the only mismatch is I believe the first byte after the colon, it's not really a mismatch. To fix, right click device and Restore Device. Another technique is to factory reset the device and then click the device and Restore Device. Using the second method, you've cleared the devices memory and then restored it, without the hassle of deleting it from the ISY, readding it, and then restoring scenes, programs, etc.

Never said the browser was a server. My theory is tho that the .js script running in browser that we can see by viewing Page Source opens a database connection back to Polisy. Likely why they force https on all Polisy pages served. Mine are only guesses and theories, and I won't spitball more about my guesses. I'll be happy to test anything for UDI and assist. As I said up above the outcome at this point doesn't make too much difference to me I don't use this method to access Polisy even while traveling. I read OPs post and said "I wonder if I have that problem or can spot a solution"---so I opened my iPad and tried everything I can think of... including multiple browsers and multiple devices...the only common denominator seems to be iOS itself.

I don't think its a connection to the ISY problem. First it works from other non-ios devices just fine. Second, nodes in the ISY are updating. I've seen the red connections banner at times on my windows laptop but it also goes away by refreshing the page. Obviously the web server on Polisy is working. If I had to guess, and its only a guess, I'd bet on a database connection from code running in browser not being allowed by iOS for some reason.

You can't mix and match neutrals between different circuits. I don't see why you can't install a keypad in the unused switch location, just connect hot and neutral from the same line to it, and put a wirenut on the red lead from the switch.

The only way I've had success using Status is "Is Off" or "Is Not Off". I don't recall for certain, but I don't believe the comparative operators < > <= >= existed in the 4.x branch. They may work with some node type and may not work with Insteon.

I believe that if you don't disable them they will run every time the temp moves. Disabling them will cause them only to run when called by the time program.

I agree with your quote, but have had trouble using Status, I just looked and I have programs where if Device Status is not off then wait turn off when I used control my If bodies do tend to be complicated, such as: Manual.on - [ID 0099][Parent 0098] If '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched On Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fast On Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fade Stop Or 'Kitchen Table Light# / {hide}Lamp 1' is switched On Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fast On Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fade Stop Or 'LR Remote -Deb - A-B' is switched On Or 'LR Remote -Deb - A-B' is switched Fast On Or 'LR Remote -Deb - A-B' is switched Fade Stop Then $Dim.Lamp1 = 101 Else - No Actions - (To add one, press 'Action')