Jump to content

Scott MS

Members
  • Posts

    24
  • Joined

  • Last visited

Scott MS's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. Just finished setting up Eisy and FLIRC and seeing some delays and some scenes turning on and then immediately turning off. I upgrade firmware on the FLIRC once installed.
  2. I see that Amazon Echo now supports Honeywell Total Connect Comfort. I will assume there might be a possibility to have the ISY control the Echo, which in turn can control Honeywell. Add me to the long list of people who would love ISY integration with Honeywell.
  3. I think I can answer my own question. You can buy a replacement power supply at universal devices. I just bought two. https://www.universal-devices.com/sales/ Also, it appears that if you use the dual-band PLM, like the 2413S I have, you need the external power supply for the ISY. Please correct me if I am wrong.
  4. The power supply I received with my ISY944i has failed. The ISY stopped working and I noticed that the network connectivity failed as well. LED was dim so I tried a different power supply I had (5v, 1A, appears to be a 3.5mm plug) and it started up instantly. Fixed. What are the power supply requirements? Can I use any 5V, 1A, 3.5mm jack power supply? I am also using an Insteon 2413S PowerLinc Modem (PLM). I saw on the Smarthome site that the PLM can power the ISY. MY ISY was purchased in 2012, so not sure if this applies to mine.
  5. Add me to the list of Honeywell Prestige 2.0 owners with a Redlink Gateway that would like some level of ISY control. Right now, these are on a separate system using the Total Control app. Pretty nice units and lots of customization through additional indoor temp sensors, etc. I have three units and the Prestige has alerted me when two of them have started failing based on performance.
  6. I am having an issue with the use of the Smartenit 5010T. When I save the programs, exit, and return to the Admin Console. It appears the "Watts" values are not saved. For instance, if I enter this in the program: Status 'PowerMeter / ZBPCM' > 1400 Watts then exit and open the Admin Console again. It will show: Status 'PowerMeter / ZBPCM' > Null It appears that the Admin Console is not saving the "Watts" values.
  7. Thanks for the enhancement. I just put together a series of 97 programs to set up target kWh usage per day (based on month), calculate hourly kWh usage from 12-7 p.m, provide alerts if the targets are exceeded, and provide a daily peak power usage report. All is working great using the 5010T and the status and watts. I am, however, having one issue. When I save the programs, exit, and return to the Admin Console. It appears the "Watts" values are not saved. For instance, if I enter this in the program: Status 'PowerMeter / ZBPCM' > 1400 Watts then exit and open the Admin Console again. It will show: Status 'PowerMeter / ZBPCM' > Null It appears that the Admin Console is not saving the "Watts" values.
  8. Any ideas when the additional functionality in REQID#55 will be available? If you could expand the range of power levels up to 20,000 watts in 500 increments for the Current State power, I could start using this device.
  9. Correct on the wait times between queries -- no rationale other than it is 3:00 a.m. and at that time I have absolutely nothing occuring in terms of Insteon traffic. I actually changed my programs slightly. I don't trigger any scenes based on the garage door open, although I do start a timer to provide an alert if the door is open longer than 20 minutes. This was randomly being triggered at 3:20 a.m. since the Query resulted in the door sometimes being "Off" using the NC sensors. I fixed the problem using two measures. First, I installed the NO garage magentic sensors so that garage is now "On" when open and then "Off" when closed. The nightly queries of my two IO Lincs should both return "Off" for the senor and the relay because they should never be open at 3:00 a.m. Thus, a delay in routing should have little impact, if I understand the issues correctly. The second measure I put in place was removing the separate IO Linc Query from the 3:00 a.m. program (that I documented above) and created a special query if the either door is open after 10 minutes. Basically, if the original query was incorrect, this second query at the 10:00 minute mark should update with the correct door status and end any programs that were running based on an invalid status. In order for the 20 minute alert to be sent, an "On" event should have been received initially and the an "On" query would also have been received at the 10 minute mark confirming the status. In the end, I really only want to make sure that nobody leaves the garage doors open by accident. And I like the fact that I can close them remotely, if necessary.
  10. I agree with Lee's comments above. I finally broke down and bought the NO garage magnetic contacts and have had fewer issues. As far as the 3 AM Query and the IO Lincs, I got tired to getting texts at 3:20 a.m telling me the garage was open for 20 minutes (Running 4.0.2, PLM v99, and IO Lincs v.41). It has happened to me about 5 times in the past year at 3:00 a.m. and mostly in the past 2-3 months. Hasn't seemed to happen since I changed the garage contacts to NO last weekend -- perhaps because both the sensor and relay is both Off with the NO contacts. I now also Query the IO Lincs a second time at the end of the program after a couple of Wait statements to isolate the traffic. If Time is 3:00:00AM Then Set Scene 'ISY' Query Wait 5 minutes Set 'Large Garage Status' Query Wait 5 minutes Set 'Small Garage Status' Query Else - No Actions -
  11. Fixed my typos above. Thanks again for your help with this.
  12. Thanks for the new firmware. I have a couple of questions. I see that I can now Reset Total Power in the programs, which is nice. Also, I see that if I check the status of the ZBPCM to see if the power is > 3000 watts, it is that evaluating the "Current State" power. Is there any way that that Accumluated power can be also added as an option to evaluate? Also, can we add in power levels up to 20,000 watts in 500 increments for the Current State power? Thanks again.
  13. Also, in my opinion, accumulated power is a more useful number. Using accumulated power avoids having to constantly query the ZBPCM to calculate power within the ISY. The ZBPCM is being updated every 30 seconds and the accumulated number can be queried and evaluated in longer increments by the ISY (like every 15 minutes).
  14. Thanks for fix. I did upgrade to 4.0.2 and I found the conditional status for the ZBPCM which goes up to 3,000 watts. Can I make a request? The ZBPCM is designed to measure whole home power and my meter runs anywhere between 900 watts and 16,000 watts depending on the time of the year. Is there any chance you can add additional values in the selection list up ot 20,000 watts? Or another option, is if you can add in the accumulated power, I can simply continue to reset the value every 5 minutes and accumulate the incremental values in a integer.
  15. Great news. I assume that the value will be queried in watts? For instance. 2.5 kW will be queried as 2500 as it is displayed from the console.
×
×
  • Create New...