Jump to content

skydvrz

Members
  • Posts

    24
  • Joined

  • Last visited

About skydvrz

  • Birthday 11/10/1954

Profile Information

  • Location
    Kissimmee, FL
  • Occupation
    Senior Software Design Engineer

Recent Profile Visitors

420 profile views

skydvrz's Achievements

New

New (2/6)

6

Reputation

  1. This problem may be fixed - I tried every trick in the book and have not seen the "Upgrade to Standard" warning message in a few days. Is there any way to tell which Notification plugin version is active in my EISY or UD Mobile?
  2. Did you install the paid version? I thought so. I originally installed the freebie version and then a day later decided to pay for the added features. Do I need to uninstall first? The paid-up version shows in my Paid plugin list on Polyglot. Each subsection shows "Installed".
  3. There is no HTML in my message bodies; I don't think EISY adds any to the text. The reason for failure was pretty clear - the ISP doesn't like text body lines terminated using Unix/Linux style (or maybe Mac) style line endings.
  4. The fix for this is probably a couple lines of code in the EISY firmware. I'd prefer a fix that does not rely on plugins that may not be compatible with future EISY updates... But I will keep your idea in mind if no EISY patch is forthcoming. I need my SMS-via-SMTP notifications! The EISY SMTP code is a lot better than the old ISY code - at least EISY can navigate modern SMTP security where the ISY died of that years ago.
  5. Does anyone else have problems sending notification messages via certain certain ISPs? I get the following error from tmomail.net (my smartphone provider) when I send a text message via SMTP to my phone: Your message to xxxxxxxxxx@tmomail.net couldn't be delivered. Your message contains invalid characters (bare line feed characters) which the email servers at tmomail.net don't support. kgmccoy Office 365 xxxxxxxxxx Action Required Recipient Bare line feeds unsupported I tried adding additional blank lines to the bottom of each notification message, but that did not help. Maybe EISY is sending LF instead of CRLF for blank lines? Maybe EISY needs to send CRLF instead of LF for every line-end?
  6. Thanks for the offer! I am just going to kill the garden program, since it depended on a weather node server that never worked correctly. I was trying to factor in Evapotranspiration (ETo) to determine how much water to apply and it stopped working when the node changed their API. I need a different node server that provides daily ETo numbers and a rewrite of my program. It ping pongs between ankle deep rain water and 120F dry weather around here, so ETo numbers would be nice
  7. I saw that Program ID 0008 according to the error log seemed to be the problem - low and behold the status of my ID 0008 "Water requirements Midnight" program (adjusts the runtime of my veggie-garden drip system) says "Out of Memory". I will take a closer look at that one or just disable/delete it. I am guessing it went recursive somehow and blows up the stack or heap. So - A big thanks to everyone that chipped in with suggestions - Especially MrBill! P.S. UD could make the error logs a bit more verbose/easier to read in the EISY if they haven't done so already.
  8. I followed MrBill's advice and that seems to have fixed the reboot problem. Woo hoo! Can I simply disable each program individually and then slowly add them back in to find the culprit? I have close to 50 programs running so it is going to be like searching for a needle in a haystack. Here is an excerpt from my log covering some of the reboots: Thu 2022/12/29 15:05:41 System -5 Start Thu 2022/12/29 15:05:47 System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2022/12/29 15:05:49 System -7145 ID 0008 :err=0, tag='/var', num=115, nest=4, of Thu 2022/12/29 15:05:51 System -170001 [Network] Established Thu 2022/12/29 15:09:57 System -5 Start Thu 2022/12/29 15:10:03 System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2022/12/29 15:10:05 System -7145 ID 0008 :err=0, tag='/var', num=115, nest=4, of Thu 2022/12/29 15:10:07 System -170001 [Network] Established Thu 2022/12/29 15:14:13 System -5 Start Thu 2022/12/29 15:14:19 System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2022/12/29 15:14:21 System -7145 ID 0008 :err=0, tag='/var', num=115, nest=4, of Thu 2022/12/29 15:14:23 System -170001 [Network] Established Thu 2022/12/29 15:18:21 System -5 Start Thu 2022/12/29 15:18:27 System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2022/12/29 15:18:29 System -7145 ID 0008 :err=0, tag='/var', num=115, nest=4, of Thu 2022/12/29 15:18:31 System -170001 [Network] Established Thu 2022/12/29 15:22:45 System -5 Start Thu 2022/12/29 15:22:51 System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2022/12/29 15:22:53 System -7145 ID 0008 :err=0, tag='/var', num=115, nest=4, of Thu 2022/12/29 15:22:55 System -170001 [Network] Established
  9. I don't recall changing a program in a while. I have *many* programs so it is a possibility that some variable or switch setting started an unexpected infinite loop. I will check that next. I replaced the ISY's 5V 300 mA power supply with a 5V 1A supply I had laying around. Nope... The replacement power supply didn't help. It is still rebooting. "ISY Connection failed" in the screen shot comes from my Arduino split-AC-Infrared-remote bridge log. I will do a backup of the ISY and then delete all the programs to see if that is the problem.
  10. Thanks, I'll give it a look and report back. I am dreading replacement of the ISY and all the other stuff I would need. Looks like ~$500 in my case (EISY, Z-Wave module, PLM), unless I can reuse my serial PLM (and it is not the culprit).
  11. For the past week or two my ISY has been rebooting repeatedly. It works OK when it has finished but (obviously) doesn't while it is restarting and polls some 75-80 IoT devices in my home network. It worked perfectly for several years until now. UD Mobile and Alexa connectivity is hit and miss too. Yes, my portal subscription is up to date. I have tried shutting off Email notifications, and stopped polling the ISY's API with some Arduino software I wrote - this did not help. I do have a Z-Wave module installed in the ISY. Any ideas on what could be the cause or has anyone had a similar experience?
  12. @MrBill High Contrast kinda-sorta works. (Thanks lilyoyo1) It is somewhat easier to read but the rest of the screens are butt-ugly That Magenta text has got to go. A larger font size would be problematic since I have hundreds of items in that list - 4 page-down scrolls with all of my scenes collapsed - and on a high res monitor.
  13. Would it be possible to add a color scheme picker to the Admin Console that gives us color blind people a break? Magenta or whatever color that is on Blue is just about invisible to me. Imagine me squinching my eyes and looking at my monitor from about a foot away to see it. This is a problem since I have around 70 devices and >100 scenes. All the rest of the Admin console is fine - just the Main|Network list. I circled the problem areas in the attached screen shot that I have difficulty seeing. I love the blue background - I have no problem with that. Thanks in advance!
  14. I am using an IOLinc to control and monitor my garage door. The problem is when the magnet moves close to the reed switch it closes and opens the sensor circuit a couple times before finally turning "on". I can see the green light on the IOLinc stutter a couple times before going solid, indicating a closed door. The stuttering is probably due to vibrations as the door closes - it is a heavy, hurricane-proof door and weighs a ton. The problem is that the IOLinc sensor sends 3-5 open/close messages to the ISY before stabilizing. This fires my door-status program multiple times in the ISY, sending numerous false SMS messages to my phone. The last SMS is correct, but it is driving me nuts. Does anyone have any clever programming tricks to inhibit the sensor-status program from firing multiple times? I do need it to fire once when the stuttering is over. I also need the sensor program to fire reliably if someone pushes the legacy garage wall opener-button or uses the car-remote.
×
×
  • Create New...