Everything posted by apostolakisl
-
Backup Request failed with status code 500
This is probably a permission issue related to one of your plugins. I have had some people have issues while others not from plugins I wrote. Though I believe this is not isolated to my plugins. Currently I am running the latest firmware from the staging repo and all of my plugins installed using eisy ui plugins interface and backups work on my eisy. Ud has said that they are going to fix this on their end, but if it is one of my plugins I would be happy to work with you to debug.
-
EISY-UI time display discrepency
No doubt, the html user interface loads the time from eisy when you first load the page, then the clock "ticks" using your browser's time keeping. The web browser may not keep the greatest time and can get out of sync. The longer you have the browser open, the more it can get out of sync. It may periodically re-sync, I don't know. So that is probably why you see a few seconds difference. The programs are triggering off of eisy's clock, not what the browser shows. Open the ssh clock and compare that to something you know is spot on to ensure eisy clock is correct. Assuming eisy clock is correct, you can look at what time eisy says it ran programs vs what time it should have run programs (using the program summary page if you only need to see the most recent run of the program). And finally, compare what time eisy says is sunset vs what time the sun actually sets. Of course that is tricky because sunset is affected by your precise lat/long as well as your elevation and the elevation of land around you. That lat/long part is an easy lookup, but the terrain stuff not so much.
-
EISY-UI time display discrepency
Ssh into eisy and use this command to view the actual time eisy thinks it is. while true; do date '+%Y-%m-%d %H:%M:%S'; sleep 1; done
-
Verizon email to text is being shutdown.
@Ross I played around with it. GV email to text appears to ignore single line breaks and truncates the message at a double line break. Makes sense since emails will often times have a bunch of non-texting relevant things like your company/phone number/etc that you would rather not have in a text. I tried both html format and plain text format and the results were the same. My suggestion to you I guess would be to put multiple spaces or dashes or some other character to break it up. Maybe you play with it and discover a certain number of characters will roll it over to the next line? So maybe you get something like Mon 65........................................... Tues 68........................................... Wed 74.......................................... etc.
-
EISY-UI time display discrepency
I put full logging of all program activity into IoX Logger plugin. Very helpful in situations like this. I used to write programs sending me emails every time a program ran when trying to debug stuff like this. @IndyUDIuser
-
Verizon email to text is being shutdown.
@Ross 1. Not sure I understand. I've never sent anything via Google voice text that was more than a few words. I use it for quick alerts, like "trash day" "washer done" "alarm armed" . . . 2. You can do email to text to any number of people. You just need them to first send a text to the Google voice number. Once you have that "from" email address you are good to go. I have been using the same "from" addresses to send my wife and I texts for at least a decade. That email address does not appear to ever expire. Currently I send texts using that setup to about a dozen people. You can not do group texts though. If you want to send the same text from iox to multiple people you need to do it with multiple emails, one for each. Group texts in GV will get forwarded to email, but a reply won't go through to anyone. In other words, the "from" address in a an emailed group text is a dead end. Replying to group texts must be done from within GV itself. The critical part of the email address is that you send it from the same email acct it was sent to. Not positive on this point, but it might need to be a GM acct. But I have never tried using a non GM acct with this so maybe not.
-
Upgrading ISY/Polisy to Eisy
Then you will need separate iox systems for each location if Insteon is used.
-
Polisy Running EisyUI plugin issue
This had been several days.
-
EISY-UI time display discrepency
just postulating here, but I would say that one of the sunset timers is using your configured location and the other is using your IP address for location.
-
getting an error when trying to backup using EISY-UI
504 is a gateway timeout. Might mean the eisy backup service hung. did you try a reboot of eisy?
-
Upgrading ISY/Polisy to Eisy
Is your electrical system all behind a single meter? If so, chances are better that Insteon will work between them. Also, depends on how far apart the buildings are. If they are next to each other, then Insteon RF will move between them even if on different electric service. I succeeded here with two buildings that were several hundred feet apart by basically running an extension cord from one building to just inside the other building. I got a 500 foot spool of lamp wire which I ran through a conduit, put a male plug on the source building and a female plug on the wire at the other end. I plugged the wire into an outlet next to my plm in building 1 and plugged a dual band Insteon device in at the far end of the "extension cord". I fused the wire at 100ma plus gfci to partially compensate for the complete lack of code compliance. It works great for now like 15 years. The lamp wire takes the Insteon traffic via power line communication to the second building and then the dual band device in building 2 emits it as rf that devices in building 2 pick up and then rebroadcast as both rf and plc. So two buildings 500 feet apart on two different electric services all are on one Insteon network. I also have both buildings on the same LAN, so all of my IP devices running on IoX plugins work great in both buildings. I have a Polisy at this location and installed eisy ui on it. It works fine, but as mentioned, it may not accept future updates. There are instructions on the forum for updating a Polisy to Eisy UI. And as mentioned, the Java ad con still works. Currently I mostly use the Java console but am slowly using eisyui more and more. In my opinion, the eisyui is a mixed bag of superior/inferior to the old console. Some things I can do far faster on the old ad con and some things I can do quicker on the eisy ui.
-
Polisy Running EisyUI plugin issue
I have two plugins on my Polisy installed from the eisy ui plugin section (not pg3x). These are two that I created and installed them from the developer section of eisyui, (where you set purchase options). On my eisy, when I push an update to git hub and update the store version, the plugin then reports that an update is available. But on the Polisy there is no mention of an available update. I had to click on re-install which did then install the latest version. The Polisy is running the current up to date production version of all the packages. Basically, it looks like the Polisy with the currently up to date production packages isn't doing version checks on plugins.
-
Verizon email to text is being shutdown.
Google voice does email to text. Create a Google voice account and enable text to email feature and set a Gmail acct as the forwarding email. Send a text from your phone to that Google voice phone number. The text will show up in the Gmail acct as an email. Now configure your iox to use that Gmail acct as the email server. Now copy the from address in the email Google voice sent you and put that as the to address in your iox email notification. Now any email you send from iox to that address will get sent as a text to whatever phone you originated it.
-
IoX Logger Now Logs Programs
@Ross Updated the plugin so if you put in http:// it redirects to https://
-
IoX Logger Now Logs Programs
did you use https:// your screen shot shows http://
-
IoX Logger Now Logs Programs
Are you running 1.1.0 or 1.1.1. I had that issue as well and thought I figured it out and fixed it with 1.1.1. I'm hoping you are 1.1.0 cause if not I have to look at that some more. The plugin was running and logging, but the html wasn't working. Currently I am not having issues running 1.1.1. EDIT: I see the issue, https:// not http://
-
IoX Logger Now Logs Programs
I added logging of programs to IoX logger. No more frustrating only getting to see the last run of a program when debugging a misbehavior. You can see all the runs and whether it ran then/else. It is all handled through the html interface at port 8765 as before. It will log all program activity when enabled for a selectable period of time. You can search the log within the html window, or you can download a csv file and use your preferred program to organize and search it. I also added authentication to open the html control page. To enable the logging, you will need to enter your LOCAL iox username (admin) and password. Not the portal credentials.
-
Latest eisy update crashes all plugins
I appreciate what you are saying. But in my case, many more than 5 minutes passed. I didn't do a reinstall all, I reinstalled one at a time. And I missed a couple. Like an hour later I was checking things out and discovered the ones that I missed still not working. Reinstall fixed them. Not the end of the world since a re-install is a benign action, but still. Also, at midnight, it looks like I may have had a double run again of my MN programs. It is possible that the false run of the program was earlier in the day and associated with a reboot after the update. Though a reboot or update should not trigger a program that is scheduled to run at MN to run when it is many hours before MN. I assume that all program runs are in a log somewhere via ssh, but from admin con I can't tell anything but the last run.
-
Latest eisy update crashes all plugins
Restarting did not work. Restarts just made the "connected" green logo blink. I had to reinstall. Reinstall in reality is not meaningfully different than restart, but still, indicates a deeper issue. Unless you were running an older version of the plugin and didn't want to update.
-
Latest eisy update crashes all plugins
I forget what version I was on before the eisy update, but it was maybe whatever was current as of last weekend. All of my eisy plugins after this update failed to function. Hitting "restart" did not do the usual restart of seeing it stop/start/connect. They instantly showed "connected" after hitting restart and they still didn't work. I had to reinstall every one of them. That includes plugins that were not migrated pg3x plugins, ones that were originally installed as eisy plugin. That included local plugins in eisy plugins as well.
-
Latest eisy update crashes all plugins
I just installed the latest update. After the update, the only plugins that worked were the legacy pg3x. All eisy ui plugins failed. I had to reinstall every one of them which so far seems to be bringing them back to life.
-
Plugin Bugs That Cause Eisy Backup Failures
To keep my life simpler and have my system backups be full drop in backups, I am installing all of my plugins from the store, even ones that are just for me. Initially I get something going as a local plugin, then I push it to github and put it in the store with status "new". "New" is not exactly the best word to describe what is really a development plugin, one that is only accessible to the developer. So while it is in the store and when installed on Eisy looks like any other store plugin, it doesn't appear in the public store. The installation of these is done from the developer section purchase options configuration page. Also, when I'm testing a plugin, it is nice to have it installed in folders with the same permissions that the public will end up with. I have had permission issues before where the plugin worked as a local plugin, but had permission problems when installed from the store.
-
Eisy_Backup Has Its Own Thread
If you have any questions or comments, please use this thread. Or you can PM me. Unless we find some bugs, I think the current release is the full feature release, and don't expect any further versions. But UD could also make changes that require changes to the plugin. If you installed the previous release, please see my notes in the other thread I posted. But basically, if you update, you will need to fully delete and install the plugin from scratch. But the latest release doesn't add any new features or fix anything, it just changes how the oauth with google is handled and you don't need to update at all if you don't want. Unless seeing that "update available" message causes you lost sleep. One comment: you will notice that if you manually run a backup using the eisy-ui interface that your backup is double sized. That is because this plugin saves the most recent backup on eisy itself (as well as pushing it to google/usb/nas). When a backup is triggered from this plugin, the first thing it does is delete the local backup so you don't keep get recursive backups inside of backups. Manually doing it from eisy ui won't delete that, so you will get one backup inside of the backup. it will never grow to more than that though. If you delete the plugin, that local backup is also removed. That local backup is accessible and downloadable via the plugins html page, should you want to retrieve it. The new version makes the plugins html page unnecessary if you only are interested in backing up to google drive. Google drive is fully configured now from the admin console or the eisy ui nodes page. You will only need to use the html editor if you want to push to a nas drive or a usb drive. Adding a usb drive also requires running a single command via ssh.
-
Plugin Bugs That Cause Eisy Backup Failures
Yes, local plugins aren't part of a backup so I would assume that it would not mess up a backup. I have seen the 500 error twice and both times it was my fault because of something in my plugin. But the first I only discovered from a user of my plugin since I had it installed local on my system. I have switched now to developing my plugins via store installs. I start the plugin locally, push it to github and then post it to the store as "new" so it is not visible to the general public, then I push all my changes to github and do "reinstalls" as I work through the development.
-
Plugin Bugs That Cause Eisy Backup Failures
I would say very nearly 100% chance. Good deal. Does this mean a permissions issue in a plugin gets ignored and everything else backs up, but the particular plugin does not get backed up? And if so, do you still get an error to know you need to fix something?