larryllix

That would be an Insteon protocol dongle. Does ISY firmware support that on polisy? Sent from my SM-G781W using Tapatalk

Wifi is not supported by ISY firmware and may never be on the polisy. The basic polisy doesn't even have a WiFi card installed-, as I understand it. Sent from my SM-G781W using Tapatalk

@Michel KohanimGot my SiLabs Zwave dongle working with polisy today. It connected fine to two Zwave devices. Range seems fairly good through a ceramic tiled floor and thick support wood, behind a steel washing machine. Thanks to @io_guyfor pointing out this cheaper, and more versatile Zwave interface for polisy!

You were given good advice from several experienced users, that was consistent and all attempting to help you from their experiences with thousands of Insteon devices. Some are professional installers with years of experience. You were also given a contrary opinion from a forum newbie attempting act like an expert and being snarky due to being called out on his lack of experience with Insteon devices. He does seem to have a lot to offer in many areas though. Take your pick. People tried to help you and you have the right to discover what works, as your experience grows for yourself. You should have no complaint with the advice given, from people trying to help you resolve your problem. I suggest you read the thread again and think about what actually transpired. Many here love to help newbies come up to speed. Nobody is getting paid anything. They just like to see others succeed with their systems, as they have. This forum is known for it's good support like no other forum. All the best.

You are adjusting a scene (preset) with that command line, not turning anything on. Can you copy to clipboard, your program, and paste it here so we can see your trigger program?

I had to run through the SSH process also to get my ISY Launcher to connect successfully also, after using the automatic update in admin console. Many reboots and update/upgrades later all working with this help. Now V5.2.2 Thanks!

Wow! Your ad hominem isn't appreciated. You have no idea what I have been through on the Cisco front, since you wanted to use some brand's quickie training course as you example. Just let me say one thing on that note... I have likely hooked up and setup more Cisco equipment than you will likely ever see. I was on the ground floor of creating a fibre-optic network, connecting three medium size cities in Ontario, supplying most of the major ISPs with data and a few million subscribers. Currently that network has become an Internet backbone, after we sold the equipment to one of the three major suppliers for Canada. I won't publish the 8 figure money that transpired. That was a sideline from my real career where millions depended on me not making a mistake, every day. Not going into detail because some might wet their diapers. I have likely shoveled more snow in my life also, so that makes me an expert on Insteon protocols. Keep shoveling. It is getting deeper, but always factory reset every Insteon device that comes out of that factory. Some like to be sure of what they install.

All devices should always be factory reset before adding them to ISY. Hundred of posts and threads here have been from users having lingering links and setups inside Insteon devices that have messed them up for clean usage. Cripes I even had a new device, right out of the package, send out reverse status information. People have had ghost operations on devices that were receiving X10 signals left inside from factory testing or just bad manufacturing process bits left in the wrong places in device memory. Always factory reset every device before linking to your ISY. If the device was setup previously in ISY, a simple restore from the admin console will reset the links and scenes back to what ISY thinks they should be. If the device has any settings made outside of ISY these should all be removed by factory resetting the device. To leave links and setups in a device is asking for trouble, as evidenced by the number of ghost problems in these threads from many user over the years resolved by simply factory resetting their devices and restoring them or even having to start over.

Look for the programs that turn off your devices and disable or delete them. Are you the original owner of your ISY controller? Sent from my SM-G781W using Tapatalk

That depends on what type of imaging software has been used. Some do low level formatting and sectoring and some only do higher level imaging and do not understand low level sector formatting. I am not real familiar with the sectoring quirks of SD cards though. I just know many SD cards crash after being used for some time as the sectoring can be formatted for more space than the hardware can handle and then the software crashes. As time progressed, the sector tables for storage had several different limitations and larger SD cards and HDDs exceeded the limitations of the hardware at times. I think after you see how easy it is to get the latest image on a new SD card inside an ISY994, there isn't much need to store an SD card containing as old image that will be out of date every time you edit a program or update your ISY with a new update.

