larryllix

Yes, Outback is one of the earlier era more top quality inverter systems for solar PV systems. I spent some time with Modbus, and more in DNP 3.0 before we went to Ethernet for electrical grid substation automation, just as I retired. When I started in 1974 I serviced tube and relay SCADA systems as well as some DTL systems. Left as Ethernet came into being. Would have loved to stay for that because it was right up my alley...but **sigh** time to go.

If you are dealing with Outback inverters they have another protocol laye on top of modbus, whereas the registers are dynamically assigned inside the modbus code. Fixed register numbers will not work with that higher level protocol.

I have a different brand and they have to be calibrated to the top and the bottom before usage. Has that been done before remote controlling them?

Very strange. I have used about 40 Insteon devices, and other than maybe 2 devices that came bad, I have only 2 devices that have gone bad since 2016. Some people have bad electrical noise that can get amplified via Insteon devices, or RF noise to interfere with wireless device comms. I would be looking to resolve those issues. Insteon is much more reliable than WiFi, most of the time in the homes I have owned. However, Chamberlain garage door openers gave me years of trouble until I found them and filtered their power plugs. I thought it was my 120/240v Outback inverters and just allowed it for years until my second Chamberlain GDO arrived and pushed my Insteon system over the edge.

I find it just stops working for no reason sometimes, Later it may start again but saving the URLs in a file helps expedite recovery times. My idea is that it sends out some "are you out there" signal and ISY, polISY, eISY and/or the new eISY responds with "Mommy. I am here" response. Sometimes they just don't hear each other and the child is MIA.

Look at the buttons on the bottom of the IoX Finder box.

I wouldn't jump to that conclusion. I use IoX Finder on two different laptops and after both finding my poISY for dozens of times successfully, either one may suddenly not find it at times. Then I have to reload my saved profile file and away it goes again. Either laptop can do this at random and I have never established a cause or reason for the random failure about once per two months.

You can increase the memory size but every update of Java will erase it again In today's world, we are pestered with updates on something every day or two. HTML5/CSS3/javaScript is coming soon, I hope.

SMS text messaging is not available to many people traveling. People do not want to pay exorbitant rates to get phone service for a week or two Usually most resorts (in Mexico) provide WiFi data, so emails are one of the only methods to receive notifications.

MS devices use many channels and each one establishes a link with your PLM. It is very common during disturbances and EPROM rewriting to MSes to lose or scramble one link. All the other functions may work, but one doesn't. Put the MS into linking mode and use IoX to Restore the device, by right clicking on the device in the device tree. If that doesn't do it, then try factory resetting the MS and then Restore it again. Sent from my SM-S711W using Tapatalk

I prefer not to add another dummy program just to run another a startup and try to use the function without another program. I have a few with Else sections that just jump back to the Then sections. Run at Startup would be much better as another program line that users could be aware that it exists without extra documentation, inside the program. A coding line for Run at Startup would also disclose the logic Run at Startup uses, and be controllable by the user usage of AND or OR logic. No extra confusing program or hidden checkbox would be necessary. Programs should be self-contained, not logic spread all over the webpages and jumps into the middle of other programs in spaghetti bowl style programming.

I also do that however it was never established what the logic is for [Run at Startup] is. I know it will fail with a time trigger because it appears to act like an AND function with the other IF logic making it nonfunctional. A few programs I have included a line Run ThisProgram[then] into the Else section to ensure it actually functions.

Key LEDs cannot be controlled directly, for some weird reason. The workaround is to create a Scene for each key, say KeyA, KeyB....KeyF, and drag and drop each key LED device into each scene. Now programs will be able to turn each scene on and off. Key LEDs can be dimmed as a group and turned on and off individually when they are part of a scene. They would then be the only device in each scene.

Also to be noted in ISY programming... Looping, of any kind, cannot be nested. Multiple programs must be used for nested looping. Sent from my SM-S711W using Tapatalk

I was big into energy monitoring years back, (spent a lifetime in the energy field) but now we have LED lighting and it is cheaper to leave a light on 24 x 7 than to purchase a smart home controller for the bulb. Make sure you are actually moving forward and let us know how it goes. If there is better out there, people will want to know about it.

Which brands are the perfect ones? Any lists?

I attempted this when I moved from ISY994 to polisy. I found most of it wasn't worth it but I think it may work with one CapU handling all Insteon comm devices while the other handled all WiFi and other protocols. The comm protocols are the bottleneck for the PLM and multiple PLMs will not help due to echoing them all over the house. It is easy to comm between ISY devices using Network resources talking to the other cpu device. Bidirectional gets a little trickier. Sent from my SM-S711W using Tapatalk

The 4000 lumen tends to line up up with the 50W actual. The size is pretty compact for that size though! Awesome light with selectable colour temperatures! Having had lots of RGBCW bulbs the 50 Watts may be the total LED draw but not all LEDs may ever be on at the same time. Perhaps only with one end of the colour spectrum.

Is that 300 Watts equivalent or 300 Watts actual? 300 Watts of LED lighting is a lot of light and not very likely. The LED companies love to exaggerate their luminescence values. Maybe the lumen ratings are visible on the fixtures?

I have only used the scene adjustment to adjust my bedroom lights for daytime vs evening vs night time, on individual lamps. This is the only scene I use now because the response time from a MS is fast. Most of my lighting is with MagicHome WiFi bulbs now. They are fast enough when operated with vocal commands and much much cheaper than LampLincs.

Scenes are presets inside a group of devices so they can all be controlled with one command. They were never meant to be manipulated on a usage basis. ISY has the ability to do this but you are reprogramming their EPROMS each time you do this and it takes some time (a few seconds each device) Use mutliple scenes (presets) or just set the level manually in each program. Insteon devices usually can store up to 256 different scene levels. There is no way to read the values inside a scene preset. The values you see in the IoX are only the latest values that ISY . If another device controlled the scene values IoX would not be aware of the change.

Getting a dual band SwitchLinc for the garage lights would be a usable pass though module, especially if it is on the same electrical branch circuit with your garage door openers. Now you could have automatic shutoff of the garage lights also, as well as increased lighting when the garage doors are operated.

I had two Chamberlain GD openers. The first one gave my ISY system intermittent problems for ten year that I thought was my house electrical inverter. When I got the second GD opener with MyQ and battery backup, it crippled my whole Insteon system from electrical and RF noise. Two FilterLincs cured that problem.

This is a problem that will not ever go away with Wait commands. When the Wait command is encountered ISY installs an absolute time into a stack to to be checked for that exact time to trigger an event or return to your program. Now when there is no absolute time between 2:00 AM and 3:00 AM (doesn't exist) your Wait expiry time never occurs. This has been discussed ad nauseum in these threads. Other problems occur when the clock return to STD time. The cure needs to evaluate each case on its own conditions and provide a fix to suit. IIRC there are about 6 different scenarios to be handled differently and they have not implemented anything that complex due to other technologies taking most of the development time. I always use some "all else fails" retrigger conditions in my IF section to circumvent loops stalling forever such as: If time is 7:00 AM OR time is 7:00 PM OR other trigger conditions THEN repeat every 5 minutes do something ELSE ------- I received a warning that my CAO Wireless tags heartbeat failed, based on a heartbeat signal every 5 minutes. I have since extended that test to 90 minutes to avoid these annoyances. Dear Doug Ford, Please stop the DST time nonsense and who cares what NY or QC is doing?

Thanks. I had thought it was the other way around, that you had ported it to PG3 as an abandoned plug-in.