smorgasbord

Thanks. What about calling other programs? Will something like this work as expected: Repeat while $sOnVacay is not 0 Run Program 'Prog2' (Then Path) $sOnVacay -= 1 I understand that if a single program gets called while it's already running the previous instance of that running program will stop at Wait or Repeat, but if a program calls another program (which could even call a third program), is that all "normal" as an old "C" programmer would expect, or is the execution stack somehow different?

So the plot thickens! In submitting a ticket, it took 4 or 5 tries for the Captcha to connect from my browser. At first I was thinking it might be that I have some sites blocked via my hosts file, but eventually the Captcha pictures came up and worked. I'm wondering if this sort of intermittent problem with the Captcha is connected with my email sending problem. I'm not running my VPN right now, but have in the past...

I've read https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order#Boot/Startup_Sequence_and_Program_Execution_Order but still have questions. I have a program like this: If From 7:00:00AM To 10:00:00PM Then Repeat while $sOnVacay is not 0 (Actions) Else (No Actions) If the EISY reboots during the day, will this program get started (if enabled)? Or, should I set it to Run At Startup and let the "If Schedule" do its thing? The Repeat code essentially does a thing every 30 minutes (there's a Wait) during the From/To time period. I don't want to have two (or zero) copies of this routine running, naturally. EDIT: What I mean by that last comment is a question as to whether programs in EISY are re-entrant. That is, can you have multiple copies of the same program running in different threads at the same time? Basically, if a program is running, and say is at a long Wait, and another program directly invokes the Run(If) of that first program, what happens? And then, if a program is running and is at a long Wait, and one of the If conditions change, how is the program re-run? Does it wait for the first execution to complete or does it terminate what's running to run it again with the new conditions? TIA

After a reboot I tried the Test function again. Got a new error: Also, maybe I should file a support ticket as this is a brand new, just installed today eisy. So, maybe there's an internal hardware problem?

