larryllix

I only have two bulbs controlled by Insteon left now, after moving. However, I have about 20 WiFi operated RGBCW/WW bulbs throughout my apartment now. These run on LEDenet/MagicHome protocol, for which I wrote my own drivers that self-adapt to many different bulb revisions, including some White (CW+WW) only floor stand LED lamps. WiFi bulbs present no flicker right down to 1% brightness and are great to be able to adjust the colour temperature from about 2100K to 6500K. I use ISY programs to automatically dim them down from more daylight colours down to a orangey warm white, as the evening gets later and we do notice a difference in bed times lately.

Most LED bulbs do not offer enough leakage to maintain the dimmer circuit inside the control device. The dimmer has no waveform to lock onto for timing and when it shuts off the LED bulb circuit leakage then accumulates somewhat and the dimmer attempt to turn on again. A small incandescent bulb mixed in or wiring one of the small capacitor devices across one lamp socket usually fixes the problem. I bought a few packages of the Warm-Glow bulbs but they were the worst I have ever tried with an Insteon SwitchLinc dimmer. They would only turn on reliably at about 45% brightness. Home Depot refunded my money. HD has since discontinued all Philips bulbs in my area, Ontario, Canada.

I do not have an eISY, but two polISYs and they get warm also. I found routers that would crash on warmer summer days despite A/C in the house but, standing them vertically worked very well for increased cooling. I have several USB run muffin fans that I plug into other boxes to keep them cool. One was created out of surplus 12Vdc desktop box fans, however two are attached by permanent wiring, and one was purchased with USB attached from amazon. If there is cooling holes in the bottom, devices can lay flat on top of the 5 inch muffin fans with some standoff spacer legs.. The attached double units have a speed switch that was inside the media PC's case. I just run the fan on the low speed. It's enough to move the air.

I have a Govee Tower Fan, a Remote BT only Thermostat, an LED Array Curtain, and a LED String. Only one Govee devices could ever be found. I believe it found the LED Curtain initially until I installed the LED String. Then it switched over to that. I concluded the Govee NS could only handle one device at a time.

IIRC there was an instruction by clicking on the NS info in PG3x. There was a parameter to install into the NS setup in PG3 and it tells you about it in that info.

One more. I found ASUS routers didn't completely get a fresh start by rebooting them (I have owned four model now). When things got tough I always had to power cycle them. Reserved in the DHCP table makes the IP address static by the router enforcement.. Also defining it in a device makes it static.

AWAY is not VACATION. VACATION is a separate function with many more settings. AFAIK Vacations can be set fully on the thermostat or app where it includes dates and times for on and off, and also setpoint temperatures for heat and A/C.

This appears to be the same problem I had with my ISY994s, my polisys and possibly with eISY. From what I can gather: The power goes out and ISY products beat the router in powering up. ISY asks the router for an IP address from the router's DHCP server. Router is not prepared to be asked, and ghosts ISY, with no response. ISY tries again (x times?) and then gives up. Router boots up and sends out broadcast "Hello, everybody, I'm home" ISY doesn't hear it, or does not respond to it, due to being busy, or low level drivers still have some deficiencies with retries. ISY never tries again, and ISY never gets connected to router due to not obtaining an IP address. Years ago I had another WiFi based receptacle that could power cycle my ISY, as well as some detection software written inside my ISY that could automatically power cycle the router again with successive increasing time delays on retries. That seemed to rid my system of that problem. MY ISY counters did show some counts a few times over the years. Since polISY came to me, this happens occasionally but very seldom. It would seem possible that the O/Ses of both may be using the same C++ drivers.

Yeah possible but I thought it wouldn't be offered by the IoX on polisy. However to handle the problem it may look exactly as what happened. Just ignore it. Some flag message would have been nice though. My guess is you are right on this. The updating module only discovers it, (the mismatch of versions) after loading and doing it's preliminary testing, and then in a dumb and drastic recovery method, tells you to reboot.

I cannot get my polisy to upgrade to v5.9.3 at all. I have tried using ISY Portal and IoX many times but nothing ever happens after the time it takes to reboot etc. Messages are confused saying not to reboot and then flagging me I need to reboot. Java has been upgraded. Old files deleted and new IoX loaded several times but still showing v5.9.1.

