swnewman

Ticket opened. Thanks for your help.

sudo uname -a FreeBSD eisy 13.1-RELEASE-p5 FreeBSD 13.1-RELEASE-p5 #7 releng/13.1-n250174-753d65a19a55-dirty: Sun Dec 4 06:58:17 UTC 2022 root@bsdev.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64 sudo tail -f /var/udx/logs/log Thu Apr 6 18:52:11 CDT 2023|/usr/local/etc/udx.d/static/udxops.sh: checking whether or not we have a new version for udx ... That was the entry that came up right after hitting upgrade packages. I waited over 10 minutes and it never gave a new message in the log. I know there is a warning sticker on the eisy about heat dissipation, but this thing is quite warm for not having any real load yet!

The portal tab shows the device as offline, with only the option to refresh. I don't see a way to approve it. I can try to ssh into it tomorrow. What are the remedies if I am in an endless upgrade loop? It seems very strange though for a brand new device to have very old firmware.

I recently purchased an eisy to replace my isy944i. I managed to get it onto the network and can launch the admin console to show the IoX. When I first login to IoX, it asks if I want to install the ISY Portal module. I say yes, and it thinks for some time and eventually comes back with an error every time. I believe I've seen 3 different error messages but I attached a screenshot of one below. Also, since I will be eventually transferring my ISY994i to this eisy I wanted to get the eisy on the latest version. When I go into config and click Update Packages, it asks me to confirm and says I will hear 4 beeps when it is done. I click yes and it immediately closes the admin console. I wait and wait, but I have never heard any beeps coming from the eisy. I wait some more and reopen the admin console and nothing has changed. And it still wants me to install the Portal module. Can anybody tell me what might be going on? Is there a way to manually update an eisy?

Thanks for your help. I've told Mike that I can write up something if needed.

Actually, I got it working finally! I had a problem with how I was parsing the feedback, but now I see all of the messages coming across. I think I still get errors in the log, but I'm getting feedback anyway. Quick question: For updating the state of my devices, I'm guessing I should use the events listed as "ST". Is that correct?

Is there a separate command for "listen mode"? All I do is send the subscribe command and wait for a response on the screen in a feedback textbox. I saw no response to the subscribe command or subsequent ISY update events. The feedback textbox is set to listen for any response (i.e. no parsing). The other user who got this working has shared his setup in the iRule library. I'm going to import his version, when I get the time, to see if I missed anything in the setup.

Well the error log is now working again. I guess maybe there is some delay before it is available.

Okay, another iRule user tackled this and managed to get it working using a TCP gateway in iRule versus HTTP. I've followed his instructions and it looks like I'm getting a good connection to ISY for sending the subscribe command, but I don't appear to be getting any feedback. I just checked the error log after multiple times pressing the button to send the subscribe command and I see errors like the following: -170001 [uDSockets] RSub:32 error:6 -5012 30 -170001 [uDSockets] RSub:33 error:6 -170001 [uDSockets] RSub:33 error:6 -5012 31 -170001 [uDSockets] RSub:33 error:6 -170001 [uDSockets] RSub:33 error:6 -170001 [uDSockets] RSub:33 error:6 -170001 [uDSockets] RSub:33 error:6 Does ISY think the socket is closed? I did notice my rest/subscriptions now has two unexpired subscriptions amongst the expired ones. <Sub isExpired="no" isPortal="no" sid="33" sock="33" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="no" isPortal="no" sid="35" sock="30" isReusingSocket="yes" isConnecting="no"/> On a related note, I decided to clear my error logs and since then every time I press Error Log in the Tools menu it says Request Failed! Is this a bug? I've tried creating more subscribe errors but now it seems I can no longer get the error log to download.

I'll check the logs. Is there a certain command that instructs the socket to remain open? Email sent.

Michel, I still haven't had much success with this. I've tried browser-based plugins on my desktop to try to help me understand the web service subscription outside of the iRule application. As shown in my first post, I can send a subscribe command and get back a "Status 200 OK", along with some xml containing some sort of ID. This is where I hit a road block. Once I am "subscribed" successfully, in theory I should be able to receive event-driven responses (i.e. a switch turning on or off), right? I get no other notices to my desktop when devices are updated in ISY via a switch. Is this even possible in the browser-based approach I am using? Or could you suggest another tool more appropriate to the task? I tried one tool recommended in the wiki but I wasn't even able to get the "Status 200 OK" response to my subscribe POST message. Perhaps I am missing some key piece of knowledge to get this working. Maybe the socket? I am simple following the tutorial for the subscribe command and entering "REUSE_SOCKET" for the report url. Please let me know if that's not right. Sorry for all the questions, I hope you can help me get this working. I've asked for help on the iRule forums but nobody is able/willing to help me. I'm sure it's something simple I'm missing, unless they do not provide the ability for the end user to subscribe to ISY feedback outside of their separate ISY module. That's why I kinda want to get this working outside of their app just to better understand the process. Thanks for the help. -Seth

iRule has an ISY module which I'm sure is set up to work with the web services, but it is fairly limited on how you can design with it. (Trust me I would purchase the module if it would work with my design, it would be so much simpler.) I am trying to do it with the built in http gateway capability. Everybody keeps saying it should be possible, but I have yet to run into anybody that has actually done it.

In my quest to get the iRule app on my tablet subscribed to ISY messages, I've had to try to figure out ISY web services. Without much familiarity with SOAP or WSDL, I was able to do the following from a desktop browser: Using the Postman extension in Chrome, I posted the example SOAP subscription xml to ISY /services. Attached shows the screenshot results of that. Essentially I get a Status 200 OK and some response xml. Assuming that means I have successfully subscribed to ISY, how would I go about viewing messages that should be now flowing to my desktop machine every time ISY records an action? I would like to see the format of the responses to, say, a light switch turning on. I assume it is xml; does it follow the same format as the REST responses? I need to know in order to be able to parse the feedback in iRule. On the other hand if anyone has already gotten subscription to work in iRule, I would welcome any pointers. So far I have not been successful. Doesn't seem like I am getting the gateway and/or command set up correctly. Thanks for your help. -Seth

If you have the URL to the stream on your network, just creat a URL widget with that link in it. Then you can size it to a size that makes sense for the video resolution. That should be all there is to it. You may have to look at the camera's web interface source code to find the URL, or google it. It's camera/brand dependent.

iRule can control almost anything you can send a command to. For cameras, you can add a URL widget with the link to your cameras stream, and then add buttons that have the commands for controlling it. I haven't gone as far as adding the buttons, but I have integrated the streams into my handsets just to get a quick view. The only caveat is MJPEG is not supported. If you have H.264 cameras you should be fine. Also, you can of course control ISY in iRule through the REST interface. This gets you around having to buy the module. I've found some of the customization of the module to be limiting. The only issue with using buttons for ISY in iRule is that device feedback becomes much more complicated. I think they are working on allowing feedback to alter what image is presented on the button.