I did but it was s lot more work for a week to debug all the errors. Wait or start over. Sent from my SM-G781W using Tapatalk

Recreating an SD card for a ISY994 is very simple. Insert the card Connect via ssh and run the card format command. Can't remember. Run the admin console and load the latest ISY version image. Restore your best backup. May need to set your password, time zone and lat,longitude. Done The whole thing takes about 30 minutes. Format inside ISY guarantees format observes ISY sectoring and will not overrun the 2GB maximum capabilities of the card hardware. Sent from my SM-G781W using Tapatalk

Get a copy of puTTY and learn how to SSH into your polisy. Much easier and effective. Sent from my SM-G781W using Tapatalk

If you have electrical noise you may get that error due to bad comms. Have you factory reset each device before attempting to add it to a new PLM? I used an ISY994 backup and did a restore into pilisy for mine. It took about a day to clean and resave every scene and NR. Variables were crazy due to the reverse endian style of numeric storage styles and programs enabled and disabled took about another week to troubleshoot by errors showing up. AFAIK it is all working well right now while on vacation. I get regular reports of house health and network devices health each day. Sent from my SM-G781W using Tapatalk

I have never changed the default theme colours but I have had the font size change on me. However, IIRC, increasing the java memory size, allows the font size to be remembered and the admin console to stop hanging at random intervals.

The admin console is a downloaded piece of java software. I don't think it has any setting memory and the settings are kept in the java memory on the local HDD files. This seems to be evidenced by losing the setting upon installing a java update and clearing all caches.

Usually indicates your java environment doesn't have enough memory allocated. It may get reset each time you install a new java update also.

For ZigBee, utilities have been using it to create mesh networks between all their metering points with great success or it would have disappeared by now. Philips Hue has been using it with great reports of reliability. I had 6-7 Hue bulbs myself and the protocol just never missed. (Tossed them due to poor colour rendition ad extreme costs, though). Some tell me the ZigBee has no standards but others elsewhere tore my head of when I stated that. I was pointed to wikipedia articles on ZigBee standards that have evolved in the last decade and many claim that most devices just work flawlessly with each other. I wrote some bridge software for MagicHome bulbs and strips and would love to get my hands on a few pieces of ZigBee hardware and a protocol spec for same.

Not sure about that Tag data path. I thought it was the cloud server that instructed the Tag manager (local) to send out it's data to whomever in the URL's the user provides. @Jimboshould know much more about it and actually I wanted to ask him for a clearer picture of the data path from Tag to his NS to ISY. Kumoapps have been down for a few very extended outages this year, as you mentioned above. I also wanted to know if NS users experienced this as well. It sounds like they did from your attached comments. As far as ZigBee I want to research that more. From it's history it may be the goto protocol. There must be some protocol information that one can write drivers for it somewhere. A NS for ZigBee would be ideal to drop into polisy and be "one giant step for ISY home automation" AFAIC.

So a proper factory reset is working well then by your last post. Your problem sounds to be quite fixable and you just have to continue factory resetting devices properly, to rid them of old Hub links and remnants.

My apologies. I missed the local operation you reported. All of my 7 Switchlincs buzzers cannot be heard more than a few feet away. Make sure you factory reset each one. I had an OnOffLinc send scene on commands for about a year, in response to the on command until I power cycled it. The little computers inside can do anything in the event of a program crash. Sent from my SM-G781W using Tapatalk

Same polisy IPaddress but with port 8080. The ISY finder app will aitomatically locate it and offer http and https selections. Sent from my SM-G781W using Tapatalk

Endian problems everywhere ! Sent from my SM-G781W using Tapatalk

I would be a little nervous deleting nodes while some software at the source end, may be still trying to stuff values into memory space that could be dedicated to another purpose in my ISY. Talk about a memory leak? More like a memory overflow. Sounds like an HA user's troubleshooting nightmare. Sent from my SM-G781W using Tapatalk