xlurkr

@larryllix: I saw you mention this in another thread. In what place and at what time are you referring to this login? As I said above, I plugged in my Polisy, the Launcher found it, and I clicked on its entry and attempted to launch the AC. Without any login request appearing, it told me that I needed to upgrade to 6.0. As I wrote, the first time I clicked no, and it terminated. The second time I clicked yes, and it threw up a dialog warning not to interrupt it. I dismissed it and my Polisy beeped a few times. Since then, I can't get Launcher to find it, which I assume is because the isy service isn't starting. Where can I log in with my email address? -Tom

btw, I should document for future posterity that your modified command for getting a new (different) dhcp lease did work for me, but since I was connected via ssh on a Polisy and not keyboard/monitor on an Eisy, as MIchel's instructions assume, I lost the connection, had to get my router to tell me the new address, establish a new connection to be able to restart udx again, only to still find that the isy service didn't start. Kinda illustrating my point about how we Polisy owners are a bit of an afterthought. -Tom

No offense, but I think I'm going to wait for a response to my ticket at this point. I promise I'll come back and post whatever I learn from UDI about what the problem was and how they fixed it. Looking at my old posts, and some of yours and larryllix's I get the sense that they have a tendency to leave out a step or two in their automated upgrade procedures for Policys. Understandable, if all they have and use these days are Eisys. -Tom

I just tried it again. The "pkg install" command doesn't have any error messages and installed one package - the rest were already there. It's the udx restart that has the error messages - something about needing to use the -H flag when running pip via sudo, and a pkg named "serial" not found. isy service still not running. According to Michel's recovery instructions, it must start for the Launcher to find my Polisy, and let me launch the AC, and finish the upgrade by clicking on upgrade packages? -Tom

Posts crossed. Yes, I did all those steps, and thanks for explaining the re0 thing. I'm assuming that just clears up IP addressing problems, but my Polisy has maintained the same address the whole time, and I have always been able to reach it via ssh. Many messages scroll by when doing the pkg install and udx restart, and some of them look like error messages. -Tom

I have a ticket in, and it wouldn't surprise me if UDI intervention will be required. The system is responsive via ssh, it's still on FreeBSD 14.1, I don't think there's any upgrading going on, and for some reason their documented recovery steps don't get the isy service to start, or the Launcher to let me launch the AC. So for the moment, it's a fully functional FreeBSD computer and a fully useless Insteon and home automation controller. But I have faith. At least it's more than a brick! -Tom

Nothing is happening, and since I can't launch the AC, I don't know how it would tell me to reboot. -Tom

I doubt this has anything to do with the "small image size" issue. I really don't understand why I was asked to upgrade to 6.0 when I connected via the launcher. I haven't read anything about that anywhere. And why doesn't it do that with my main Polisy? The release notes suggest that the upgrade requires manually clicking "upgrade packages" in the AC. -Tom

p.s. I followed all the recovery steps in the release announcement, but I can't get the isy service to start. It also says the interface re0 does not exist. -Tom

I just tried to upgrade my backup Polisy to 6.0. I pulled it from storage and connected it, and the Launcher found it, but it said that I needed to upgrade to isy 6.0. This is even though my main Polisy is still there, and still on 5.9.1. Weird. I said "no", and it exited. Connected again from Launcher. This time I said "yes", and it presented me with some kind of "don't interrupt" dialog, then exited, and the Polisy beeped a few times. Since then, the Launcher is unable to find it, though it still finds the main Polisy and launches the AC on it just fine. I don't know what to do next. I can't launch the AC to start the upgrade on the backup Polisy. When I ssh into it, it says it's still on FreeBSD 14.1, and the isy service isn't running. So I guess that's why the Launcher can't find it, but how do I upgrade if I can't launch the AC? -Tom

Yes, after migrating, mine went from ZW to ZY. -Tom

@plumcrazy426 Maybe the "migrate to ZMatter" thing was a matter of timing, and not whether you had a previous dongle? Or if it was internal vs. external (mine is internal)? I don't know. Anyway, if you have that "migrate" menu option you could always try it. -Tom

I should have checked my old posts before replying. Apparently, I excluded the lock, migrated, and readded it. Maybe that was a mistake? Anyway, everything is working. I also seem to recall that I was worried about security levels (S2 vs. S5) because their weren't as many choices when I originally added the lock. Maybe my mental note was about posting about the node I ended up with and asking other Schlage owners if theirs looks the same. -Tom Sorry, S0 vs. S1 vs. S2 security. Or none. Clearly I'm no expert. -Tom

I did click migrate - sorry that I forgot what it was called. And it did have some side effects. Afterwards, the nodes for my Schlage lock changed. There are fewer of them, and they have different displays and controls on their pages than the prior ones. The ones I needed were there, though, so I didn't look into it any further. I also made a mental note to remove and readd the lock someday, but I have not done so. -Tom

