sorka

Spent all day setting it up including getting the legacy Isylink up and running (because I need CAI and the PG2's DSC plugin doesn't have the features I need that are in Isylink's node server). So then comes installing PG2 and I get errors like this: Reading package lists... E: Package 'mongodb-server' has no installation candidate E: Unable to locate package python2.7-dev E: Couldn't find any package by glob 'python2.7-dev' E: Couldn't find any package by regex 'python2.7-dev' E: Package 'python-pip' has no installation candidate E: Package 'mongodb-server' has no installation candidate And then I find a post in this forum that says you have to install the lagacy raspian lite which won't work with other stuff I've already installed. So what do I do? Just keep running PG2 on my old RPI3 and don't shut if off? Can I run it in a docker container on the the RPI5 even though PG2 itself dockerizes for each node server?

I got my replacement caps today from an ebay seller. Spent a few extra bucks for the curation of them rather than going straight to Digikey. Now I'm not so sure it was the right thing to day. Two of the caps have significantly bumped voltages which I thought was an issue for powerline signal reliability: C3 - 6.8 µF 250 v (replacement is 450 v).C11 - 100 µF 25 v (replacement is 50 v) Is this ok?

So it sounds like this is a "replace PLM" process rather than just a restore and would require placing all battery operated Insteon devices into programming mode to update the links since the board with the caps is also the board that has the Insteon address for the PLM?

Does anyone know if I can swap a board from my new 2.6 to my 2.5? Which board has the address of the PLM? The big one with the caps or the small one with the RJ45 jack? Hopefully the small one?

Ordered yesterday. Shipped today. Should be here by Tuesday.

Thanks. I ordered a new one. I also ordered multiple sets of caps for the 2.4-2.6 versions. I guess cap failure on their power supply redesign was a thing, just not a soon as the old design. I still have my previous failed PLM which appears to be a 2.4. The caps look to be through hole, so they should be pretty easy to replace. I won't even attempt surface mount.

I'd reply to one of the many existing threads about this but can't because they've all been archived...which is why there are so many threads. I believe 2.5 is the last version made by Smarthome before they went belly up. It's been since I got it but 3 times in 2 weeks tells me I'm in trouble. Has anyone had a 2.5 memory failure yet? Is there any point in rebuilding the power supply? I heard a rumor that new ones might be available again soon.

Did you actually read my post? Apparently whomever decided to nuke the other 7 leds didn't realize that the on/off switches can be be used as REMOTE dimmers.

Does the new on/off switchlinc work with the older switches? https://shop.insteon.com/products/on-off-switch The fact that this new one only has 2 leds for on/off worries me that it may not work correctly. All the old on/off switches still had the full led array for level since they can and are often used as remote dimmers for the switches actually carrying the loads.

Actually just one new issue also solved and it was the same night, not the "next" night. My thanks to @techman in this thread for solving the 1011 issue. The other one I solved myself. The Leviton plug I bought does not support reporting its status. I'm not willing to use the hail program work around. I have multiple additional brands coming in the next few days and will report in the other thread which ones do and don't report their status.

Given that this thread solved my issue in about an hour, I think it worked out for me just fine ?

Since this thread is now completely off topic, I've asked the mod to either retitle and move it or split it.

False. Had the the old thread been up still I simply would have ask "was this ever solved for anyone"? . If no answers, I would have started a new thread posted all the details as if it had never been asked. But that's NOT what would have happened. Every member in this forum who posted this issue has already had it solved and one of them would have replied.

You mean like what I did in the first post? How's that working out? Had they not been closed I wouldn't have done what you claimed closing the topics fixes.

This is an awful practice. It eliminates context and previous lessons learned. It also keeps those who have awareness of the issues being informed when something new related to it is posted since they are not following the new threads already. I totally agree that closing out threads that get off track is an occasional ok practice when it doesn't lock out awareness of valuable trouble shooting. By closing these threads, folks who've had their problem solved can't post in the existing threads so it looks like the problem was never solved...as in this case. I did post links to the previous threads, but I was already so irritated by them being closed and preventing awareness of this issue already being solved, that it basically turned into a rant from me. Also, I didn't upgrade to a weird version. I updated to the version every said I should 3 years ago and haven't gotten a prompt in the UI since to upgrade that version to something newer. Prior to 5.0.14, I'd occasionally get prompted to update the firmware which I would do. Did upgrading to 5.0.14 eliminate that because I was on some funky version?

It's not a signal strength or mesh size issue. Maybe if it was far enough that exceeding 4 hops on the way back might cause the issue. There are several technical reviews in the Amazon review section for this switch that mention that status reporting is not supported and the hail work around. I've already initiated the return and will not be buying any Leviton products until this is confirmed fixed for any future models.

I get where you're coming from. I did make an attempt to see if this issue had been resolved before making a single post. The two threads on it were closed resulting in: Those who'd previously posted about the issue not being able to report to the existing threads that a newer update fixed the problem. They would be unlikely to start a new thread just to report something had been fixed. Those who go searching for the problem previously reported can't post in the existing threads asking if the issue was ever resolved which would result in those who are already following the thread and had the issue fixed being able to reply as such if they hadn't already.

That was the first thing I tried.

Just installed a GE Enbrighten. Works ok. The only downside so far is it's slow to report its status. Takes about 2 seconds vs the Minoston which shows up instantly. Of course even with the speed of the Minoston, scenes would never be as slick as Insteon since those don't require a hub and all devices in the scene listen and react at the same time to the controller. With zwave scenes, the hub has to listen to the controller and then send out commands to the other devices listening.

Just the amazon reviews that claim the product page is wrong about 2-way status being supported.

Just like the folks in this thread: No status reported with this device: https://www.amazon.com/gp/product/B01NAO4B9Z/ If I query the status, that works fine but no status broadcast with local control. Running 5.3.4 firmware and UI. 500 series dongle running 6.81.0 Works fine with these: https://www.amazon.com/gp/product/B08LN2NPZ3 Assuming at this point that this is a Leviton bug?

Isn't 4.9 the current official release?

Updating to 5.3.4 has fixed the scene controller issue for Minoston plugs. The Decora switch is still not reporting it's status when changed locally. I'll check its documentation to see if there are any params that need to be set.

This is the dongle I have:

There is no led at all sticking out the back. It was purchased last in in February from Amazon: https://www.amazon.com/gp/product/B07GNS1B7V