Jump to content

auger66

Members
  • Posts

    286
  • Joined

  • Last visited

Everything posted by auger66

  1. Up and running with PG3x. The Hue node server was "disconnected." Tried several restarts. Ended up deleting and installing again. Had to add the "bridges" custom parameter. It works but doesn't survive any sort of restart. I have to do everything Hue related again. A reinstallation doesn't work. Only delete and install. Edit: Also, managed to delete Hue out of all my scenes. Makes sense, but I haven't had this happen before. Hue in programs just had to be clicked on, updated, and saved.
  2. Same PG3x problem on eisy. I've had this pretty much every time after an IoX update. Usually an eisy systems settings reboot gets it back. Not this time. Repowering didn't work, either.
  3. Yes, it did. The dashboard and store are still showing 1.0.7, btw. But it's clearly a new version since it works now. My exit-music-fade-to-off-pause-and-reset-volume program executes so rapidly on eisy compared to the ISY, it's really like hitting the pause button. I'll have to play with it. I've run into other eisy's-too-fast issues after switching over. Some steps in other old ISY programs I had to add repeats to make them more reliable. All Insteon fwiw. Thanks!
  4. I've been using the eISY for over a month now. This node server has never worked on eISY. I've tried every version of IoX and PG3x since late Dec. Multiple installs, restarts, etc. All Sonos S2, and a wired connection to the eISY and half of my Sonos devices. Dashboard shows connected with one ST-Sonos controller node. No device nodes. Today, I noticed 1.0.7 of ST-Sonos. Changelog says "update to work with eisy," along with a 50% price cut. Still doesn't work. Same as before, "connected" with one node. I attached my 1.0.7 debug log if anyone wants to take a peek. ST-Sonos_1-31-2023_64452-PM.zip
  5. Airports, too.
  6. My friend had a similar problem with vultures on the deck of his bluff-edge house. They went out of town frequently, and the vultures thought his deck was a great place to hang out. I suggested a motion-activated sprinkler. He left it connected to a hose and buried the stake into a five-gallon bucket full of rocks. It worked. They hated being sprayed with water. He was able to take it down in a month.
  7. Thank you, Jesus! Big Unifi network redo recently, and this was the only thing that wasn't working. Fooled around with it for a couple of hours before I came here. I was using the exact, same local IP address as before, but it didn't work until I added your bridge IP value. Thanks, again!
  8. eISY .20 I get this popup about every 30 seconds. This didn't happen repeatedly with previous versions. Also, my ST-Sonos shows connected with one node for the first time ever on eisy. It still doesn't work, though.
  9. Updated to 3.1.18 and reinstalled ST-Sonos node server on eisy. Still disconnected. Logs are the same as the OP.
  10. Or a bug detector for the more paranoid of us here. It's not paranoia if they really are after you. Just sayin' . . .
  11. Agreeing with UD tech support on this. You're basically describing a near Faraday cage location. While I agree a USB extension cable would be preferred, I think the difference from an antenna extension would be negligible.
  12. Did you try reboot on the admin console?
  13. same same. And "Current Status: Disconnected" on the ISY Dashboard page. It was disconnected on 3.1.16 also, but I never had any logs on 16.
  14. I had the same. It fixed itself eventually and didn't seem to make a difference.
  15. Good point and understood. My experience is a little different. I had one ISY-99 a long time ago, and until a few days ago, six ISY-994s running. I finally stopped concurrently running my personal 994 and switched it completely over to Polisy last week. Never had a failure. My eisy will be here soon. I've also never had a PLM failure. Lucky, I guess.
  16. Wouldn't you still have a single point of failure?
  17. Unfortunately, I have this happen every two weeks or so. A restart of the Sonos node server always gets it going again for me.
  18. I didn't get a shipping notification, but after checking "My Orders," I see I have one on the way for delivery on the 27th. Ummm, I'm a little scared . . .
  19. D'oh! That was easy. The setting must have changed when I got a new phone. Thanks!
  20. The state variables page used to show the current values of the variables. Now, the page doesn't populate the values until you open every one. I'm not sure when this started--a month or so ago, before the latest v1 update. Is this a bug or a feature? Seeing all the values when opening the state variable page was pretty handy to see what state everything was in. Thanks.
  21. I've been thinking about trying this migration, but everything is working perfectly so I'm hesitant. I can't find the pdf you're referring to here. I don't know if it's better to migrate now or wait for eisy, which I plan on getting as soon as it's available. I have a Polisy running PG3 and an ISY-994. Everything is working well. No z-wave. PG2 still shows up on my IoX launcher, but I don't use it now. I don't know how to delete it, or if I should. I see references to the Polisy migration tool from last year, but I can't find it. The wiki Polisy user guide subject "Migrating from 994 to Polisy" looks straightforward but don't know if it's up to date. I saw another thread attempting to consolidate the migration information, but it's old and don't know if it's best practices now. If someone could point me to the latest best practices for 994 to Polisy migration, that would be great. If it is recommended to wait for Eisy because I will have to migrate twice, I can do that, too. Thanks.
  22. Can't add much more to the title. Updated PG3 to 3.1.14 and WF node said disconnected and "not purchased" or something like that. Deleted the node to see what the store would say. Still prompting me to purchase again. ?
  23. auger66

    Matter

  24. Thanks for the replies. This for one of six Portal accounts for six ISYs on my Android phone. All are on different email address's. One person has one Portal account linked to one ISY on his iPhone. No sub accounts. He can see the devices, programs, etc. on his phone for the one ISY we're both looking at. After setting up the API key and everything on my phone, the notifications come to my phone but not his. I don't know how to add his device to the list. Do I need physical possession of his phone and set his phone up the same way as the video instructions?
  25. Welp, I fooled with this for an hour or so. I was looking for something to replace email-to-text notifications for more than one person for one ISY-994. I was thinking anyone with UD Mobile logged into the Portal account for this ISY could get notifications. The doesn't appear to be the case. The API looks like it is attached to the app and not the Portal or ISY. Is that correct? If so, this isn't going to work for me.
×
×
  • Create New...