Any chance you had another dongle (like Zooz) before ZMatter? That was the case for me, and at the time "upgrading" was not automatic, and the backup was not included in the support for the other dongle. I fixed it by choosing "upgrade to ZMatter" or something like that in one of the menus. Then "backup" and other options started showing up for me. -Tom

Make sure you read up on this. There are two ways to get support for Insteon in HA. The first is with direct support of a PLM. You probably don't want to go that route. Device and link management is not very good or easy, apparently. The better approach uses a ...wait for it... ISY device. If you're really dead set against giving UDI any money - and for the record, I agree 100% with @sjenkins that there's no better place to spend it - you should consider keeping your Polisy (that's what I have), managing and linking your devices (at a minimum) with it, and adding automations, interactions with other devices, and UI with HA. Even then, it might make sense to have some automations on the ISY, due to speed and failure mode considerations. -Tom

All: Thanks for the helpful replies. I could have mentioned a few things earlier. I don't have an existing doorbell or wiring for one. But the "Dakota hub" is the Dakota Alert. Its job is to turn signals from Dakota sensors into Insteon triggers. I have several sensors, including a battery powered button on the front door. So I'm fully covered as to having a doorbell button that a visitor can push to trigger any Insteon activity I can think of. At the moment it just triggers an Insteon siren. It's plenty loud, but equally annoying. I have already experimented with having the Dakota button set a state variable and having that variable act as a motion sensor to trigger an Alexa voice announcement. That's less annoying, but has the typical unpredictable cloud delay, and I haven't found a way to have it always make the announcement at high volume, regardless of the current volume setting of each Echo. And there's the 30 second debounce which ain't great. The doorbell chime either has to be really loud (though not annoying), or visual rather than audible. That's because my wife spends hours every day with Airpods in her ears on a videoconference. And the phone she's on is a work phone that she (and her employer) refuse to let me set up with any kind of home automation, including alerts. So far @Geddy's suggestion of colored Hue bulbs will probably work best. I have some, and they are never required for any important activity in the house. Mine are a novelty, not part of the critical lighting, and this is a good use for them. I'll post an update if the Hue solution proves to be inadequate. But I still think it would be very useful to have the ability to record the state of all (or selected) nodes in IoX and restore that state - mindful of security and safety issues, of course. -Tom

@GTenchThanks for the first-person account. I think I'll get another speakerhub based on your experience. The Yolink stuff works great, and the plugin has worked well for me too, @Panda88 ! -Tom

@GeddyThanks for the link. I remembered reading a post about someone with multiple hubs, but my search turned up nothing. Unless I'm misreading the post you linked to, it doesn't say anything about how multiple hubs are handled in the plugin. I'd want to be able to send a TTS command to 2 or 3 of them with the same message at the same time. Not clear if I'd be able to do that. This is related to my doorbell thread in the IoX Support board. -Tom

@Guy LavoieThanks for reminding me not to track the state during the flashing! I'm sure I would not have thought of that myself. @GeddyThe doorbell button is extremely old school - it's a Dakota Alert button that is linked to a Dakota Alert hub. I bought all kinds of oddball Insteon stuff at one point, and I usually try to solve any new problem I encounter with things I already own. It's 100% local and 0%"big brother", too, which I like. -Tom

I might be able to continuously track the state of a small # of lights, each in its own variable, so I can restore them after flashing them, but again, given the many ways the level can be changed, I'm not sure it won't get out of sync. This weekend I might experiment with a single light. I'm hoping there's an easier way that I just don't know about. -Tom

BTW, the alarm panels of the past (HAI and ELK) used to give you the option to flash lights when the alarm triggered. IIRC, they would restore the lights to the previous state when the alarm was cleared. I want the same thing, only not all the lights - just one per room - and to restore it based on time, not on any action. -Tom This had crossed my mind, but I don't know how to do it, or if it's possible. -Tom

Generally speaking, no. I have a mix of lights - mostly Insteon and Lutron, and they go to their "on level" when they are sent a command to turn on. But they all can be controlled through other means, such as scenes and verbal commands, and less frequently through manual dimming, that might have them at some level other than the "on level" or 100% when the doorbell button is pressed. -Tom

I'd like to create a silent doorbell. My wife hates the sound of the Insteon chime, and TTS via Alexa and Yolink's speakerhub have too many limitations. What would work great, if it's possible, would be to flash at least one light in each room. That's easy enough to do through programs, but ideally every light would return to its previous state after flashing - and that state could be anything, because we set the levels of lights throughout the day through a combination of manual switching, scene controllers, and Alexa commands (for scenes and individual lights). I can't think of an easy way to do this. Can you? And in general, this is just one use case where one might want to capture the state of every light (and maybe some other devices, too) as a global state representing a moment in time and restore that state after making arbitrary, temporary changes. Is there any way to do that? Is this something a plugin could be written to do? -Tom