larryllix

Something wrong there. Fixtures do not draw voltages. They draw current. Fixtures may be rated at 600 volts for maximum potentials, but that is not what they are necessarily fed to operate. Even in industry 600 volt lighting runs off of 346 volts, from each phase to neutral. In many places, 600 volt systems are not common, but use 480 volt systems, making the phase to neutral voltage used for lighting 277. Even then safety codes force use of metal switch plates and other enhanced mechanical equipment techniques.

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.

@bpwwer Since Govee seem to be taking off and releasing dozens of cool lighting gadgets, at decent prices, I installed their Curtain, and now the 5m RBGICWCW led strip. IIRC the Govee plug-in seemed to be working well for the Govee Curtain previously. When I installed the 5M LED strip it showed up in PG3x and my polISY and are fully functional but the Govee Curtain disappeared and is not accessable from my PG3x, or polISY, on IoX. Does anybody know if this plug-in can only handle one device? When I rested another api_key and installed it, the plug-in config removed the former one and replaced it with the new one. Also:It would be nice to see an update to the brightness level to match other devices 0-100% (not 256%)

However. I think the main issue is if UDI could make the option greyed out, they could have made it invisible with the same amount of quick coding. OTOH..we should have an HTML browser GUI coming soon. Then we should have a flurry of webpage writers making our heads spin with variations we never thought of before. Think..old iPads, or mobile phones, on the walls for control panels with temperature gauges, sliders for lighting levels. and whatever else you can dream up. Sent from my SM-S711W using Tapatalk

Looks like my estimation was fairly accurate. However, I don't find any API description document on that website, mostly only sales info for their silabs chip. There seems to be some discussion of some code but no actual code or links to anything. Am I missing something?