mdfled

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?

I"m having issues with the YoLink node server after the last update. AC will show the YoLinkSetup node as connected, and then drops the "Connected" status indicator after the node server is up and running for a few minutes. I've tried rebooting several times (both NS and eisy) with nothing changing after the reboots. Even though I didn't change anything, I've verified my user credentials in the NS and they are correct. I can see the Notification Controller NS and it is working, connected and functioning, it is only the YoLink NS that seems to be having trouble starting up. Running the error logging and restarting the NS I get the following error: yoLink_init_V3:__init__: Exception - init- MQTT: Unsupported callback API version: version 2.0 added a callback_api_version, see docs/migrations.rst for details The NS screen in the PG shows "connected" after the error posted to the log, so I'm guessing the error isn't the problem? I can upload error logs or logs if it will help. Any help would be appreciated!

EJones, I have a couple of Tuya Human Presence Sensors (HPS) working through Home Assistant (HA). HA is able to trigger a program on my eisy when it receives a notification from Tuya's API. My HA installation runs on my local network, and it runs on a Raspberry PI. You have to use Tuya's SmartLife app so you will need a Tuya Zigbee hub to communicate with Tuya. You will also have to set up a Tuya account and go onto their website to configure your devices and to key in your authentication credentials. Tuya then sends info to HA through the API. There is pretty good documentation on HA's website that will walk you through most of the Tuya setup. Once you have HA recognizing your devices, you can set up an Action in HA triggered by the HPS sensor to run a program in eisy. Right now, I have my programs set up to increment or decrement a variable in eisy that I then use to turn on and to keep on the lights until I leave the room. Now for the bad news. I haven't had the sensors hooked up for more than a week, but so far my impression is, the marketing hype about being able to sense your breathing is a joke. I still find that if I don't move around some the lights start shutting off. I'm not perfectly still, ever, in the room in question, so I'm sure they aren't picking up my breathing when they aren't even sensing small movements. I'm going to add a couple more sensors for overlap and play with layout of the sensors to see if I can get them to perform better. I should also say, I didn't spend a lot on these sensors, maybe $20 per sensor, so there may be better quality sensors that can do the job better than what I've purchased.

Any Zigbee human presence sensor, preferably Tuya device as there a lots of them available! I've got a HAOZEE Sensor from Ali Express https://www.aliexpress.us/item/3256805765649725.html?spm=a2g0o.order_list.order_list_main.23.19fd1802hrsD37&gatewayAdapt=glo2usa Loginovo sensor https://www.aliexpress.us/item/3256805291297545.html?pdp_npi=4%40pre!!US %2428.74!US %2413.22!US %2413.22!!207.96!102.02!%40210313e916994709671554017e092d!12000033255721585!sh!US!4313580587!&spm=a2g0o.store_pc_aeChoiceSimplified.allitems_choice_2005294756320.0&gatewayAdapt=glo2usa Wenzhi sensor https://www.aliexpress.us/item/3256804518651916.html?spm=a2g0o.order_list.order_list_main.11.19fd1802hrsD37&gatewayAdapt=glo2usa I think a lot of these you can find on Amazon as well. These are available in both wireless and Zigbee. I'd be ok with another brand as long as it is Zigbee and a human presence sensor. I'd like for the Zmatter dongle act as the hub so I can eliminate the cloud connection and another hub running in my house!

If Michel is right and you are having DNS issues, it could be your ISP's DNS server. A long time ago I learned that most ISPs do a pitiful job at name resolution servers. I switched to Open DNS's DNS servers and a lot of sluggish and non-responsive queries went away. You could also try one of the evil empire's (Google's) DNS servers as well. 208.67.222.222 and 208.67.220.220 are the DNS servers for Open DNS. Open DNS has guides on their web site if you are unfamiliar with how to configure your router for using an external DNS server. I hope this helps!

I can get a Aqara motion sensor detected by IoX but all IoX gives me in the Admin Console is "Unavailable". My eisy is running eisy (5226) with IoX running 5.6.4. When I try and run (from the Admin Console) "Identify" nothing happens, and when I try and Query, I get an error message. The log shows an error for the ZB 8385.1 entry which I'm guessing is when I did the initial Interview with the device, but no greater detail. This is a MS-S02 model (from the label on the bottom of the sensor). The box it came in states that a Aqara hub is needed. I'll probably send these back to Amazon if a hub is required which is a bummer as I like the ~ 2 year battery life and the size of them is very small. I was hoping to use these under my soffits outdoors so the 2 year battery is a real plus since I need a ladder to change batteries. Some of the other suggested MSs don't offer the same battery life or the small size.

Kevin, I have a personal weather station running Weewx on a raspberry pi. The program is uploading my weather data to WeatherUnderground. I was wondering if you've played with Weewx at all? Have you spent any time looking to see if you could receive the data from Weewx instead of using one of the commercial weather data streams. There is a program within Weewx using a SDR receiver to pick up the transmitted data stream from a weather station so you may be able to pick up a neighbor's data stream if you don't have your own weatherstation. It would address some of the issues as to how often you can get updates from the weather services. https://github.com/matthewwall/weewx-sdr https://github.com/weewx/weewx

Thanks Kevin, I've been working on getting my weather station interface, ntp server, and a couple of other items I want for the consoles, so I haven't had the chance to do much configuration of the SoftConsole yet. I'll update my SoftConsole and install it on another machine probably later this week. I'll let you know if I find any issues.