Jump to content

EISY - MH is a little flaky, day 4


MJsan

Recommended Posts

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.

 

Edited by MJsan
Link to comment

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 * * * * *
Link to comment

I have the same issues with Govee LED lights using the Govee node server. The lights will not stay connected. They will disconnect and then re-connect at some point. The lights seem to not have the problem of staying connected to Alexa.

My node servers are in my Polisy. I haven't migrated them to my eisy yet.

Edited by dbuss
Link to comment

I'm surprised that you have it working given the number of bugs in PG3x. 

Looks like it's trying to contact those devices every 30 seconds or so. While it fills up the log with a bunch of useless messages, it shouldn't be impacting anything else.  (it may slow down the node server response if it's waiting for one of those devices to timeout before it can respond/send a command to another device.

  • Thanks 1
Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...