MJsan

Updated packages to 5.5.6 and now I'm getting this fun error @bpwwerI looked at the network traffic and didn't see any traffic from outside going to the 24 MH modules - not a single one - when I sent commands. Taking a breath, resetting everything... and thanking myself for not selling all of the old Insteon plug-in modules that used to be in front of the MH lights ... I'm very close to putting those back in as they were reliable.

Looking at one specific device that isn't behaving ... MagicHome sees it, controls it, and it's showing cloud and local online... UD shows it blanked out... Same is true for about 10 other lights. I've tried querying ... rebooting EISY ... rebooting router ... and it's always the same. UD doesn't "see" the light, MH/FW app sees it and can control it perfectly. Router sees all of the lights as well. Google Home (through speakers and app on phone) controls perfectly.

I'm on a pretty beefy Ubiquity UniFi Dream Machine Pro router/firewall with 4 access points in a mesh config, so I don't think it's on the network side... plus the MagicHome and FLuxWiFi apps and GoogleHome work 100% of the time perfectly. I went out of town for work for a few days and OF COURSE the lights went wonky. About 1/3 of them worked, and my husband is NONE TOO HAPPY. I believe the exact words were "it all worked fine before, why did you have to mess it all up trying to make it better?" WAF/HAF not good here. I'm playing with it now. Activate scene from UD mobile ... 1/3 of the lights respond to that scene. Trying individual lights - got a few more to turn on. I have a few other lights not part of this scene - and they aren't behaving with the UD mobile app. MagicHome Pro and Flux WiFi apps (have both) work 100% perfectly. I'm at a complete loss here ... why does this NS only work sporadically (and completely unreliably) while the APPs work locally perfectly (iPhone, iPad, Mac) ?????? This is really frustrating because I don't know where to focus my efforts on - is this the Node Server? Is it the EISY? Things were working pretty well for a week or two, but "went to hell" after 5.5.4. Well, the fun just continues... I can't access UD from console - it's showing up but no option to login to console. https://eisy.local:8443/desc is blank, had to re-add manually keying in IP. But it works from the mobile app. ARGH. @Michel Kohanim is this just me struggling with this stuff? I'm getting increasingly frustrated... so much so that I'm debating on experimenting with HA to see if maybe that's a more stable platform? Ugh.

Ok, let's try this a different way I have 24 lights now (added a new one). This scenario only pertains to that new light ... a ceiling light that has both warm white/cool white (acts like a regular light) and also RGB. I'd like to have that light participate in a scene with 23 others and come on to a soft green color like the others do via a scene (accent lights ON). All of the others are pre-set to their last-on state and don't change. BUT I want this new light to come on full white when the command for "overhead light" is issued - or come on green when ACCENT ON scene is issued. I have to believe there is some way to accomplish this. I can set each light individually in the MH app, why can't I send both the ON command and light color/intensity settings in a scene command? Hopefully I'm explaining it - if it's wishful thinking on my part that I could do this, then that's a wish and I'd love to see if others are trying to do similar types of things. With the availability of addressable, color LED lights, being able to set scenes with colors would be AWESOME. I may end up having to talk to @larryllix some more about a bridge software... maybe even migrating to HA? Thanks, MJ

@larryllix thanks for that insight ... I can't get Fluxnet app on IOS, so am stuck with MagicHome. The device settings are in a separate menu and there's no way to set local network on .. it's either there or not. Now for the fun part... it changes throughout the day. The last few days, things work fine. What I'm seeing this moment is attached. Everything is showing up OK for cloud, but only a few items are "local" online. When I go to the MH app, everything shows up accurately and can be turned on / off just fine. When I try to do that from UD Mobile app, some (most) of the ones with local dimmed (offline) will work. The UD portal shows them connected=true. It's just weirdly flaky. The program to turn on all of these access lights runs nightly, and I have it set to repeat the "ON" command for the scene 5 times (30 seconds apart) just to be safe. Same for the OFF event later on. The last two nights, 100% of the lights behaved, 3 nights ago, 1 didn't come on (out of 23) and before than 2 didn't go off. It would be awesome if there could be some kind of handshaking / acknowledgement like Insteon does to ensure that when ON is sent, it's actually done. I'll keep an eye on it and hopefully we can find a way to make it stable? Cheers and THANK YOU ALL for your help!

Strange. Tonight the program timer ran at 530pm and every one turned on (and they all are showing locally online right now). I’ll keep an eye on it but it looks like they don’t stay locally online all the time - yet MH app can still address them. Is there some way to “wake up” to keep them online locally? I have several versions of the MH controller and a few of them are bulbs without separate controllers.

