macjeff

I tried that. I have edited the program a million times. It works fine after it never runs. Driveway just happened and this is a good example I have two programs run off motion sensor. One counts how many times someone has come in driveway. If its greater than 10 it waits an hour. This is for the lawn mowers that set it off over and over and drive me crazy. THAT RAN but at the same time. Another program has alexa announce someone is in your driveway. It never ran. I made the motion sensor go off again and both programs ran. So if one of the two programs ran its not the device. Its a program thats asleep. Especially when a minute later it ran fine.

The Driveway motion is. I have a different version for day and night so I have day and night folders. but the garage one is not. Its in a folder but not. Just had it happen again and I last ran it about 2 hours ago. Opened garage door- No program but status changed. closed garage- program ran. Opened garage same door worked. Then another door- already open- Closed it and status changed but no program. Opened it and program ran. Closed it and program ran. So its like the programs have to be WOKEN UP and then they work. I guess I could put the program in a continuous loop. Like the last line runs the if again every 5 min or so. But that uses processor.

I have tried for a week (and even the new IoP 5.4.2 update) and cant find a solution. Its usually first thing in the morning when devices have sat for a while. My wife gets up and opens the garage door (IO-Linc). The status changes to ON but the program did not run. I can close it and open it agian and program runs fine. I can try another door and it may or may not work first try. I thought it was ONLY IO-Linc but this am she walked to the mailbox and triggered my driveway motion sensor (insteon). She said she saw it blink and I looked at log and saw that it did report motion. BUT the program did not run. About 10 min later, my son walked past it and it all worked. This is driving me crazy because every test I run works UNLESS it seems to have been sitting for a while. But once it fails it works after that. I checked the program (last time run) and confirmed these programs are NOT running. Any ideas? These are not new programs. They have worked for years on ISY 994i and the devices are showing correct status so the control trigger should work.

I dont know but I was testing a lot of versions for Michel like 5.4.0_1, 5.4.0_2, 5.4.0_3. Those worked fine. but every time it was a upgrade like 5.4.0, 5.4.1, 5.4.2, I had to do this and it fixed it every time. Did it work for you?

This has probably been answered but this is normal now. Clear JAVA cache (And apps) and it should work. The start java app will download the proper version after doing this.

Got it. Not using the "issues" on Github much anymore since the forums are better!!! So did not even look there.

It may be API or ISY limitation but I had a device named Drives/Monitor and it would not add to ISY So I changed name to Drive & Monitor in KASA app and still nothing changes to Drives and Monitor and it came right into ISY

This seems fixed also in 3.0.54. Only issue left for me is the Harmony Hub 3.07 wont upgrade. Jimbo confirmed issue and reported to you.

I hope the power strip uses one ip addres and not multiple ip for each outlet.

So I kind of like KASA but I have like 100 switches in my house so if I replaced them all I would have to have 100 IP addresses. So I was thinking of putting KASA on a different subnet just for the switches. BUT can the Node server support that? It seems to scan your LAN for switches so thinking this wont work.

verified mine actually works also Just activated some things. But it still says 3.06 and if it really installed 3.06 on the next restart it should not try and download it again but it is.

It shows connected but whats strange is ZERO log entries even in DEBUG mode since I did the update to PG3 3.0.54 and I have it on debug and yes I tried to change and restart but still no log entries. Each time i restart it takes forever so its trying to grab stuff from the server but then it comes back on connected at 3.06 not 3.07. Poor @bpwwer Been a busy couple days for him. I assume he will see this and if you need my logs let me know.

3.0.54 should fix these issues. Its pushed now sudo pkg update then sudo pkg upgrade

I restart Node server and I still get 3.06.

try 3.0.54. May fix issues

3.0.54 seems to fix all the issues including wireless tags

Great!! Its not the perfect fix. I think the next version will fix Wireless Tag, Harmony, and Kasa for you. I sent in my logs but you may want to download a log file and send it (PM) to bpwwr At this point dont try the erase and install at this time because what you have working now is better than nothing.

