larryllix

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%)

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?

Where is the local API? I haven't seen anybody that even knows what Matter is, let alone why we would need a new piece of hardware to broadcast a protocol over WiFi hardware that is already built into every router EISY is attached to. From what I can deduce, Matter is just a standardized way of interrogating a device to find out what it is, and what parameters it will accept. That sounds like a huge database to handle every style of device that can be thrown at the EISY. However, I detect the same secrecy for Matter, no different than every other protocol that was destined to fail because the manufacturer always tried to keep it a secret, or was too lazy to write an API document, that programmers could understand and support their products. "Total control...end to end" (we won't mention the EU threat of banning that one! ) I sure hope I am wrong in some of these assumptions.

I have a Govee LED curtain light set and it supports BT, WiFi, and Matter. Alexa sets up with it automatically when permitted. That is over WiFi via the Alexa server through my fibre router and Wifi. Router is a few years old and belongs to the ISP. Just the same old 2.4GHz WiFi AFAICT. Nothing special about this router so I don't understand what the big deal about Matter is.

Does V5.9.1 have support for that bulb yet?

I had one of the early release polisys. IIFC there was an early BIOS chip that had to be udated. UDI spec'd a microSSD to USB interface and gave me an image to update the BIOS, and I still run my polisy with the latest updates. IIRC the USB/microSSD adapter cost about $9 on amazon.com.

Thanks Goosgle! Goose gives little hints called.... .....goslings!

@Guy Lavoie Many apps have learned to ask the google android spy network what your SSID and password is now. I guess the assumption is if you allowed it to install then you already trust it with your credentials. Hassle saver but scary. AI (oneUI guessing?) at your service.

Write the text down in the QR code on the side of the bulb. I write the MAC address on the side of all my WiFi bulbs.

Then you will still be running. v4, similar to running MSDos. Beta means all the 1000s of devices are not installed yet. Sent from my SM-S711W using Tapatalk

..or jack up the price to pay for a support person. People here are happy to help donating their time and actually have used the equipment, instead of just reading a fake AI monitor with a language translator. Sent from my SM-S711W using Tapatalk

@CoolToys Yeah I thought about trying the split IP address technique. Trouble with that is, when a device connects and asks for an IP address assignment from the DHCP server, both routers would see only it's MAC address and both attempt to assign it an IP address from both ranges. There is no "steering" mechanisms. This is not "bridge mode". That could be done with most routers but then the user supplied router, in bridge mode, has it's DHCP server disabled. Only the master router assigns IP addresses and contains the NAT storage. Using the Bell HH4K DHCP server is the problem. There is no backup/restore facility. PPPoE was the real only way this could work, allowing the HH4K router to just act like a dumb modem, and Bell has disabled this function in their routers. Bell will not allow and will not support another modem on their fibre lines. The Netgear went back for refund. I am considering a different ISP now.

Looks like this will only be the second upgrade I won't install since v3.xxx when I bought my ISY994. Too scary and the upgrades don't matter yet.

I think that should have been (typo) $Timer -= 1 For more complete If $sTimer > 0 Then Repeat While device is OFF <---- avoid repeated useless comm traffic if desired Set device ON Repeat 1 time(s) Wait 1 second $sTimer -= 1 Else Set device Off Now to turn device on for X seconds, and automagically turn it off after X seconds. $sTimer = X

I wrote my own interface and had to update the firmware many times each time a new version of the bulbs came out. Then white variations use a completely different level technique also. I have them all compensated with patches now and they work well. I can control up to 10 bulbs simultaneously on the fly with some ISY program code and 3 NRs. All software is contained inside my polisy. Sent from my SM-S711W using Tapatalk

Tariffs are starting on all sides. I buy my equipment, made in UK or S.E Asia anyway. Things are not healthy with this trade war somebody started. It's a way for our governments to take money out of our pockets and many happily support it.

Oh Jeez. You mean we are going to hear... 'are we almost there yet?' ....'are we almost there yet?' . . . . . . . .'are we almost there yet?' over and over? Reminds me of V5.0.1 Sent from my SM-S711W using Tapatalk

Plus or minus 90 days, based on the coding world realities.

Sounds like two guys in Michigan are already setting up a date. Here's hoping you don't have to pay a tarrif on my Canadian data bits.