randyth

Yay! Glad I could help. @Michel Kohanim, perhaps someone could update the readme to include the fact that the latest RPi OS won't work with PG2?

If you use the Raspberry Pi Imager, choose Raspberry Pi OS (other) and then select Raspberry Pi OS Lite (Legacy). After installing PG2, follow these instructions to fix the “ee key too small” error. Then you should be all set.

Yeah, I can forgive a device for needing Wi-Fi to talk to Sonos, Ring, etc. But I draw the line at not being able to turn on a 3-way light switch if Wi-Fi drops out.

I looked into Orro but never purchased one because reviews talked about how hot they get and how the screen is really too small (and low resolution?) to be useful. The real deal killer for me was that the switches can't talk to each other -- or anything else, of course -- if your Wi-Fi/LAN drops out. My Wi-Fi is pretty reliable, but I own enough Shelly devices to know that this would drive me crazy.

I definitely worried about that distance limitation. I understand that Brilliant utilizes a s mesh and I've no problem so far with a switch that is much farther than 15' from the mother-ship controller. That said, it's early days and I only have three Brilliant dimmer switches in my system to date. I love these switches so much (they have no moving parts to break along with built-in motion sensors) that I have ten more coming. I'll give an update once I install them in more distant regions of my house -- all to replace dying Insteon switches. FYI, Harmony hubs are BT as well and mine are at least 40' from their remotes and work fine. I have a headless AV system with Harmony hubs all located in a central area where a 4x4 matrix marries them with all my TV + streaming devices.

The Brilliant-brand dimmer switches and smart plugs communicate with Brilliant's in-wall Controller using Bluetooth. You need at least one Brilliant Controller for any of the Brilliant-brand switches or plugs to work. I have no idea how their Bluetooth protocol works, but if they chose to they could absolutely allow ISY to talk directly to their controller (and vice-versa) over local Wi-Fi.

Thanks!

Me, biased? You're right, of course, but it could be argued that their device did not not properly implement the UPnP protocol. Bugs are in the eye of the beholder. I remember often jokingly arguing with my QA department whether something they reported was a bug or a "feature." :-)

That's a lame response from Brilliant. The fact the Brilliant Controller ignores the port number HueEmulator feeds it is, in my opinion, a bug. Their product roadmap should prioritize bugs.

I agree with @larryllix with how distasteful it was to "pollute" my setup with another hub/bridge requiring me to create yet another cloud account, especially one that pretends to do a lot of things ISY does far better. (Alexa is a similar pollutant I could not resist.) Of course, when their hub looks like this, I just had to try it out: I'm not planning on using the hub/bridge part of Brilliant to do much more than interface with Sonos and Ring, something ISY can't do properly without a screen + UI code. All other home automation logic will still be done on my ISY. I do also really like Brilliant's Dimmer switches. And, the Brilliant Dimmer->HueEmulator->ISY works very well. For example, I have a 3-way setup where the load switch is Insteon and the other is Brilliant. It works surprisingly well. I just wish I didn't have to go through Alexa (requiring a round trip through the cloud) to make the ISY control Brilliant. I cannot recommend Brilliant to anyone at this point. It's too early days for me to make any endorsements. But so far it's been a (mostly) fun adventure.

I'm looking forward to a crypto coin of the month club card.

Me too, but they are a relatively young and growing company with more pressing things to do at the moment. I remain optimistic that they might release one... someday. For those who want to pester them, you can request they release an API here: https://support.brilliant.tech/hc/en-us/articles/360017751831-Does-Brilliant-have-a-public-API-SDK-to-integrate-with-

https://www.radioshack.com/ RadioShack: "Bringing Cryptocurency To The Mainstream" Say what?!

Ah, you are right, of course. The Brilliant<->ISY connection would most likely be through a node server. The problem with the HueEmulator as a solution is that it only supports features offered by Hue devices, and it is a one-way connection. That is, it only allows Brilliant to control ISY devices, not the other way around. If Brilliant offered an API, someone could develop a Brilliant node server that supports more features and works both directions (i.e., ISY could manipulate a Brilliant Dimmer without going through Alexa).

