mdfled

Larry, thanks for the reply. If I understand you correctly, I'm guessing you missed that the motion sensors in question are YoLink sensors and not Insteon sensors? I think I've narrowed it down to one program that has a single YoLink motion sensor associated with it; I reenabled my "laundry room" program and the phantom turn-ons started again. I'm going to try and build a new program to see if my problems go away. Thanks for your input!

Ok, I implemented the program to force the DON for any of my YoLink MDs, and I've turned on one of the MD programs that I disabled when troubleshooting. This morning, one of the phantom turn-ons happened, from what I can tell. I'll turn on another program after a couple more days with the current configuration to see if I have any more phantoms in the house. I'll post back, once I know more.

Ok, I'll see if that helps. Thanks!

Thanks Larry, I don't thing this is communication noise as everything works well with the programs in question disabled. Thanks for confirming that the event log may not show some of the communications where scenes are involved. Obviously, not an ideal situation if you can't see what is going on. I'd love to have a sniffer like device/software that would allow me to monitor traffic in real time! DRPRM1 can you please explain or send me the link for the discussion about using programs to force only on from the YoLink motion sensors? Please elaborate.

Thanks for your replies! DRPRM1 seems to me there is a problem with the YoLink node server since you seem to have had the same symptoms and the removal of the YoLink stuff seems to cure the issue. I only run their motion detectors, so YoLink motion sensors seem to be the issue. Funny, but I have some programs that are running that use YoLink motion sensors, and they seem to be behaving correctly? Also interesting, I have had the YoLink devices for longer than the i3 switches (installed for more than a year before adding i3 switches) so I'm wondering if there isn't something going on between the YoLink devices and the i3 switches. I'll go in and set the error log to level 3 and reenable the programs that seem to be causing the issues.

Recently I was having several scenes turn on randomly. I've monitored the logs and checked link tables. Where needed I've factory reset devices and restored them if I found anything unusual or missing in the device's link tables. After going through all of the troubleshooting and still having issues, I shutdown the eisy to see if the phantom problems went away; with the eisy offline my problems went away. I had noticed that there might be some correlation between my YoLink motion sensors and the random turning on of lights and the central vacuum. I checked and updated the node server for YoLink, still issues. Since I'm using programs associated with the YoLink motion sensors I decided to disable several of the programs that utilize the YoLink devices to see if they were the cause; the problems have gone away after disabling the motion programs that utilize the YoLink devices; I still have some YoLink associated programs running and they aren't causing a problem. I should say, the programs that are disabled are indoors and probably get triggered more than the outdoor sensors, but it has been over a week and I haven't had any random lights turning on. These symptoms then begs the question, is it the program or something strange with specific nodes on the YoLink node server? I'm also curious why I'm not seeing the commands (viewing the logs) from the PLM/eisy when I have the random turn-ons? I wouldn't think the YoLink node server has anything to do with the phantom on commands, and since I have Insteon motion sensors in my configuration, and other node servers, I don't think it is anything unique to motion sensors. I've never stopped the YoLink service so all the motion sensors are still working, I've just disabled the programs the motion sensors are associated with. I haven't removed the YoLink motion sensors, just disabled programs, so I can see the YoLink device's lights when they detect my motion, so I know they are still working and not directly causing any false "on" messages (which I didn't think was likely). If I turn the lights on associated with the scenes that are called in the programs in question, I don't get other lights randomly turning on, so I don't think this is related to the association between devices in a scene. Also, I have a wide mix of devices and ages of devices. This only started occurring when I installed some new i3 devices, but based on symptoms, I don't think the i3 devices are causing issues as things are working fine with the programs in question disabled. My next step will be to one by one turn on, each program to find out if it is one specific program or a group of programs. I plan on writing new programs as a test if the symptoms come back, but I'd like to better understand how a program could run and send out spurious commands without anything showing in the logs? Is there some way communications occur that won't show up in the log, or some other way to configure the log to capture all of the communications? Any thoughts or suggestions would be appreciated. I'll post again if I happen to find a solution as I enable (one by one) the disabled programs.

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.