I see it but it’s not a setting - it just shows whether local network is online or offline. I get this message when I tap it. many of my lights change from showing local network online or offline. I’ve got a mesh WiFi with 4 access points and everyone shows great signal at the router, everyone is on the same network, and magichome app can 100% control all of the lights. I’m not getting why the MH poly isn’t able to control when the MH app can?

How do I enable that? It’s not apparent on the MagicHome setup? You’re right those 5 show local network offline, cloud online. thanks for helping!!!

After the latest update posted... I now have 5 "bad actors" out of 23. They are fully accessible and work with MagicHome app... but just will not play with the UD portal. I deleted everything on EISY- re-added MagicHome Node Server, and discovered nodes. Only 18 were showing up. I manually added the 5 that didn't show up, but they just won't work with UD Mobile or UD Portal. They are fine with Magichome app. Any ideas?

I can capture the bulb settings with this Node Server ... and change them... from the console and UDI app. I just can't figure out a way to do it via a scene. It might require scripting or doing it via programs...

I'm looking at our LED accent lights - right now there are about 21 lights and they are set up for holidays, some green, some red. They work perfectly, coming back on to the last color setting when they were turned off. At different holidays, we change these (orange/purple for Haloween, blue for other seasons, green normally). I have these colors set-up in the MagicHome app and it's relatively easy to change them. I'm wondering if there's a way through this Node Server and scenes to have "Christmas" or "Haloween" or "Blue" as a command that sets each light to the color I want? I'm looking at the list of devices and I can set RGB values, but I am stumped how to set each one up with different colors ... unless I add each one multiple times at different color settings? Thanks in advance for the help!

I'm afraid to say this for fear of jinxing things ... but we've now had 4 days of trouble-free operation!

@bpwweroh how true. @Michel Kohanimhas been in my system a few times working through some of them.

These are the continual errors that shows in the logs until Insteon controllers are turned on. 2023-01-01 15:07:16,465 Thread-1466 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:07:18,081 Thread-1471 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.157 socket connect failed * * * * * 2023-01-01 15:07:18,125 Thread-1466 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.35 socket connect failed * * * * * 2023-01-01 15:07:46,503 Thread-1482 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:07:48,109 Thread-1482 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.13 socket connect failed * * * * * 2023-01-01 15:08:16,617 Thread-1508 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:08:16,617 Thread-1513 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:08:18,226 Thread-1508 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.35 socket connect failed * * * * * 2023-01-01 15:09:16,689 Thread-1550 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:09:16,689 Thread-1555 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:09:18,340 Thread-1555 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.157 socket connect failed * * * * * 2023-01-01 15:09:18,340 Thread-1550 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.35 socket connect failed * * * * * 2023-01-01 15:09:46,703 Thread-1566 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:09:48,306 Thread-1566 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.13 socket connect failed * * * * * 2023-01-01 15:10:16,732 Thread-1597 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:10:16,732 Thread-1592 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:10:18,334 Thread-1592 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.35 socket connect failed * * * * * 2023-01-01 15:10:18,334 Thread-1597 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.157 socket connect failed * * * * * 2023-01-01 15:10:46,677 Thread-1608 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:10:48,336 Thread-1608 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.13 socket connect failed * * * * * 2023-01-01 15:11:16,714 Thread-1639 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:11:16,773 Thread-1634 udi_interface INFO rgbled:start: Attempting connection on port 6668 2023-01-01 15:11:18,331 Thread-1639 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.157 socket connect failed * * * * * 2023-01-01 15:11:18,375 Thread-1634 udi_interface ERROR rgbled:start: bulb: IP:192.168.7.35 socket connect failed * * * * *