That would be a good interim solution, but I'd rather have a more direct (Brilliant<->ISY) connection between the two than one that uses an intermediary (Brilliant->Hue/HueEmulator->ISY + ISY->Alexa->Brilliant). The HueEmulator also can't support all features your devices might have because it has to make them all look like Hue devices.

You can have more than one device on your network that uses port 80. That's no problem. But, you can't share ports on any one device. So, if Polyglot's web UI is on port 80 of Polisy, nothing else on Polisy can use that port. The real solution here is to avoid the Hue Emulator and convince Brilliant to support ISY, either by adding ISY support to their Home Control system or by providing an API for Universal Devices to use. If you haven't already, please add your voice to this cause by going here and clicking on the Submit Request button found at the bottom of their website.

It's sloppy on Brilliant's part, but apparently Brilliant isn't the only "Hue-compatible" device with this issue. In any case, thanks so much for creating the HueEmulator node server. It is really quite useful. I'm hoping you are planning to port it to PG3 (and that PG3/Polisy allow it to use port 80, of course).

With the state of Insteon being what it is, RA3 months away, and a house full of dead or dying Insteon switches, I took a small plunge into Brilliant, purchasing a Home Control unit and a few of their Smart Dimmers. They truly are quality-looking devices with great build quality. I am concerned with how young and unproven the Brilliant company and their products are, and I am equally concerned by how reliant their system might be on the cloud (what happens to my devices if Brilliant closes shop?). That said, the Brilliant Home Control unit is a pretty sexy device and I figured if all I got out of this was an overpriced wall-mounted controller for my Sonos, I’d feel OK. Brilliant meets ISY Of course, one of my first tasks was to see if I could get the Brilliant devices talking to my ISY. As a test, I wanted to get a Brilliant Dimmer to control a light connected to an Insteon switch. Currently, Brilliant has no support for Insteon (why would they at this point) or ISY (understandably, since Brilliant is largely a “controller” just like ISY). Brilliant also has no public API for their system (yet). All that said, Brilliant supports a ton of protocols, including Hue. This made me think… Brilliant->Hue->Polyglot/Hue Emulator->ISY Simple, right? Well, as you can see from this thread and others like them, it's not. But, I am nothing if not stubborn -- er -- I mean persistent! The main issue here is that Brilliant requires a Hue hub/bridge to use port 80. And, as I discovered, it's not easy to make that happen. Yes, the Hue Emulator has the option to change its port, but port 80 is reserved on Polisy for Polyglot's web UI and (as of this writing) you cannot change this without breaking things. Additionally, you cannot use port 80 on most (all?) Linux distros unless you run as root, which Polyglot does not do by default. In any case, enough of the blah, blah, blah... Here’s a brief summary of the steps I took to get it to work: Install Raspberry Pi OS Lite (Legacy) onto an RPi. I used an RPi3 but it likely works on an RPi2 as well. Please note that you must use the Legacy version of the Raspberry Pi OS or Polyglot won't run. Install PG2 Follow these instructions to fix the “ee key too small” error. SSH into your RPi and enter these commands: sudo service polyglot-v2 stop sudo service mongodb stop cd /usr/lib/systemd/system nano polyglot-v2.service Replace the User=pi line in polyglot-2.service with this: Environment="HOME=/home/pi" Save the file (ctrl-O ) and exit (ctrl-X); then restart Polyglot with these commands: sudo systemctl daemon-reload sudo service mongodb start sudo service polyglot-v2 start Open Polyglot on your RPi (https://[ipaddress]:3000) and install the Hue Emulator node server, following all the instructions to set it up with an ISY device and/or scene exposed. Go to the node server’s Configuration page and change hue_port to 80. Restart the node server. Follow Brilliant’s instructions on adding Hue lights to their system If all goes well, the Hue Emulator devices will appear on your Brilliant Home Controller! Hopefully, I didn't leave out any key parts above, just all the head banging and blind alleys I went down along the way. ISY->Alexa Routine->Brilliant (going the other way) If an Alexa is part of your setup, having ISY control Brilliant devices is a bit easier. Because Brilliant can expose its devices and scenes to Alexa, you can use ISY-triggered Alexa Routines to control them. Just be aware that this is a cloud-based solution that requires a subscription to the ISY Portal (which you already have, right?). Temporary Solutions I truly hope my hacky way of getting these two systems to talk to each other is only temporary. Long haul, I hope Brilliant adds official support for ISY. Agree? Then please let your voice be heard by going here and clicking on the Submit Request button at the bottom of the screen. Cheers, -Randy

Last I checked, the most recent Raspberry Pi OS doesn't support mongodb so you are unable to install PG2 on it. Update: I just verified that if you avoid the latest RPi OS and install the Raspberry Pi OS Lite (Legacy) port of Debian Buster instead instead, PG2 installs just fine (though you might have to follow these "SSL error" instructions to get it to start properly: https://github.com/UniversalDevicesInc/polyglot-v2#ssl-error-ee-key-too-small).

Testing this out in the morning, everything is working great. Thanks for clueing me in on needing to uninstall/re-install each NS, @bpwwer. Interesting possible side effect of all this is that one might actually be able to support multiple ISYs with PG2. Just change the System->Polyglot Settings to the desired ISY prior to installing a NS. You simply couldn't share any one NS with more than one ISY.

OK, I think I got this. Some newly installed node servers appear to work with ISY/Polisy. Not all yet, but perhaps I have to be, um, more patient? It looks like the answer is to uninstall and then reinstall all the node servers after changing the System->Polyglot Settings. Does that sound right @bpwwer?

You have me at a bit of a loss as to what the solution is here. This statement in particular confuses me: "When Polyglot starts, it queries the ISY for what node servers have been configured there" I am happy to uninstall all the node servers and re-install them. But my understanding is that this would still all take place in Polyglot, not ISY. In other words, I don't appear to be able to install or "configure" node servers from ISY's admin console. I feel like I'm being obtuse and missing something obvious (apologies). It's been so long since I set up Polyglot that I honestly don't remember doing anything on the ISY side to "configure" node servers there. So, how do I set up my ISY/Polisy so Polyglot knows about the "node servers [that] have been configured there"? In other words, how would you get ISY/Polisy talking to Polyglot/Polisy after originally setting up Polyglot/Polisy to talk to an ISY994?

I decided to cutoff my old ISY994 from the PG2 Node Servers hosted by my Polisy and point them at the ISY 5.2 hosted on the same Polisy. To do this, I simply logged into PG2 on my Polisy, went to System->Polyglot Settings and changed the ISY Settings to point at my ISY/Polisy. That is, I changed the Address/Hostname to the IP address of my Polisy, changed the port to 8080, entered the device password and clicked Save and a happy green "Settings saved successfully. If you changed the Polyglot Web Port, please restart Polyglot." message appeared. However, when I reloaded the ISY/Polisy admin console, there were no Node Servers. And, frustratingly, they still all appear in my old ISY994's admin console?! I've restarted the Polisy a few times now (via soft reboots and a complete shutdown-powerdown-powerup), but that is not helping. What am I missing (it's probably something obvious)? How do I convince PG2 on Polisy to talk to ISY on the same Polisy?

Not sure if this is related to your issue, but AWS is largely down this morning, making Alexa a lot more stupid. https://www.businessinsider.com/amazon-servers-are-down-and-its-affecting-dozens-of-services-2021-12 https://status.aws.amazon.com/

Not sure if this is related to your issue, but AWS is largely down this morning, making Alexa a lot more stupid. https://www.businessinsider.com/amazon-servers-are-down-and-its-affecting-dozens-of-services-2021-12 https://status.aws.amazon.com/