mdfled

I've run into this issue also. Is there a bug that is causing this to happen? I've not had this issue with years of use of the Admin Console? Could you please explain what is going on Javi?

Another improvement that could be made is the headings for the programs list. At least on my view when I click on one of the programs, the headings in the left box can't be seen without expanding the column so if you aren't familiar with the labels you have to widen the column to read the heading. Hovering over them could show a pop-up of the heading name as an alternative or could the heading labels be displayed vertically so you could read the labels without having to manipulate things? I also haven't found a way to resize the two boxes, they seem to be fixed at 1/2 screen sizes.

Yes it would be nice to hear what UD's plans are for addressing these issues. I wonder if they are working on this? Is there a roadmap we can review to see if these items are being addressed in a future release?

Another thing that needs to be addressed is an error in a program should open the subfolder that contains an error in the program so it is evident when you switch to the program screen the error will clearly be visible.

For some reason this morning my lights didn't turn on automatically. I went into the eisy UI looking for an issue and after a bunch of searching I found that several of the programs wouldn't enable. I went in to look at the programs and it wasn't very obvious where the lines were that were causing the issue (in Admin Console the line would change to an error message and be highlighted with a different color). I loaded Admin Console and quickly located the errors, although the errors don't give detailed information on what changed, at least there is an error. I went into eisy ui and deleted the lines with the error and to the best of my recollection I didn't need the lines that had "set" but the node address wasn't valid. The errors are more cryptic in eisy ui than they were in the Admin Console as there is no indication of what changed and all you see is a node address, not even the node name. It would be really helpful if at a minimum the interface could highlight the lines that are causing the error by changing the lines that are in error to a different color. It would also be helpful if there were more information given so it would be easier to know what needs to be corrected. Information such as the given name and something like "node no longer exists" or "ZB address no longer valid". It would also be helpful if the UI could pop up a message when you try and enable the program and the program won't enable; currently when you try and enable the program there is no response if something isn't right so a user has to go searching for errors. One other "enhancement" I'd like to see is when you go to do a search for a node the tree is collapsed or in the last state. Right now it seems like all the sub folders are open so if you don't do a search every time you go in you have to close a number of sub folders, which in my experience defeats the purpose of having subfolders.

Having been in the door hardware business, I would expect your experience differences between the Yale and the Kwikset locks. Yale is a quality product that is used in large institutions and commercial applications. On the other hand, Kwikset is viewed to be a residential grade lock, something below the quality of a Schlage, Yale, Best lockset and generally not acceptable for the commercial environment. The price you pay is commensurate with the performance you get. When it comes to radio waves instead of wires there are all sorts of things that can impact the performance of a device's communications. Yes better engineering of things like antennas or materials made to make the radio will make a difference and obviously if the manufacturer isn't implementing their system using industry standards you can have issues. In the OPs case it sounds like there is an RF issue as the model of locks they have, based on other user's experiences, seem to be reliable. One of the most difficult things about wireless based devices are the tools to monitor for interference or other errors with the signals can be quite expensive and require some knowledge to understand what you are looking at/for. There are a lot of considerations when it comes to intermittent unreliable signals and troubleshooting. First thing to do is to eliminate all RF producing devices and gradually add them back into the environment (I know not necessarily practical) to see if one of them is causing interference. Most electronic devices give off RF and if they happen to be out of spec or just plain, poorly made they can emit wide spectrum RF noise, which means turning off most everything in the house! For example I have a couple of small portable induction hot plates that when plugged in block my insteon signals. Second, as I suggested, make sure your network (in this case a mesh network) of antennas are robust enough and within the distance of the designed spec of the emitter for proper signal strength. Things like walls, cars, furniture can all block signal so the maximum distances between devices may need to be reduced; this is where adding lots of repeating devices to the network will help with strong signal performance from end to end. Also, as stated earlier you could have a failing repeater that is causing harm rather than helping, so again, eliminating devices and adding them back in will help you find your problem. Looking at error logs can also be helpful in understanding where you are having failures. The above is why whenever possible I use wired connections. Not only is a hardwired device more reliable it also doesn't add to the spectrum of signals in your home/environment.