Greetings! I finished migrating ISY994 to EISY (with a lot of help from Michel, we found some weirdness, he was able to fix things) and then went on to the next step - migrate MH lights off of insteon controllers and control directly with EISY and this Node Server. I had 21 various LED bulbs and strips all behind Insteon controllers... ISY would turn them on/off, and if I ever needed to adjust colors, I'd do it with the MagicHome app. I've now eliminated the insteon controllers and plugged the MH lights in directly for almost all of them (I have to have 3 remain insteon controlled for another month - too difficult to get to the controllers to remove them). I see in the logs that those three generate errors (since insteon is off, makes sense). I'm wondering if those errors popping up every few minutes are causing other issues? I've had to reinstall the MH Node Server several times - it will just stop working, sometimes show "disconnected" in the PG3 dashboard. I've tried restarting EISY no change, but reinstalling seems to do the trick. Right now I have a hybrid system with 23 MH nodes and 35 (ish) insteon controllers, keypadlincs, and remotelincs. When it's working, it's pretty cool - a keypadlinc or remotelinc button turns on a scene that has both MH and insteon controlled lights ... that was the goal When it's not working, the insteon stuff remain working but I have to go to the MagicHome app to control those lights so getting some grief from the other person in the house who just wants things to work (common problem many of us have, I think!). @bpwwer is there anything I should be doing - capturing logs, ?? It seems like the system is a little "flaky" requiring a lot of manual tending to to keep it going- hopefully this is just early adopter bugs.

After some major work by @Michel Kohanim my system is 100% functional - PLM and Insteon side as well as MagicHome node servers on the PG3 side. Everything y'all have said about how awesome UD support is ... absolutely true.

I completely agree- I tested a few devices as a "new install" and it was flawless (ish). When I migrated my 50+ insteon ISY backup I completely hosed it. @Michel Kohanimworked late into the night on my system and ironed out whatever bugs / kinks and I'm now thrilled to have my existing scenes now control a mix of Insteon and MagicHome lights. This is the holy grail for me - I am now able to really integrate with other home automation devices beyond the insteon world!!!

Yup... cannot launch PG3. Just sits at Login tried clearing cache, Safari, Chrome, and Edge.

Previously - was working. Right now I've got no PG3 running so no log to view. Waiting on Michel for next step.

@Michel Kohanimprobably too busy fixing things to write on here -- there was a bug that blew up certs after a restore, been online with him most of the afternoon. We went from 5.5.0 to 5.5.1 to 5.5.2 since noon I completely understand what folks have said about how great the support is !!!

Before I got my PLM serial cable and restored, I had to play with Magic home ... 23 nodes and it worked!!!!!! I actually purchased it. I did have to go through a few reinstalls to get it to actually be online vs. disconnected, but I can attest to it worked at one point. Sent the developer mad props and praise for it too! I'm working on a slew of other issues with Michel right now - after restoring my ISY994 backup I completely hosed the system - I'm one of the reasons for 5.5.0 now being 5.5.2 (and I suspect that number will tick up a few more times as we all do our install and some of the other bugs come up). My goal is to migrate 23 lights from Insteon to MagicHome but have it act like one system - app, voice, keypadlincs driving lights on/off regardless of what they are plugged into. Will see how well I can make it all work

Howdy! This thread is a little old, but it's new to me just now installing an EISY to replace my ISY994. Bob @bpwwer I really want to thank you for this little gem of a node. I have over 25 LED accent lights all over the house (ambient), each one behind an Insteon controller. The new set-up will eliminate all of those (aging, some over 12 years old) Insteon on/off modules and give me single-app control of both on/off and color. WOO HOO. I had to move off of Insteon as the modules have started reaching EOL. Luckily I haven't had any break apart or melt as some have... but I am losing about 1 every other month lately, and my supply of extras was exhausted (and given Insteon's lack of supply and survival not totally guaranteed, it was the kick I needed to move to a more open multivendor HA platform. I had to install your Node Server a few times to get it to move from "disconnected" to "connected" (and had to restart PG3) but once it worked, it was amazingly fast. So, THANK YOU. My journey continues ... but this was the most important first step!

Thanks for responding Michel- I did get a reply this AM and will drop the duplicate EISY off at the post office tomorrow first thing. Don't know what's going on with email - I am on Google Workspace and here's every communication since October (searched all folders, including junk)... it might be on your end? I will definitely use support tickets in the future since that is a little more trackable. Much appreciate all the hard work you & the team have made on this. I've already excited a few friends about what EISY should accomplish for my home system, will start the migration this weekend

Fair enough … I’ve only had to deal with customer support a few times and it’s 50% so far. Still a believer and looking forward to a successful ISY migration to EISY.

Shawn- what I'm bitching about (publicly) is that I've emailed them several times since December 12 regarding the cable - not one single response. So today I get not one but two EISYs delivered, so yay? I've ordered the customizable pinout DB9 + USB adapter from Amazon which I'll get Wednesday. Probably before I hear back from UD about (a) the cable I originally asked about and (b) what to do with the extra EISY. So... UD definitely has some process issues to work on - timely customer contact replies and accurate shipping. -mj