Jump to content

greazer

Members
  • Posts

    70
  • Joined

  • Last visited

Recent Profile Visitors

1006 profile views

greazer's Achievements

New

New (2/6)

14

Reputation

  1. Thanks @Geddy I'll check out the videos too!
  2. Nevermind, found it!
  3. Awesome, thanks! Oh wait, while I have "you" here, can somebody provide me a pointer to where I can find instructions for installing Polisy on a raspberry pi? I'll look around myself. Maybe I've missed it somwhere.
  4. Oh, here's my understanding in a nutshell, of Polyglot and Polisy. The Polyglot cloud provides a way to run nodeservers with your ISY without needing to purchase Polisy hardware or Raspberry Pi. The Polisy hardware or a configured Raspberry Pi can be used *instead* of the Polyglot cloud. Current hardware and the cloud are using Polyglot 2.0 nodeservers. Polyglot 3.0 is in development and will require existing nodeservers to be modified to work. The polyglot cloud is not likely going to support 3.0 nodeservers, so it would be prudent to consider setting up local hardware in some reasonable timeframe. Do I have this right?
  5. Just up front, I am always amazed at how thorough and helpful the users are on this forum. I've never experienced one this good. Thank you soo much! Also, @geddy, thank you for the details. It really really helps. @jimbo, First good name (It's my first name too). Second, you have helped me in the other thread. For anybody who runs across this thread for ecobee problems, here's three really useful pieces of info. Restart on the polyglot cloud service means, Stop and Start of the node server. You certainly don't need a PIN anymore to setup ecobee. The biggest thing I hadn't been doing but needed to was to restart the ISY admin console after getting the ecobee nodes to appear in the console. To get the nodes to appear in the admin console you might need to copy the ecobee authorization link from the ecobee nodeserver log as I understand that sometimes the website fails to display the link.
  6. I've been using ISY now successfully for many years. And recently I was able to get a couple of node-servers up and running on it (DarkSky, Ecobee). However, I have a few questions: I'm confused as to what an extra Polisy device would be used for? I mean I was using two node servers and an ISY without one. I do have a raspberry pi that I could consider installing it on but for some reason I'm having a hell of a time trying to find instructions on how to do so. Maybe it's right in front of me, but I'm not seeing it. As I mentioned that I had both DarkSky and Ecobee successfully running once. BUT now neither are working for me. I was just trying to do some updates after setting them up about a year ago. For whatever reason I ended up uninstalling and tryin to reinstall both. I don't care about DarkSky but I do care about Ecobee. I'm never getting the PIN that it says I should be getting. I can post or look in another forum for that I suppose. Based on my problems above, I'm having trouble understanding just how to diagnose the problem and fix it. Would my life be simpler if I just got a Polisy (either new device, or raspberry pi?) Any answers to the above questions or pointers to existing docs on this would be greatly appreciated. In the meantime, I'll keep digging through.
  7. Really great info, MrBill! Yeah, this community is just one of the best I've experienced for anything. Yeah, I didn't think of having to re-add all my devices. That would be a pain. For now I just ordered a new serial PLM. Hopefully that at least buys me a couple more years.
  8. Good to know about the PLM! And thanks for the info about how you use HA. With regard to the PLM fail problem, one thought I had (but it's ugly), is to move away from the PLM and instead use HA integrated with a true Insteon Hub. I don't think the hub requires a PLM as it is one (I think). All the programming I've depended on in the ISY would have to move to HA though. That's the ugly part. But in theory is this a possible option? Hmmm... I suppose this is an inappropriate question for this forum, since it implies leaving ISY... The only solace is that I've really liked how well the ISY has worked for me over the years!
  9. One other thing though, MrBill, do you find yourself doing programming using HA exclusively now? Or are there situations where you still rely on programs in the ISY? I'm new to the HA world, but I'm thinking that it's likely going to support more devices than ISY will ever be able to support (even with the Polyglot stuff) and it can to integrate all of them. This question is totally off topic, I realize, but any pointers would be appreciated.
  10. Thanks for all the help here! After determining that I wasn't getting any events for ANY of my devices (including wired switches) I realized that this was more likely a problem on the PLM side. I found this article (INSTEON No Status Feedback From Devices - Universal Devices, Inc. Wiki (universal-devices.com) and followed the instructions. Lo and behold it found 0 links in the PLM. After restoring it all is working again. I'm not sure what happened, but perhaps it had to do with what MrBill indicated about "adjust scene" events accumulating. The fact that I had had a power outage happen while I was on vacation AND I adjusted the TLS settings for HA were just red herrings. I have updated to 5.3.3. So hopefully I won't see this again. Thanks again!
  11. Note that it's possible that this has been happening for a longer time than just recently and I didn't notice. I don't depend so much on programs for my motion sensors and typically my door sensors only matter when I'm not home and somebody opens a door that shouldn't. Therefore, it's entirely possible I just failed to notice until now. Here's the version of the firmware I'm using. Perhaps 5.3.1 is buggy in this regard?
  12. I'm at a loss. For some reason all of my sensors in the house are no longer showing status. It's simply blank. This screenshot was taken right after I manually pressed the Set button on one of my original Insteon MS's. No events, no status. The linked devices do turn on and off though so it's not a battery problem. I can even make my hidden door sensors beep from the admin console, so communication is possible. I'm getting the same problem for Door sensors and motion sensors I have in the house. What am I missing? Note that I just recently started playing around with Homeassistant and it's integration with the ISY. Could that be the source of the problem? I know I futzed with a TLS setting somewhere. Otherwise, Homeassistant successfully found my ISY and all the connected devices. I can control lights and such with it just fine.
  13. @larryllix, I am definitely changing the brightness of triggered lights based on the time of day using the technique I described above. That leaves a way to change the OFF time after a light is triggered on. I don't know how that can be done other than by changing the MSII to be ON Only, then creating a program that starts a timer when the MSII is triggered on and turns the light off after it times out. You could then use a variable time limit in the program itself based on time of day. If you did that, then you could set the applicable MSII's to timeout after 30 seconds since you want motion to be sensed as quickly as possible each time. This way, you can still take advantage of having scene-link performance to turn a light on. Lag is probably not much of an issue when turning a light off. I used to do something like this, but I really didn't like the fact that when setting up a new MS, I'd HAVE to remember to change the hardware options (particularly make it On Only as well as setting the timeout) AND make sure I have a program for it to ensure the lights are turned off. By making use of the defaults for MSII, there have been cases where I just made a scene to link the light and the MS and that's pretty much it.
  14. @tjkintz, I didn't think I was experiencing what you indicate with my MSII. I don't get an ON notification until after the MSII times out. I created a quick program to beep my office light switch when an ON is received (or just open the event viewer to see what events are occurring, I usually find beeping easier). It looks like this: The Office Desk MS is an MSII v.46 (not v.47, like my others) and sits pretty much right by my keyboard so it's constantly seeing me move as I type. The LED blinks as expected when I move, and the scene-linked lights stay on while I'm in here, but I do not hear a beep from my light switch. If I let the timeout expire and the MSII goes off, when I trip it back on I do hear a beep from my light switch. This is true regardless of whether I have On/Off or On Only set for the MSII. Here are the settings for my Office Desk MS II: Note: I actually get multiple beeps when the MSII senses movement. This can be verified in the event viewer. I don't know why this is. But in any event, I don't get continual beeps as I see the LED light up. Only after the timeout occurs.
  15. Your welcome, @larryllix! Lord knows I know you have helped me countless times in the past! What you describe is happening makes total sense now and I certainly agree with your new ISY Axiom. However, I do wonder why you would even need to have the ISY timer fallback to turn off a light that is hard-linked to a MS or MSII? As long as there's motion in the room, the light will stay on. When you leave, the MS or MSII times out, turns off and thus turns off the light. I suppose you might have a situation where a person can turn on the light in the room for some reason without ever triggering the MS. OR perhaps you have it hooked up to Alexa or have some other programmatic way to turn on the lights without requiring anybody to walk into that room. Is this why you have this fallback? For me, I don't have this situation occur much, but even if I did, it doesn't bother me as the appropriate MS is likely to be tripped eventually. On a related note though, I do have a program that runs when all MS's in the house turn off. That program waits for a 30 minutes before turning off all the lights in the house if no further motion is sensed anywhere. (Actually if the lack of activity is discovered during the day, I lengthen the timeout to 3 hours since during the day, 30 minutes could conceivably pass if somebody's sitting on the couch watching TV, not moving much. In that case, turning off all the lights in the house is undesirable. If you're not moving for 3 hours, then you must be asleep. ) This should usually ensure that any light that doesn't need to be on is turned off after 3 hours, no matter what.
×
×
  • Create New...