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.

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.

Thanks again Kevin, I got the console up finally. I built another pi and it seemed to have trouble logging into the ISY, so I went back to the original SD card and edited the .Screentype file. I also put back in the original Config.txt file since you were seeing something corrupt (I'm in the habit of saving files with a new name if I make a change so that I can always revert to the original version). Everything is up and working, now I need to configure things. I'll do a little more testing to see if I have to have files in the two folders I created on the ISY. I also need to figure out why the other build wouldn't connect. I could see in the ISY error file that there was an authentication error. The console log file wasn't even getting as far as the folder error I originally started out with, I suspect something is funny with the build. I checked the Auth file and it looks like my credentials are correct. I might send you my log files if I can't figure it out. I'm assuming that I can have multiple softconsoles log into the ISY, but I guessed I needed to use a different device name so I called my second build SoftConsole2. I'm assuming each one should have a unique name.... This has inspired me; One project I was working on was the raspberry pi garage door controller. I lost interest since as it is configured, messages would be pushed to my smartphone. I don't normally carry my smartphone around the house; and at night I don't bring it into the bedroom; with SoftConsole I should be able to glance at the screen and make sure the garage doors are down and all our exterior doors are closed. I think the SoftConsole opens up more functionality, thanks for all your work on this.

Kevin, We've made some progress, the cursor now changes about 30 seconds into the blank screen; since making sure I have both types of variables defined. I made sure there are at least 2 variables of each type; just in case the system wants more than one variable much like it's need for more than one folder. Attached are the last couple of log files. I think the current console log file is the last reboot which has the ISY back to no files; which I do so I can easily get back to the desktop to transfer the log files, so the console.log file may be irrelevant. Console.log.3 Console.log Console.log.1 Console.log.2

Thanks Kevin, I'll take a look at this tomorrow. I can't recall what variables I have defined on my ISY. I'll recreate the folders in ISY and make sure I have both types of variables defined. This reminds me of systems I used to work with; every customer wanted their own custom solution; which meant every time there was an upgrade; at least 1/2 the systems would crash because of all the different "customizations" which couldn't be tested.

Ok I added a second folder. Now the raspberry pi goes through a cycle where I have just a cursor in the upper left, and there is no response from the mouse, keyboard, or the touchscreen. The program seems to get caught by a watchdog timer as the desktop will reappear if I leave it sitting. After a minute or two the console will try and start again and the screen goes back to no response with just the cursor in the upper left corner. I've added devices to both folders and I'm still getting the same cycle on the ras pi. I've also moved all my devices to the two folders and I still am getting the cycle. So console.log.1 is with no devices in the two folders, console.log.2 is with all the devices in two folders (SoftConsole1, and SoftConsole2). I also included 3, 4, and 5 which should be logs of the pi cycling through the process. Just out of curiosity (and to make it easy to break out of the loop) I removed the folders in ISY and the pi went back to the original error looking for a folder that didn't exist in ISY, and the pi did the short run and threw the original error. Console.log.1 Console.log.2 Console.log.3 Console.log.4 Console.log.5

Thanks Kevin, Here is the struct.dmp file and the xml.dmp file. Interesting I had to reboot the pi a couple of times to get it to come all the way up this time. Looking at the struct.dmp file, I'm guessing, I have some devices that are structured oddly in the ISY??? struct.dmp xml.dmp

Thanks Kevin, So I added a folder in ISY called SoftConsole and tried to run SoftConsole and it failed. I also tried to move a couple of devices into the folder as I was seeing an error that the values weren't integer values (progress?). It still failed. Attached is the console.log for your reference. I really appreciate all the work that you have done and this looks very promising, the little bit of work I've had to do is nothing compared to what you've done, so no need to apologize. I'm looking forward to the added functionality your project will add to my Insteon network! Console.log

Kevin,I am really interested in getting SoftConsole working, I think this is some fantastic work. I have everything loaded and ran into an error seen in the console.log file snip below. I loaded the mini-test version of the install. Here is the error. 01-08-21 14:50:06 Sev: 3 SysParam: DimIdleListNames: ['MyClock'] 01-08-21 14:50:06 Sev: 3 SysParam: DimIdleListTimes: ['20'] 01-08-21 14:50:06 Sev: 3 SysParam: ErrLogReconnects: True 01-08-21 14:50:06 Sev: 3 Create ISY hub version 0 as My Lighting 01-08-21 14:50:06 Sev: 3 My Lighting: Create Structure for ISY hub at http://192.168.1.10 for user Mark 01-08-21 14:50:25 Sev: 3 My Lighting: Successful node read: 200 01-08-21 14:50:25 Sev: 5 Fatal console error - fix config file: 'folder' 01-08-21 14:50:25 Sev: 3 Traceback (most recent call last): 01-08-21 14:50:25 Sev: 3 File "console.py", line 455, in <module> 01-08-21 14:50:25 Sev: 3 hubs.hubs.Hubs[i] = pkg(i, v.get('address', ''), v.get('user', ''), v.get('password', ''), hubvers) 01-08-21 14:50:25 Sev: 3 File "/home/pi/consolestable/hubs/isy/isy.py", line 312, in __init__ 01-08-21 14:50:26 Sev: 3 for folder in configdict['folder']: 01-08-21 14:50:26 Sev: 3 KeyError: 'folder' 01-08-21 14:50:26 Sev: 3 Console was up: 00mn 24sec 01-08-21 14:50:26 Sev: 3 Console Exiting - Ecode: 13 01-08-21 14:50:26 Sev: 3 Immediate Exit: 13 01-08-21 14:50:32 Sev: 3 End Log I'm guessing the software didn't find the correct folder to read for the password for the ISY???? I checked the Auth.cfg file and it has the password to the ISY correctly listed along with the correct IP address and everything else looks correct. Any idea of where the problem is? One thing I'd like to change is my ISY is listed on the network as ISY99 and not my lighting, but I have left things for now as I'd like to get things working before I start making changes. I am starting with the 7" display and an ADA fruit case but I have a couple of 3.5" screens in the wings waiting to get the bugs worked out.