Bumbershoot

With the new PLM in the FCC database (4000 links), then this might be practical, provided it works.

Update to this thread: I purchased a reconditioned LiFX + BR30 Night Vision Enabled bulb to place in an outdoor soffit fixture. It's controlled by an Insteon SwitchLinc dimmer switch. I set the dimmers "On Level" to 100% and the "Ramp Rate" to 0.1 seconds. The purpose of this light is to illuminate an area at the rear of the house that is covered by cameras. The previous LED that was in the fixture needed to be sufficiently bright for the cameras. This caused a fair bit of light leakage around the window dressings in a bedroom. The LiFX light, however, emits infrared when turned to very low light levels (currently, I have the light set to approx. 2% illumination at night), which noticeably helps the cameras, and greatly reduces the light leakage into the bedroom. The light is controlled by the LiFX Polyglot nodeserver. The light turns on to full brightness under certain conditions when motion is detected by the cameras, and the response to motion has so far been rapid and acceptable. The color temperature of this bulb has been set to match the rest of the LED soffit lights, so the exterior lighting all looks uniform. The SwitchLinc dimmer controls this light perfectly, as long as the "On Level" is set to 100%. I haven't tried setting the "Ramp Rate" to anything other than 0.1 seconds. The switch is completely controlled by the ISY, and is almost never physically touched. In any event, this setup works fine.

I know you need to enable the Java cache, so you might try clicking on the checkbox shown in your screenshot. I don't run Windows but occasionally in a VMWare prision, so I'm not certain about Windows firewall issues. I just started the AC using "start.jnlp" after completely updating my Windows installation, and Windows Defender complained. You might check your security settings.

You saved 'start.jnlp' to you desktop (or wherever), and ran it from there? It sounds as if you're still starting the older version, "admin.jnlp".

Nope, you need the file: start.jnlp You can download it from the link below. Nobody needs any holiday stress from their HA systems... ?

Are you using the ISY Launcher to launch the AC instead of your browser? It works like a charm on my iMac.

I’ll be back next week, prior to turkey day. I’ll look at my service file and repost it. I bounced NodeLink just before I left, and it started successfully and continues to run (I get several notifications daily that report changing values in NodeLink nodes). BTW, my experience with NodeLink on an RPi has been exceptional, both with Mono and now with DotNet. I’m expecting the same when I install it on my Polisy. No crashes, no nonsense.

Sorry, I'm traveling so I can't look at the script on my RPi, but I notice right away that you're calling 'nodelink.exe' instead of 'nodelink.dll'. You might edit 'nodelink.service' to see if that matters. I really haven't touched Windows machines much in over a decade, so my expertise with Windows executables is low.

I’ll bet that Polyglot sees nodes left over on your ISY. When I did this, I deleted them on the ISY from the Nodeserver | Configure menu, restarted Polyglot and all was well.

If you can get far enough along in the boot process to get a command prompt, then maybe you can "sudo killall deamon"? The continual restart problem has been noted before in this thread. I'm not entirely sure, but you may need to drop the database. There's information in this thread.

I got 2.2.6 this morning with a regular update, so it appears that 2.2.6 was promoted to production. That's the version that you should get now.

I understood that the "Geek Batch" shipped without the Admin UI, but it will come with the production units. Earlier in this thread, Michel posted this, "With regard to Basic UI, well, that was the whole point of delaying the release date while giving you access to the unit. The UI is in the works and will allow configuration of network, wifi, etc. Bluetooth is a little tricky since, currently, there's not much we can do with it. But, all the drivers are there and are loaded at start up. "

Smart! The cameras are there for her peace of mind... ... and she HATES spiders! ?

Understood, but the point would be to not have visible light creeping in through the blinds at night unless motion is detected. If I can get one of these in the next day or two, I'll run a test and see how it does.

Mine as well, but I have two locations where the lights are adjacent to cameras. Now, I have to leave them lit, though at low levels. It would be nice to have no visible light at these locations unless motion is detected by the cameras. I'll probably give this a try later in the month.

I noticed a few more homes with similar setups in my area this Halloween, but most homeowners haven't made the investment, yet. Are you using any of the BR30 + (infrared) bulbs, and if so, how much do they help with your cameras?

You sound like a man who has been around the block on this. ? Thanks for the perspective. While there's no way I'd spend the kind of money required to populate my entry light with these things, I'm impressed with their functionality. Maybe a nightmare to program, however...

Except... There are obviously people for whom $50 is chump change, and for them, there's this: https://www.lifx.com/collections/lamps-and-pendants/products/candle-color A dozen in the hanging lamp in the foyer might make for some spectacular effects... 26 addressable zones in a single candelabra bulb? That seems like a huge leap in functionality.

I started out with them, but in an art studio, we prefered the lumen output and color saturation of LiFX. Otherwise, I liked them. I have a relative who's happily using them.

Yes, not becoming obsolete/unsupported. Other than that, there are some nice new abilities in the programming environment, as well as some nice changes to the "adjust scene" functionality. I suspect you'll have an easy time of it. You may have to re-save some of your programs (the program icon will be yellow if this is the case). Mostly, with only Insteon, it hasn't been too big of a deal for folks.

I've got really stable power here, along with whole-home surge protection so I'm thinking about wiring them so they're always powered on. I'm not completely sold on the idea of having no way to turn the current off except at the circuit panel, however. Is that being over-cautious?

Turning them off can cause some problems with the LiFX nodeserver. If they're off upon nodeserver startup, then they won't be discovered. There are two possible mitigations to that: the LiFX nodeserver does provide for a text device list, making no discovery necessary using your reserved addresses (I'm currently not using a device list so I can't test that theory). Also, the LiFX Controller node does have a "Re-Discover Bulbs" function, so if you programmatically turn on the switch, you should be able to programmatically re-discover the bulbs after a period of time without having to restart the nodeserver. Also, another untested theory. So, in theory, your idea might actually work fine with the nodeserver. I haven't fussed around with it enough to find out.

Fortunately, I have one of these. A nearby neighbor lost a bunch of fancy doodads in a storm, but nothing bad happened here. Okay, I get the point. The accidental presses could cause issues. The Mrs. and myself are accustomed to seldomly touching the switches in question, but that doesn't account for others. I still like to have a physical means of control, if it's available, though I have several devices for which that's not practical (cameras, outdoor on/off modules, micro devices, etc.). I admit, logical control is often preferable -- we almost never touch inconveniently placed SwitchLincs, and only occasionally touch the convenient ones. If I could find good motion sensors that didn't look like barnacles, I'd have them all over the house and never touch a switch again.

I'm not sure I follow. Wouldn't the switch take the hit, leaving the bulbs unaffected?