I find I have to manually install the same URLs every month or two. However the save/restore works well and helps save some hassle. I have never found the app to find my polisys or my ISY994s, automatically, very successfully .

Have you checked your router DHCP Table to discover what the actual assigned IP address is? You may have to manually insert a new URL if the IP address has changed. or Add a fixed IP address assignment to your router's DHCP table and then reboot your eISY. BTW: Some of these upgrade take about 10-15 minutes to complete the huge song and dance they require, on the polisy anyway.

Ecobee API states they may cut you off and refuse to update polls if you interrogate their server more frequently than every 3 minutes. You may lock yourself out and require ecobee support to re-enable your account access.

I keep contemplating that style but have avoided assigning rooms until now. How would you operate the fans in another room then? Say to operate the fans in the exercise room from the back patio? Can two different names be assigned? Absolute and relative?

I have two polisy boxes. I had both go down at the same time (power glltch?). Re-imaging on SDD fixed one but the other would not. UDI support talked me through getting anew SSD and that fixed the other polisy. Apparently the polisy units used smaller SSD sizes and that makes them less reliable with less swap and rotate memory bits room. A USB to mSATA programmer runs about $10 on amazon and a new say 256GB SSD will run you about $40. Programming is quick and easy. After installing it, setup takes a few hours to load in your credentials, time zone, and backup files, and you are away. It wouldn't be that expensive to create a new SSD and if, not the problem, you would have a backup drive. It sounds like those polisy SSD only last a few years, anyway, from experiences here.

It takes some real thinking and creativity to fabricate so many names. There has become so many taboo words also that Alexa gets confused with. For my motorised blinds I had a big problem for different positions and finally settled on" Alexa... Open "full living room blinds" Close "full living room blinds" Open "living room blinds" Opens to about 2/3 and cuts some sky glare. Close "living room blinds" closes to about 1/3 but leaves a gap behind couch, or A/C unit in another location. Any other position of "partial" or "full" would make Alexa angry an I am tired of sleeping on the couch.

Looks like amazon strikes again. Suddenly my "TV Lights" started working again and things are back to where they started.

Looks like I spoke too soon. Again my main Alexa Show 10" screen started doing the "I don't know how to do that" response like before. This time, only one of the 10 devices did this, while still operating the ISY Portal devices just fine. All others answered "OK". A power cycle of this device seems to have cleared up this outstanding problem unit, for now. However, my "TV Lights" commands, I have been using for over three years now, will not function anymore on any unit now. Thanks amazon....NOT!

Looks like amazon must have discovered their error and corrected their responses to my requests. Now Alexa just answers with the original "OK" again.Howvere my "T V lights" seems to have become a taboo phrase now so I will have to use "television lights" for that function.

Not that I know of but you never know what gets forced on us sometimes. They are really pushing this phony, so-called "AI" guessing, everywhere.

@bmercier I seems amazon has changed something and caused bad response messages. When I vocally operate ISY Portal device I get back a verbal message "I don't know how to do that". My polISY programs still seemed to still be triggered, most of the times though. Nothing has changed at this end. I now tried to "Discover devices" with nothing new found several times. I have changed some Text in the ISY Portal for "T V lights" to "Tee Vee Lights", same thing happens using the "television lights" verbage command On/Off. This seems to be all some change at amazon's end, or some lack of feedback from ISY Portal to Amazon. Most commands still work but most or all, retort the "I don't know how to do that" error response. All my programs are listed as "switches" to avoid t constant asking "are these are lights?". I use On/Off commands via ISY Portal only. Mostly a heads up. Anybody else experiencing this new problem with Alexa commands?

How can you know the DHCP option is greyed out if you cannot get to the administrative console?

I would doubt the minimum freeBSD O/S likely incorporated into eISY would have USB drivers for this, but who knows?

The adapters are dirt cheap and work well. https://www.amazon.ca/dp/B07VP2WH73?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_3

I don't think the format is readable on the SSD by Windows after imaging the SSD. OUCH!