MrBill

I know more than the average person about networks, BUT I still don't understand how the finding part works, nor do I understand what makes or breaks the named addresses (i.e. //isy or //polisy) from working or not working.

Finder has two type of records that are displayed. Those that it found on it's own, and those that were added via the add button. Yours appear to be the manually added type and your network appears to support addressing //isy. If Finder found an ISY the URL column would be showing an IP address type of link. So... Finder didn't find the ISY, but there are two manually ADDed records being maintained by Finder.

This doesn't make sense. Maybe it's a typo.. but if the scene is turning everything off, then the button should be non-toggle Off. (Not non-toggle On). If the button are controllers for the scene they will already be included as Controllers, however if the All Off it turning off devices that were turned on via another scene, that scenes controller button(s) will need to be included in the All Off scene.

Don't do that!!! If you do, you'll create more issues than you'll solve. At most delete a single nodeserver and reinstall it. Don't hard reset the Polisy and start over unless support@universal-devices.com or a majority of the people here in the forum think that is your best option. Like @larryllix mentions it appears your Dyson node server is an unhappy camper. Check its setup, try restarting it individually. Ask more questions here if you need help with the instructions. Worst case, delete that nodeserver and re-install it. Follow the instructions in the README.. (Click the name of the nodeserver in the store to find the README)

Finder: Finder is the program that locates ISY's on your local network and supplies the IP address to the admin console. If there is only one entry in the finder table it makes an assumption and opens an admin console for that ISY. While many people probably only have one ISY, its still possible to have two entries in the table--first the one that's automatically found from your local network and perhaps a second record that was manually added to access via UDI's portal (this would allow access to your ISY from anywhere in the world via a secure portal, without opening ports on your router.) The finder window is harmless I usually just leave it behind the admin console. The write changes button is a bit of a confusing issue, but before we tackle that topic lets cover did you factory reset the Insteon devices, then add them to the ISY? If you're trying to carryover a previous setup from houselinc by just adding the devices and trying to add previous links I wish you luck, at some point in time you will give up and start over from scratch. Nobody ever wins trying to import an Insteon installation from another platform. You didn't say what you're having difficulties changing, but to change the dim level or ramp rate in a scene you need to edit the scene, not the device. Also you must edit the scene multiple times, once at the root level and once for each controller in the scene. To reiterate that with an example: this is a simple 3-way switching scene with 2 switches, both controllers. If we want to change the On value or the Ramping Rate, we need to first click the Root level "DN Recessed OH (Kitchen)" and edit the scene there, this are the scene attributes when the ISY itself is the controller. Next we need to click each of the RED Controller links and edit the scene under each of those controllers as well. While most people tend to use the same values in all 3 places it is possible to customize and use different values in each of the three. Device attributes: Somewhere along the way.... the write changes button became less useful. When changing these values shown above it's NOT intuitive but change the dropdown on the right, then press the corresponding button on the left to write the change. In other words, change the Dropdown for On Level then click the button "On Level" to the LEFT of the dropdown... yea it doesn't make sense until someone tells you. Another important thing to understand is that Backlight has a bug around it's usage. It works fine for setting the backlight level... but when you move to the next device it will show the LAST setting, not the setting stored in the device you just switched to. So Set the dropdown, and push backlight it will write the change. Whatever the box says when you land on the device is going to either be 0% or the last value that you set. All firmware distribution is done thru the forum. The pinned threads contain download links AND INSTRUCTIONS for upgrade in the first post of the thread. The PINNED threads at the top of the listings are versions that are most current, the thread to The Launcher is also pinned. 5.3.4 is the most current version, technically it's a "test build" but it been out for a few months and no one has reported major issue. (Prior versions are no longer pinned but can be found with search.) The version you're running 5.3.0 is the last "Official release" but is a couple years old now. You're better off with 5.3.4. Version 5.0.16C is pinned because it's the last version that can be used in ISY's that have a series 300 Z-wave board installed. Version 4.9 is for those that haven't yet made the jump to version 5.

The problem is ANY Insteon traffic during the count will invalidate the count. Do you have battery powered device? if so how many? and are they easy to disable? If it's practical disable those by removing the battery. Even a heartbeat signal will throw the count off. You can prevent programs from running by creating an interger variable such as $cFalse or just $iTest and leaving the value at 0. then click the My programs folder at the top of the program tree and enter a folder condition: Since $cFalse (or $iTest) has a value of zero this statement will never be true and will STOP all programs that could interfere with the count. If you have nodeservers, temporarily stop them as well. Obviously you also can't turn a switch on or off during the count either.

I think you already did, but yea open a ticket... support is going to be your best venue for this one, everyone in the forum will be guessing.

What was the error? Also you might want to open a ticket... support@universal-devices.com

@Geddy, @jons7391 NOTE: Hue Emulator is not what it sounds like. It allows you devices like harmony hub to talk to polyglot by pretending to be a hue hub.

Personally I use Network Resources, however there is a Hue nodeserver in the store. I use NR's for a couple reasons one being my setup existed before I had Polisy and secondly a technical issue that wouldn't apply to 99.9% of other users that prevents me from using that particular nodeserver. Many use the nodeserver and no it wouldn't be going away.

too late now... maybe next time. that would be cool tho.

