apostolakisl

I have found that searching the forum is very difficult. I have on several occasions tried to find my own posts where I knew I answered a question and struggled to find it using the forum's own search function. I often have better luck doing a google search to find something on this forum as opposed to using the forum's own search function.

I agree you wouldn't want them all listed out on the home page. As it is, the home page is kind of long. A folder like structure where you drill down seems logical. Only "nodeservers" title would be listed, then you click on that to see all the individual nodeservers. Not sure why a forum needs to have every title listed on the home page.

Not sure I agree. So what if there are 500 sub topics? That is like the fact that there are >1 billion websites out there. You only visit the ones you want and the rest being there is no skin off your back. The alternative would be a single stream of discussion that bounces around from one thing to another. I suppose you could tag posts, but that relies on the author going to the trouble to do that. I have seen forums that do it that way and before you can hit the "submit" button you have to put at least one tag. I do agree that there needs to be a mechanism to prevent what is happening to this thread. These last posts have zero to do with the topic. Until AI comes along that lives up to the "I", you need an "HI" to actually read everything and keep it in order.

Did the "wait" used to work? Typically, when people say the "wait" isn't working, it is because the program starts over because of a condition being met within the "if".

I get that banner message on and off even though the user/pass is correct and polyglot is connected to ISY. Michel seems to know about it but hasn't spoke to why it happens or when it might be fixed. Now if your Polyglot is not connecting to ISY, then that would be something else.

before restoring them you can do a "show device links table", then hit compare to see if ISY has it the same. If they are the same, then you have orphan links and a simple restore device will just put the same links back on. In that case, you need to factory reset the devices, delete them from ISY, then start over from scratch.

This is probably the deal. They dont sell ISY because they look at ISY as an Insteon device and figure it is worthless without the PLM. Of course ISY with the nodeserver and zwave support is not so much an Insteon device at all anymore.

I assume you took a backup before you transitioned. Consider going back to whatever functioning version you had and restore your backup.

The app is coming along nicely. Suggestions: For programs, when you open it, have the "run" choices at the top. In all likelihood, that is what someone is looking to do, not check the last time it ran or whatever. That would hold true for other items as well. Put the action items at the top. For favorites: Be able to set a favorites icon to execute. Like it turns the light on, or runs "if" of a program directly. So you don't have to navigate through more menus.

I have the same issue. How is this resolved?

I don't really know what he did, but whatever he did, it allowed me to use the same email address as a sub account. It would seem that this would only be allowed if the primary account he originally created no longer existed. I base this off the fact than when I tried to add him as a sub account originally, it said the email address was already in use. After he did whatever he did, it let me register the email address as a sub to another account. He also tells me that he can no longer log into the original account.

@bmercier How do I get the request to go away? The person deleted his account and I added him as a sub account to another user. But the request is still there.

That info should be added to the wiki as well as the portal page of isy. Also blocked from asking you to accept the request but rather saying the limit has been reached.

@MrBill I already have 5 accounts connected. Adding a 6th. As far as I know you can connect as many as you want. As you can see, it has accepted the request and is asking for me to approve it.

I am trying to add another account. It shows up as an account requesting to be added. I click on "accept" and get the response "bad request". I tried restarting the admin console to no avail.

Twilight duration by latitude and date. Further from the equator, the more it varies by date.

Another trick if you have varying amounts of twilight at different times of year is to use the "sun position" node server. When the elevation hits a certain number of degrees below the horizon, that could be your trigger to turn on lights.

The weather nodes you can install using polyglot include "solar irradiation". This might be better for you than sunrise/sunset. I assume you are very far North and have very long twilight? I'm looking at the weatherbit node and it has that measurement, but I am pretty sure it isn't the only one. This is also affected by cloud cover. Obviously, patchy clouds will be very inconsistent from your location as compared to the measuring location, but on days with horizon to horizon cloud cover you will get an accurate reading.

centering on the current value is another option, currently it starts at the current value and goes up. I still think centering on 72 with a range of maybe 62 to 82 (or more) would be the best.

When you click to change the set temp, I would suggest having it default to 72 degrees as the center point of the shown range to increase the likelihood that scrolling isn't necessary. Also, I suggest a bit smaller font so more can be displayed at once on the screen, again, to keep the need for scrolling down.

I have this issue randomly many times over the last couple years. I have to unlink and relink ISY from Google Home on my Android phone Google "Home" app. Like others, I find it very frustrating.

That is true, but generally you want all controllers of a scene to do the same thing. They used to have a single button that would copy the primary scene attributes to each controller with a single click. They got rid of that. So now if you have a scene with lots of controllers and lots of devices, it is a PITA to go through and set each device's response for each controller.

@hart2hart If there is a reboot command that you can send via REST, then you could put that directly into the program I wrote above using a network resource. But I don't know that Nodelink does that via a REST command. If indeed there is a REST command for ISY reboot, it would be good to have it added to the REST wiki.

Perhaps the simplest approach is to do the following. There are already two time nodes for ISY (ioguys nodelink version and polyglot version) Both have a true/false for DST. When the True changes to False, or vice-versa, that will be a program trigger indicating you just switched to or from DST. Makes no difference whether you put true or false in the if since it is just the change you are looking for. By putting the exact same things into both then/else, these things happen when and only when the DST switches from True to False or vice-versa. At ISY startup, it will have a true or false status, but it shouldn't run provided you don't click "run at startup" . I haven't tested this, but I feel pretty good about it. interupt - [ID 017E][Parent 0093][Not Enabled] If 'ISY Data' Daylight Savings is False Then // Do the things you want to do when it switches Else // Do the things you want to do when it switches

I don't think it is really fair to call the PLM a "controller", it is a modem. As mentioned, everything has these modems, be it a z-wave board, PLM, or a built in wifi board. You could argue that a wifi board isn't a modem, but there are issues with that as well. Most wifi starts running into issues with more than 100 clients and putting in the kind of wifi that can deal with huge numbers exits the consumer market. The PLM's have had failure issues, though the most recent one (fingers crossed) seems to be holding up just fine (as are the ones people have re-capped). Z-wave has also had its issue in that I have been forced to replace my z-wave board, not as a result of failure but rather obsolescence. I don't really see that happening with the Insteon protocol. The death of Insteon has been a topic for quite a number of years. It hasn't happened and I suspect that the current discussion is just one more in this long line. We shall see. I also think Insteon is unlikely to ever dominate the market. The people running it don't seem to have the kind of marketing skills that are needed. I mean look at what Nest did . . . Insteon just didn't know how to jazz it up for the mass market. Seriously, how something as boring as a thermostat came to be such a vogue thing speaks volumes to the marketing people.