Hi Gweempose, I've been using the SchlageBE469ZP deadbolts without any hiccups. Part of the reason I selected this deadbolt is it matches the other locksets I have in the house. I'd have preferred a lock that would do reporting on who entered based on code entered and other statics that you get with the higher grade locks, but these work well enough. I've not had any problems with remote locking/unlocking or reporting. I'm using an eisy to control the lock through the Z-wave dongle. Since you've changed your configuration/location and you are having issues, I'm wondering if your Z-wave network is robust enough (has enough devices to be reliable)? You might try adding some Z-wave plug in devices that can help repeat the signal since the plug in devices are relatively cheap for testing? When I started using Z-wave I added several Third Reality plug in switches around the house to act as repeaters. You might have some interference or structure that is blocking some of the signal so try boosting the signal before you give up on the locks.

I was trying to add a 2447D Switchlinc to a scene that is already part of another scene and getting a message do I want to make it a Responder to the scene I'm trying to add it to. The Switchlinc is linked (via eisy/ISY) to two other Switchlincs. So, I'm trying to add "Stair Master Switch" to "Daily Lights" and it is already part of "Stair Lights" scene and is the controller for the Stair Lights scene. When I try to add it to Daily Lights I get the message Stair Master Lights is already a controller for Stair Lights, Would you like to make it a Responder? If I say yes the next popup asks me if I want to make it a Controller or a Responder for the scene Daily Lights. I'm curious as to the consequences if I make it a responder in the first popup and then make the controller or responder selection in the second popup? I'm asking because I've been having the dreaded All-On mystical different lights turning on and I'm trying to rewrite some of my programs to see if I'm getting the errors because of Scenes sending multiple commands to the same device at the same time as outlined in the manuals/wiki. I thought it was better to use scenes to control multiple switches but it seems I don't fully understand what the consequences are and when to use a scene versus when to use manual linking, or to use discrete device commands in my programs. IIRC a long time ago I was told not to do manual linking but to let ISY/eisy control things like linking. In this case, the linking was done within eisy between the stair master switchlinc and the other two associated switchlincs but, at least for me, it is confusing when the UI asks about responder vs controller. Is there a wiki link or something in the manual that better describes when to use which and has examples?

Thanks all, I'll trust that the case is dissipating enough heat. I haven't had any problems to this point, but knowing the chassis is the heatsink, I might have a fan blow on it to help keep it cool since fans are cheap insurance.

Thanks all, I had my eisy mounted on the wall with the brackets that came with it, but felt things were too hot so like I said, I have it propped up so it gets more air around it, but it is still hot. Compared to both Raspberry Pi's I run for my 3D printers, HA installation, and other small SBCs the eisy seems to run hot. I've got some large aluminum heat sinks that I think I'll try first and see if that cools things some. I've never been a fan (pun not intended) of the combination of heat and electronics; the TV above the fireplace design has always made me cringe whenever I see it.

Has anyone added a fan or heatsink to their Eisy to reduce the temperature of the device. When my eisy has been running I can barely touch the case because it is so hot. I used to have it hang on the wall, but I've moved it and propped up one end of the case to get more airflow around the device. I can't imagine that the heat isn't shortening the life of the device. My ISY never ran this hot, are others finding their eisy extremely hot?

GS are you getting an API error for each of the node servers that won't connect or show the nodes in the Admin Console? I just had a problem with the YoLink Node Server, and I was getting an error about the API. I had to delete and recreate the node server to get the nodes to show up in the Admin Console. So, check your error logs when a node starts and post the errors you get when the node doesn't start, and then someone should be able to tell you if you need to recreate the node server.

Thanks gzahar, after trying other things, I did delete and recreate the NS plugin and it fixed most of the problem. I still had to go in and correct some of my IF statements related to the YoLink devices, but the deletion and recreation solved most of the issue. Thanks again!

Thanks for the reply. I found an error that the API was broken (I'm paraphrasing) and searched the forums. I found one of your posts about a new API that was breaking Node Servers. You suggested if the error occurred the user should delete and recreate the NS. I did what you suggested in the other post and the NS started working and all the YoLink devices showed up in AC. I still had to fix some programs as I think they were broken with the broken NS, but the repair was fairly simple, I just had to make a couple of changes to the If line of my program. Thought I'd update you, in case you get other messages that a NS failed after the latest update.

I opened a ticket on this error as my YoLink devices aren't working any longer after I did the latest updates. I've checked all the logs, and the error you posed above is the error I'm seeing in the YoLink node log when I restart the node server. Can you please tell me how to fix this?