Not sure about Sense but Kasa basically scans your network for the devices. No config needed. I think Harmony does the same thing. So that must be broken. One thing you can try which was previously mentioned. My KASA is working but I did this under 3.0.52 and it worked so now its still working. Go into the Node server, click on LOG, then change the log level which is probably on Error or Warning to start. Go out of Node server. Then try it. If it works you can go back and change your Node server. Unless you want a bunch of Data, or they ask you to put on DEBUG, I would leave on Error.

I am sure it was. WirelessTags was working for me too before but was sending old data. So I deleted it and reinstalled it. The reinstall worked with 3.0.50 but would not authenticate. In 3.0.53 it would not even install. I think you may be onto something. And I think Jimbo and Bpwwer already know this. Some node servers have an API key and those are all working for me. I think Harmony is like wireless tags that it authenticates to Logitech. UPDATE- My harmony is working on 3.0.53 but it is already installed. So it must be just the install thats broken. A support file of some sort is not being installed that it needs but if you already had it installed you are fine. Thats my best guess.

Thanks Jimbo., I hope Michel reads this. He always says its ALWAYS YOU, But again THANKS for taking the time to test. Have a great weekend.

I have some extra if you want to borrow. But you should be able to setup account and install Node server without even having one. One thing about this Node server that’s really different is in the controller (in admin) there is option to monitor tags and you have to set to true as on mine it defaults to false. So out of the box it does not even add the tag nodes. It just monitors the hub. But I am always willing to test a beta before you release it. Just let me know what you need.

Just sent to him (already sent to you so please ignore). Sorry to be such a pain to you guys. If there is a bug I will find it. Thanks for all your help.

Sorry but everything came up but now it wont even let me install WirelessTags. (before it would install but not allow me to authenticate) See screenshot. I will send PG3 log via PM

Thanks!!!

The problem is that I deleted what I had. The issue is the Authorization part is broken. I have no access in the portal. If I use Pg2 I get the access and it works. Then I can revoke it as you said, but when I go to pg3 and add it back I dont get the auth page so I cant go any further. The errors clearly tell me its not going to work. I even tried manually putting the auth code in there and it wont work. So whatever you do, dont delete the Node server or you can probably not add it back. Or try adding it to a second slot. See if it works. For now I have to wait for Jimbo. I can go back to Pg2 until its fixed. These errors are in BLUE in the configuration where in Pg2 and before in Pg3 it would say click here to auth REST Server (False) not running. check Log for ERROR No NSDATA Returned by Polyglot key=None data=None Unable to start server, no NSDATA returned client_id=None client_secret=None This is the entire log!!! And it does not grow 2022-03-25 10:16:29,293 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-03-25 10:16:32,410 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.38 Starting... 2022-03-25 10:16:32,624 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.0.52 [ISY: 5.4.1, Slot: 12] 2022-03-25 10:16:32,627 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2022-03-25 10:16:32,629 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-03-25 10:16:32,636 MainThread udi_interface INFO Controller:__init__: WirelessTag Controller: Initializing 2022-03-25 10:16:32,637 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: wtcontroller not found in database. 2022-03-25 10:16:32,638 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {}} 2022-03-25 10:16:32,961 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-03-25 10:16:32,963 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_12 - MID: 1 Result: 0 2022-03-25 10:16:33,182 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-03-25 10:16:35,644 MainThread udi_interface.interface INFO interface:addNode: Adding node WirelessTagsController(wtcontroller) [None] 2022-03-25 10:16:35,646 MainThread udi_interface.interface INFO interface:setController: Using node "wtcontroller", driver "ST" for connection status. 2022-03-25 10:16:43,377 Thread-5 udi_interface ERROR Controller:handler_nsdata: No NSDATA Returned by Polyglot key=None data=None 2022-03-25 10:16:43,381 Thread-3 udi_interface ERROR Controller:handler_params: oauth2_code not defined, assuming False 2022-03-25 10:16:46,429 Thread-9 udi_interface ERROR Controller:rest_start: Unable to start server, no NSDATA returned client_id=None client_secret=None BTW...thanks for your help!!!