Jump to content

lilyoyo1

Members
  • Posts

    7177
  • Joined

  • Last visited

Everything posted by lilyoyo1

  1. https://forum.universal-devices.com/topic/19565-isy-and-phillips-hue-integration-step-by-step-for-dummieslike-me/
  2. To run the hue nodeserver, I'd recommend running polisy since using an Rpi is not supported with V3 of polyglot. However, it's easy to use network resources with hue with your current Isy. Unless you plan on using the hue app, network resources is the way to go. I've been using hue since the first Gen (subsequently upgraded bulbs and bridge) and not once have I had one drop off the network or a signal not go through to a bulb. It's easy to use, well supported by a high number of platforms and simply works. First generation hue did have problems with rendering certain colors 10 years ago but that's not the case with newer bulbs. I guess some people don't realize that things do change over the years. That longevity also speaks volumes about what you get with hue devices which may not apply to some fly by night company using magic homes API. I have had 3 strips go bad over the years between my house and customer homes. A couple of emails with the required information and a new product was at my door within days. This is the type of experience I expect and appreciate which is also why I continue to use and recommend the hue brand. My warranty experience with lifx was completely opposite. I purchased 3 strips for testing. Within 2 months 1 went out. After waiting almost 8 months for a new replacement, I was finally able to get a refund on the bad unit. The other 2 has continued to work great. 1 will drop off from my network from time to time but outside of that I've been pleased. Great colors and different effects are wonderful. Besides my warranty situation (I'm assuming that's not their norm) the only downside of the to me is ease of use. While not hard to set up, hue is definitely much easier to use and manage. Especially with network resources. With lifx, should a customer want to change their colors, that requires a service call from me. With hue, they can simply update their scene themselves. This goes for my wife in our own home. If she wants her colors to be different, she just updates the app. I don't have to log into the Isy and change anything. As my experience with lifx shows, wifi bulbs are not perfect (no protocol is). Depending on how many bulbs you need, it can pose a problem for your network. A few devices probably won't have an issue. A large number potentially can... Especially after a power outage. Besides that, depending on your network, do you really need to upgrade your router or potentially use multiple routers just to manage things? I'm not a fan of magic home bulbs at all. While they may have improved since I last toyed with it (a year ago for my grand nephew's underbed lights), the experience left a bad taste in my mouth. The app was clunky in trying to get the light strip connected and working. Even when using, it would drop off more than I'd like. I got tired of of my niece calling me that i eventually pulled it out and out hue in with no issues since. Granted it could be her network (she used the at&t router) but it still goes back to what I said about needing to buy a new router just for some lights. Cost: Hue and lifx cost more but you get what you pay for. There is a consistency that you get across their product lines that you don't get with cheaper bulbs/strips. I know quality matters to me but for some, they are ok with just good enough. This reminds me of a client that chose not to use me for some strip lighting. He did it himself with some home Depot strips. He called me when he didn't like how things turned out. The strip specific reason was that the light was not consistent. Some whites were slightly off whether it was due to temperature or brightness (with the same settings). You don't have that issue with more expensive lights. You can easily find hue on sale at Amazon, especially around the holidays. If you don't need color in a location, cost drops significantly since the tunable white is about 30-40% cheaper than the color options. IMHO, I'd rather save and buy hue over time vs using cheap wanna be knockoffs that use the magic home app.
  3. That depends on budget, use, and needs. I use hue bulbs and network resources. There's also a node server for hue which may be easier and also gives 2 way control. You can also use other zwave bulbs, magic home compatible bulbs and lifx.
  4. No there is not. But if you want the bathroom light on based on that scene, why not add it to thse scenes and have it part of that?
  5. No. Upgrading will not help. You need repeaters
  6. For starters you can clear your Java cache and use the launcher from the 4.9 firmware update page so that your firmware and UI matches. Once that is done, try to reposition your isy so that it's upright. Depending on your network, most likely you need more devices to strengthen your mesh network
  7. Can't see your p program. However, if you're using insteon and the sensor is linked directly to your switch, then it will do what you are experiencing
  8. Bali isn't a bad choice. I enjoyed mine when I had them. Lutron is much smoother and quieter than Bali (or anyone else for that matter). You do pay for that however. With that said, depending on desires, it's worth looking at. Depending on need, you could always hold off to save for them depending on cost difference for your windows.
  9. Bali auto view is zwave and works with the Isy. I had them in my old home and they worked well. If pricing isn't a concern, I'd go with litron shades as they are much quieter and there's a nodersrrver for them which allows you to integrate them with the isy. I can't speak on the other company you mentioned as I've never used them. Them charging 150 for a 30 dollar controller doesn't surprise me. There's always a markup in business.
  10. It's showing in my app store. It's probably not showing since it's called UD Mobile not UDI mobile. https://play.google.com/store/apps/details?id=com.universaldevices.udmobile
  11. OTW= over the wire
  12. If you purchased it new last year on Amazon then you have the 500 board and can upgrade to 5.3.4. The missing light confirms it's 500 series
  13. The ISY can still be a secondary controller. You just have to know what you're doing to make it happen.
  14. I assume you meant zwave encourages the use of multiple devices not hubs as its the devices that builds out the network not the hubs. Multiple hubs can be used in a single install by adding other hubs as secondary devices. Thats not something an entry level person should attempt however unless they are willing to settle for a huge learning curve.
  15. Spoke to soon. While I'm able to get in now, i do not have the portal. Manage modules shows all up to date but does not show the portal in help>about. No portal tab either under the Configjuration tab. Added polisy to my portal account. Shows as my preferred Isy but is currently offline
  16. That did it. Thank you for your help. As always, you're the best
  17. I had already tried the factory reset but when I went into polyglot every still showed. I deleted everything but wanted to make sure polisy was cleared too. Thank you Cloud works as far as pulling the admin console up. The default password worked.
  18. @Michel Kohanim I am unable to log into one of my polisy's. It shows up in the launcher but nothing happens when I click on it. SSH'd into it and ran the different updates which there are none. Stopped and started UDX and ISY and its still a no go. Also is it possible to sart all over with a clean slate as if this polisy had never been used? It was once connected to my isy but I dont want to port the system over (I want to do a fresh install). uname -a=13.0 release P6 Free BSD 13.0 release p6 #16 pkg info udx= 2.5.3_36 pkg info isy=5.3.0_26
  19. Im reading into what the op was referring to from the original post which deals with what parameters are. If your referring to something different then we are talking about 2 different things. Any database not designed to take into account future devices and changes is one set up to cause issues. As someone who's ran f500 company systems, I would think you would know this. I dont have any ideas on how to do this database as I think its unnecessary and there are much simpler ways to accomplish most of what was spoken on. Obviously if others feel different, thats their feelings and I have no issues with them or anyone pursuing what they feel will make the ISY a better system. You say that you have the knowledge, experience, and desire so feel free to pursue it instead of simply talking about it. Thats the part that I speak about. People constantly saying what someone else should be doing without taking any amount of time to see what it takes to accomplish any given task.
  20. Whoever you were implying should have a database is irrelevant. I did assume you meant UDI since you did not volunteer in your initial response and you said UDI should harness the community. If you werent referring to them you could have easily stated it was something you were looking to work with UDI on or take on for yourself. With that said it doesnt matter who maintains a database, its still an extremely daunting task that requires a tremendous amount of manpower (man hours) to setup and maintain. The only thing worse than no database is a poorly maintained database with incorrect/out of date information. Take a moment to peruse the fibaro's manuals for their motion sensor alone (1st and 2nd gen). Then extrapolate that across thousands of different devices and firmwares (different firmwares support different things). So yes, while the community can add information to it, who will ensure it is the correct and up to date information (without losing or confusing with older devices). Lets say a database of every zwave device made is maintained and keep up to date with zero errors. How does that make it easier to find things than a person simply downloading the owners manual from the manufacturers website to their computer? In regards to my non techie comment, read for context. It was a statement made towards another one implying that most of the general public wouldnt want to invest in the time needed to learn and setup an ISY/Polisy. The fact is, most people who use the ISY/Polisy will have some technical ability. Most of the non technical general public will automatically gravitate to easier systems such as smartthings, google, amazon, etc. Nothing about this post has anything to do with teaching someone professional methods. Since you decided to mention that, we could talk about some of the things professionals do to make their installs much better. One of the main things professionals will do that most do not is take the time to learn about their craft and the devices they plan to install. One of the simplest methods to do this is to read the manuals (which if this post is any indicator doesnt happen). Many people will create overly complex solutions to the most basic of problems and for what?! Another is they focus on installing a limited number of devices. This allows them to focus on a few select devices and know them in depth. Trying to install a multitude of like devices is counter to that as the likelihood of being highly knowledgeable about the product goes down the more they use. Next, they just dont use the product. They'll test it. Learn its strengths and weaknesses so that they use it in the best manner possible for success vs. trying to fit a round object into a square hole. This includes but not limited to taking the time to learn all that you can about the chosen technology. If people took the time to do so, they would understand,the difference in how zwave handles different device properties via different mechanisms. If people do so, some debates such as this would be moot as they would understand the ROI on trying to build and maintain a database along with the additional coding needing to try to find the matching parameters.
  21. Only you can answer why one works better than the other for you. Then again, depending on nodeserver, you may only have the option for cloud based or local based only. Most on here prefer local access to their devices (me included) so they would shun cloud based nodeservers since those require internet access. Even if you have perfect internet, who's to say someone else wouldn't have problems with their server? There are plenty of recent threads talking about the differences between pg2 and pg3 so I'm not going to rehash easily found information. Basically, pg2 is old and pg3 is new/up-coming. Most development is being done on PG3 so there's really no point in worrying about pg2
  22. You didn't answer the rest of the questions
  23. If you do not use zwave then you must update to 5.3.4
  24. Firmware, UI, distance from isy, and process used to enroll?
×
×
  • Create New...