larryllix

Nice! If the KPL was all ISY program driven you could use my combination lock for enabling / disabling the programs.

The "1011" symbolises binary code to be written to the ioLink. ISY is trying to update the data and can't or hasn't yet. Right click on the device and select Restore. Write Updates (See PB below) If this doesn't clear it up then you have a communications problem. I trust you factory reset this device before linking to your ISY? This always needs to be done, when new, to avoid many problems.

Just the indented line underneath it. If more lines followed they would all be indented and repeated until another "repeat 1 times" is found.

As per Paul's sample program above.... When the door is first switched ON, run the Then section until it finishes. However if the door lock ever becomes NOT ON, then quit running Then at the next Wait or Repeat, and start running Else, code or not.

My logic is New users should be enticed with a free trial. New users should pay for initial development Old users should pay for server and software maintenance. Really old users, like Teken, should just pay as much as they can

Too complicated but I would like to see a 30 day free trial, a $50 for the first two years and a renewal fee of $10 - $15 per year after that. Sent from my SM-G930W8 using Tapatalk

Some of my GH minis do this randomly at times. One will say there is no connection to UDI and Alexa functions normally right after. Next time the GH works fine again. Very sporatic.

The slight delay for human operated switches to lights or devices isn't that bad. When it's in between an MS and a light/lamp then it seems like forever.

Correct. Without JRE there is no ISY994i setup or editing programs.

Ditto When echo doesn't understand all words it will sometimes tell you it found more than one "possibility". It lies a bit but gets the job done. Lately I get a lot of bad reports from echoes with it "can't find anything fitting that description" and does it anyway. Or agrees and confirms but doesn't do what it's asked. Google Home just makes an assumption and operates anything or everything that comes closest in sound Sent from my SM-G930W8 using Tapatalk

ISY doesn't like it when you try to bypass her. I wonder if a special scene activated from ISY to turn off all the LEDs would attract less attention? Air-gap? Breaker? Program to detect functions and reverse them immediately?

Control / switched would cause it to trigger every signal. Status will only trigger once. In the Belias programs he gets around all these problems by setting a variable flag and then sensing the variable / flag state. You can only set a variable to X once and make it change. Works as a "Once and only once" logic.

Those are the hardest ones to solve!

People have no rights to their purchased computers anymore. You just get what you are given on your "rented" machine now. Usually this ricochets back to you from google asking if you want to approve this before allowing it.

The powerline signal has a much farther rating than RF. If memory serves the powerline signal is 500' and quite possible it will travel to the pad mount transformer and back to the outbuilding. There will likely be no passing "through" the pad mount but dual band units at the other end can transverse the phases with Insteon. Making the outbuilding a sub service from the house or vice versa would make less dual fixed charges on your monthly bill. Dual first rates may be a bonus though, depending on billing structure. Is the transformer between the two buildings somewhat, assuming dual feeds from padmount, or where is the split in services done?

This becomes much more critical with all the laminate flooring happening now. Most of it is a hard surface / wear layer of something backed by compressed cardboard. A bit of water plus an half an hour, it's wrecked and all needs to be replaced. Now you pull up your baseboards and trim that will cost you four times the price of the cheap laminate.

Did you create the scenes using the admin console?

I had an Insteon Leak detector against the foot plate of my dishwasher for a few years. It got kicked around and kicked over many time. I had a leak that never triggered it as it ran out the side. Fixing the leak damage I now have the LD under the dishwasher without any problems in the last year or so. I missed one heartbeat in that time. This unit turns off my well pump, rings local beepers, and notifies us four different ways. With 3000 feet of piping in my basement slab (open system) there is a fair residual pressure to drain off but the dishwasher is on the main floor and should dissapate the residual water quickly. I know there will still be water damage but I will not come home to a basement swimming pool. The LD is surrounded by metal on the front face but the other three side are wood cabinet materials. It works fine.

Each aspect of an Insteon device can be a separate link. In the admin console there is a feature to download links from any device and then a compare button to check them against what ISY thinks should be there. Or you can just right click on the device in the admin console device tree and select "restore". Battery devices have to be in linking mode first before doing any of the above. It's a battery saving feature they have.

Only if ISY knows the scene changed. Many operations do not change the scene and are not reported. I have overlapping scene device lists and some scenes may change the status of a device and yet the scene is still reported as on. eg. I just activated my Gathering Room Off scene to 'On'. All lights went off and MobiLinc reported the scene to ON. ISY handles it and operates the scene anyway. Then I operated my kitchen bar lights on from the switchlinc. ISY is aware of it but no programs are triggered. This was a device operated in the OFF scene but the scene still reports ON in the REST interface to mobilinc. Scenes created outside of ISY will not report their changes to ISY. Study the scene protocol in the SH white papers.

I block all my similar types of devices together by function, so my ISY and related input devices are all 0.160- 0.169. RGBWW lighting 0.140- 0.159 etc. Printer and system stuff 0.100 - 0.119 etc. Then my router assigns guest devices randomly, starting at the bottom by native DHCP, at 0.010 - ? Right after my four routers 0.1, 0.2, 0.3, 0.5

Your quest really caught my eye. It was freaky you assigned exactly the same IP address as I did my ISY.

192.168.0.1 will be the IP of your router, not your ISY. Look inside your router for the IP address your ISY is using.

Yes. Your router will assign the next available IP address within the range of 192.168.1.2 to 192.168.1.254 (you have set) less any already designated IP addresses within that range. Using the DHCP reservation table in the router will assign devices into that range only and not allow any conflicts. As I stated before, using the 192.168.1.xxx address range may find you in trouble with some new devices. Many new devices have factory defaults in that same range and if their IP address conflicts with another device on your LAN you may not be able to configure them and not realise why your system has more trouble. However this setup may allow you to access your ISY to turn on DCHP and then you should be able to change your router range to whatever you want, rebooting ISY each time to do a new IP address grab.