Why do you fear tickets? they don't incur charges or fees. I read this forum everyday all day... you have an edge case here... I don't recall this situation occurring since Polisy was originally shipped, I don't expect anyone to have a magic answer for you. You also lead with: But go on to talk about a problem with your Polisy and Polyglot. Are the two related? maybe, but we don't have any idea what has been going on with your ISY... You've simply lead the conversation with you've been having ISY issues, but then go on to talk about a Polyglot issue.

Hue may or may not need internet during initial setup. The solution works locally tho, no internet connection needed for daily usage. I went thru many choices on amazon and never found exactly what I wanted. I ended up ordering from an Amazon Vendor in China. Specifically this strip. Considerations included spacing, cut-abilty, and max-brightness (normal day to day use is 50%, but it's nice to have 100% from time to time. Color is neat, but we never use it, tunable white is mandatory tho. 24V because we have a long span. Don't laugh, but some of my Amazon trial strips got rejected because I didn't like the way they looked in the reflection on the counter top. The linked stripped has nice even spacing regardless of mode. nope. ------------- Edit to add: SuperLedLighthing ships fast... I've ordered from them twice, both times over the weekend, they shipped by Tuesday (China time) and I received both on Friday... less than a full week from order to receipt of product.

What kind of trouble have you been having? Have you rebooted polisy yet? After that if you are still having this issue you should open a ticket by emailing support@universal-devices.com For some reason Polyglot can knows the nodeservers are installed but thinks they are managed elsewhere (besides this polisy).

like @lilyoyo1 mine are controlled via Hue. I actually used a different strip tho with Glendopto controllers that talk to the hue bridge. The ISY has various programs that trigger when the overhead light is switched on or off, that tell the Hue Bridge to operate the controllers. There are diffident on and off levels depending on time, for example under cabinet lights in the evening don't turn all the way off, instead they go to 1% when the overhead light is switched off.

Since Insteon switches will work for you (e.g. 100-277VAC, 50/60Hz) I'd suggest using the native Home Assistant Integration which can use a 2448A7 USB stick as the interface.

1. They are functionally equivalent. 2. the spoken field in the device table isn't actually used. (it might be used by mobilinc with mobilinc connect, but I've never actually used that). Spoken for ISY with ISY portal is set later in the ISY portal. When setting up the spoken in the portal you would want to control the scene, so that all switches will stay in sync. 3. I didn't go to that extreme naming.... I just named what I called things. I'd suggest including a ~ in the name of devices that don't actually control a load. It's not supported in the UDI app yet but is likely coming soon as a method to hide extra devices. It's already viable to use that with the Univeral-devices Home Assistant Integration. to each his own... but I found it easier to take use a "TV table" or portable table and chair to areas where there was no table for a laptop. You can program, test, and not spend alot of time walking around.

If they're smart they won't sell the PLM as a single device unless it's for a premium....

Threads selling items appear periodically in the Coffee Shop section of the forum.

I remember now!!... just yesterday I wondered why I had a variable named "iDummyLastVariable"

It's not the same thing. Even from the factory devices should be factory reset. As @lilyoyo1 mentions this forum is filled with people that tried to make short cuts. Bite the bullet and do it the best way. It goes faster than you think.... For the record I started out that way myself... i was convinced I could add all the devices to the ISY AND keep the Insteon Hub too... it only took me a few weeks to just wipe it all and start over.... Yes. One notable difference is Hub to ISY tho is in the ISY you just designate it as a controllers. In the ISY Controllers are automatically considered Responders, unlike the Insteon Hub were you need to use "both". I'm not certain exactly what you mean, but the best way to do this is take your laptop with you. Do a room, take laptop to next room, etc. Not really... Factory Reset is "hands on" the device. The list of devices might help you because I think the "Input the address" method is faster than the error prone method of putting the device in linking mode and letting the ISY "find" it.

Interger Variables that don't change... used as Constants cTrue = 1 cFalse = 0 cBlue = 255 c30percent = 77 (30% of 255, used in dimming) Makes programs easier to read: If sAway = cTrue then......

You're not going to like the answer... but the best answer is: 1) Factory reset every device and 2) manually add it to the new system. The problem is that you're not just adding a device to ISY, the problem is that Links in every device need to be read as well as written/re-written. People that have added devices and scanned the links in the devices always end up with bad links, phantom links, full PLM's etc The best way is time consuming, but it will save you time in the long run.

Doubtful. more likely bad signal/noise/signal suckers etc. Do you have polyglot running either via Pi or Polisy? if so load the nodeserver ISY Inventory so we can see counts? Do you have pro or regular version of ISY? Pro does have a smaller node limit, although I don't recognize these symptoms as being that issue. You could also count links in the PLM to see if the PLM is full/near full. Tools > Diagnostics > Show PLM links table > Count. It should be noted that OTHER Insteon traffic screws up the count. If you can do it while no one else is home, and repeat it several times until you think you've got a good count. If you have motion detectors don't make motion during the count. If you want to stop all of your programs from running, create a temporary integer variable and leave it's value at zero, then click My Programs at the top of the program tree, Create a folder condition, in the IF for that folder enter a condition "If Temp_variable is 1" (Which is false, because the value of Temp_variable is 0)... and save programs... this will immediately prevent all programs from running... be sure to remove the condition and resave when you are done with the counts and want your programs to run again.

Is there another Insteon switch next to this one? like the light? same circuit? If so does it work as expected? If so this may be a defective switch. I'd pull the switch out of the wall, and wire it up with a test cord (cap the red wire) and plug it in to the same circuit as the PLM, and retest. (pic shamelessly stolen from a @Teken post somewhere else on this forum.)