I don't have any SMTP settings since I'm using the default via the check box. I have an excellent 1Gig internet connection. EDIT: Just swapped the cable. No improvement. EDIT: Firmware and UI are both v.5.8.4 I assume the UDI_TREE-STATE files are on the eisy - (they're not on my host, which is Mac). How do I access the folder to delete them? thanks again.

Alternatively, can I write messages to the console? The UD Mobile app has messages for PG3 starting and stopping. Can I write my own messages there? I'm trying to do some debugging on my programs with timers and countdowns and not being able to do the equivalent of printf is pretty frustrating.

Well, now even sending to my regular email address is failing. I've rebooted multiple times. Here's the log for 2 Test sends, nothing really in there except what's shown in the error dialog. ISY Error Log.v5.8.4__Tue 2024.11.05 05.14.16 PM.txt

This may be problematic as the "History" feature ("Get device activity logs") always comes up empty "No Logs Now." I do get historical measurement data, but that's not the same thing. Are there other ways to grab logs in YoLink? As for "theaparm," I don't know. My settings are: Type - Fixed as "Water Depth Sensor" Name Room Measure Range (5m or 10m) meters Tank Depth in feet and inches Unit (cm, m, ft) Density (0.50-1.50) where water is 1.0 Alert for Water Depth range, alert reminder, alert interval Recording Interval Thanks for looking!

FWIW, this was working on my old ISY-99i. Same program (backed up on ISY, restored in EISY).

Can't do either TLS or increase timeout when using the default UD SMTP server.

My ISP is Frontier; My email provider is TutaMail, and I don't believe they provide SMTP services (encrypted service like ProtonMail). I don't know about the "TEXT" feature - can you explain/link? thanks

Just migrated from an ISY-99i to EISY, running 5.8.4, using the default (UD) SMTP server. Email to normal email addresses works. Email to 9876543210@txt.att.net numbers (ATT wireless SMS) doesn't work. However, from my email account, messages to that same ATT wireless numbers works. Error message attached.

Great - thanks so much. I seem to be up and running. Not all of my YoLink devices are showing - I'm guessing that's because the Plug-in doesn't yet support some non-popular YoLink devices like the "Water Depth Sensor."

This is what my Configuration tab looks like, unless I'm looking in the wrong place. I just now went into the YoLink App and created/copied the UAID and SECRET_KEY variables into the "Custom Configuration Parameters". I won't post those here, obviously. Then I did a Restart and got a couple messages, one on YoLink(1) being Disconnected, then Connected. OK, and now in the Admin Console I'm starting to see devices! Still not finding instructions....

Long-time ISY-99i user and have also been using YoLink for a couple years now. Finally decided to integrate the two, and so just bought and installed my eisy. Got the old Insteon devices and scenes and programs up and running again, got the trial version of the YoLink plugin installed, and now can't figure out how to get my few dozen YoLink devices added and managed. I did an Add All Nodes from the Yolink menu, but that didn't seem to do anything. I went to Add Node, but the menu has all sorts of repeats and I can't find things like the YoLink Plug (see attached screen shot). Sorry, but I literally don't know what to do next.

I admit I haven't been paying any attention to ISY stuff for over a year now. When SmartHome went under, it seemed that Insteon might be in trouble and there was some effort in trying to get Insteon devices going again. That's about the time I started adding YoLink devices - I started with the water sensing devices since my well water tanks are located 600' feet from my house and the LoRa range they offer was nice. I ended up with some thermostats, open/close sensors and relays, and a few other things as well. At that time (a year or two?) I checked the forums here and there wasn't anything I found on YoLink, and it didn't seem like that was going to happen. It's great that it did! If you've got a pointer for me to start looking at, that'd be great, and if EISY can control my YoLink and Insteon devices with programming logic, I'll certainly get on-board and migrate.

OK, so I reconfigured my router to use the 192.168.1 IP pool instead of 192.168.50 IP pool and sure enough, the ISY showed up after reboot! Now I should probably remove the static IP setup in the ISY and do it only in the router, for when I upgrade my router again - last time was over a dozen years ago so no complaints on that. Of course, my portal lease is up, and it's now $44/year. A new eisy is $255, but considering I'm using it for my now also discontinued Insteon devices I don't have much incentive to upgrade. If eisy would support the YoLink set of devices, I'd be all over it in a heartbeat.

This the first and so far only thing I've noticed wrong. Since I changed the SSIDs I'm using, I had to reconnect all of my wireless devices anyway, and the few wired ones are all working. The ISY is the only thing so far I can tell hasn't re-connected. The portal doesn't work either, as expected when not seeing the ISY in the router's client/device list. It's good to know the ISY will function and make Insteon devices using powerline/wireless do their things, and that internet is only/mostly for talking to the ISY.

OK, so I have a new router. I think what's going on is that the new router's address range is 192.168.50.XX whereas the old router's address range is 192.168.1.XX. I don't see the ISY in the router's client list (short list since it's ethernet cabled), and I can't connect to the ISY admin console. I tried resetting my Java cache, too. Rebooting the ISY doesn't help. If I unplug the ethernet cable to the ISY, the Memory and Error lights blink, which is to be expected for no ethernet, so it does see ethernet, the router just doesn't allow it to connect. I'm using DHCP on the router and do not have any manually assigned addresses. My only thought at this point is that perhaps I gave my ISY a static IP (because I had a bookmark for http://192.168.1.200/WEB/INDEX.HTM) and now my router isn't allowing 192.168.1XX addresses. So my two options are: 1) Change the router to use 192.168.1 instead of 192.168.50 for its LAN address range 2) Reset the ISY to factory defaults (if in fact it's using a manual static IP) The ISY is functioning fine, btw, as my programs are all running and I've verified that inputs run programs and cause the right things to happen with my Insteon devices. So, are those two items what I should try, and in that order, or should I check/do something else first? thanks!

Yes, it did. Did that AND ran both cables through my LANSeeker cable tester just in case.

OK, did the reset while connected to the EZIO8SA, per instructions. Got the confirming double-beep a bit after I let go of the SET button. Connected to the PC and got this: So not 80 00 00 06 but 00 00 03 06 Does that help identify where the problem might be?

So for "Factory Reset" that's the Press and Hold the SET button in while plugging the EZICOMM back in and hold SET until it the beeping stops. Then it'll buzz/beep again. I should do this while the EZIO8SA is connected, right to it, right? There is no separate EZIO8SA reset that I know of. Then go to ISY Admin Console and try to add the device? Or, unplug the EZIO8SA and connect the EZICOMM to the computer and run Docklight again? Thanks much

Thanks @Brian H, but if you don't mind, can we get specific on the steps I need to take? I think they are, in order: Connect PLM to EZ8IO with ethernet cable Plug PLM into power Plug EZ8IO wall wart into power ??? I'm not sure what I'm debugging here. My problem is that my ISY isn't recognizing the EZ8IOSA device properly. It comes in as "unsupported device." Do I reset the EZIOCOMM while it's connected? How am I using the connection cable from the EZIOCOMM to the PC if that means the EZ8IOSA can't also be connected at the same time? Sorry again, I'm very confused at this point.

I also connected the SHN utility and tried connecting through that: But, I don't have any instructions or idea of what I'm doing. Note that when the PLM is connected to the laptop, the EZIO8SA box itself is not connected to anything, since there's only one RJ-45 out of the PLM. So, I'm a bit confused as to what I should be doing. Sorry for all the newbie questions. I actually am reasonably technical, but not at this kind of low-level stuff.

OK, got DockScript and the PLM.ptp file and did some of the preliminary commands: What's my next debugging step here? TIA