david-4

I just found the problem! How stupid of me. There was a space at the Beginning of the UAID field that I never detected. Everything seems to now be working. Thanks everybody for your help.

I verified that there is no space at the end of the UAID and key. I just PM you with the logs. I appreciate you taking the time to help me with this.

I did this when I first set it up and it accepted it. I tried all this. And I have done a reboot of the Polisy from the configuration page of the AC. I agree, It looks like it has a problem with the Token. But the hub showes up in the Polisy and moble ToLink app can see all the devices.

Only one node for the hub, no others : I have restarted AC and stopped and started node and refreshed webpage multiple times. As suggested I ran debug: 2024-09-23 17:55:25.715 Thread-7 (start) udi_interface INFO yoLink_init_V3:__init__: Trying to obtain new Token - Network/YoLink connection may be down 2024-09-23 17:55:25.716 Thread-7 (start) udi_interface INFO yoLink_init_V3:refresh_token: Refreshing Token 2024-09-23 17:55:25.716 Thread-7 (start) udi_interface DEBUG yoLink_init_V3:refresh_token: Exeption occcured during refresh_token : 'expirationTime' 2024-09-23 17:56:00.723 Thread-7 (start) udi_interface INFO yoLink_init_V3:__init__: Trying to obtain new Token - Network/YoLink connection may be down 2024-09-23 17:56:00.724 Thread-7 (start) udi_interface INFO yoLink_init_V3:refresh_token: Refreshing Token 2024-09-23 17:56:00.724 Thread-7 (start) udi_interface DEBUG yoLink_init_V3:refresh_token: Exeption occcured during refresh_token : 'expirationTime' 2024-09-23 17:56:18.103 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-09-23 17:56:18.104 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-09-23 17:56:18.105 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-09-23 17:56:35.730 Thread-7 (start) udi_interface INFO yoLink_init_V3:__init__: Trying to obtain new Token - Network/YoLink connection may be down 2024-09-23 17:56:35.731 Thread-7 (start) udi_interface INFO yoLink_init_V3:refresh_token: Refreshing Token

I don't see any YoLink devices after installing the YoLink node. I have Yolink working on my phone and have three water leak detectors running fine on the Yolink hub. I have loaded the User Access Credentials in the YoLink Node configuration and I have restarted a couple of times. I have even rebooted the Polisy. The YoLink hub shows up in the AC but no other Yolink devices. When I click on add node I get the following window. What do I put in the fields to find my leak detectors. Everything I have tried just returns an error.

I had done reboot by pressing the button on the polisy box 2 times. And I ran an update within the last month. I will inquire about these errors. I think they are indipendent of my IP address problem. I was able to fix my IP address problem with Michel's help.

As suggested, I opened a ticket. The problem has been solved thanks to Michel. My understanding was that the IP address was set to a static address in the configuration file /etc/rc.conf. I suspect it had been carried over from a setting way back in an early version of ISY when you still could set fixed network setting. I had built my system back on ISY version 3.x and just kept upgrading then moved it to the Polisy. More resent versions are locked to DHCP and do not allow you to change network setting within the ISY. The config file held the network setting from the original installation. The fix was to SSH into Polisy then edit the /etc/rc.conf file as follows: find: ifconfig_igb0="inet 192.168.1.56 netmask 255.255.255.0" replace with: ifconfig_igb0="DHCP" remove: defaultrouter="192.168.1.1" Then do: sudo service netif restart

I have no idea if these entries are significant, but I found the following lines in the Ploliglot log after I did a system restart: polisy daemon[2872]: 12/18/2023, 13:29:39 [pg3] ^[[31merror^[[39m: Getting IoP UUID failed: Error: connect ECONNREFUSED 127.0.0.1:8080 and polisy daemon[2872]: 12/18/2023, 13:29:59 [pg3] ^[[31merror^[[39m: stderr: pkg: Repository FreeBSD missing. 'pkg update' required polisy daemon[2872]: pkg: Repository FreeBSD cannot be opened. 'pkg update' required polisy daemon[2872]: pkg: Repository FreeBSD-base cannot be opened. 'pkg update' required polisy daemon[2872]: pkg: Repository udi cannot be opened. 'pkg update' required

Interesting idea. How do I access the polisy network logs? I don't see anything about IP address in the IoX Log or the Polyglot sytem log.

There is a way and I have done so.

Yes. I performed a proper shutdown, remove the power source. I left it unplugged for about an hour before reconnecting the power. I also tried rebooting the router. I tried different ports on the switch and different switches. I even try changing the lease time. I've tried all these solutions many many times. I've been successful with every device except the Polisy.

I have all my IoT devices on a VLAN specifically for IoT. To do so requires that I change the third octet of the Polisy IP address to one in the VLAN group (xxx.xxx.40.xxx). I have a Unifi Router with DHCP enabled. I can successfully assign an IP address to the Polisy if I only change the last octet of the address, but when I try to assign an IP with a different third octet the Polisy IP does not change. I can't change the IP address from within IoX because Polisy/IoX 5.7.1 defaults to DHCP and has disabled the ability to set a static IP address from within IoX. When I set my router to assign a VLAN IP address to the Polisy, The Polisy does not change its address. Are there IP address limitations hard wired into the Polisy? How can I change the address so it can join my IoT VLAN?

I think you are right. I appreciate all your help. Thanks

I don't know if it is causing a my problem or if the Ecobee is a symptom of my problem. Some of my Insteon devices started coming on or turning off are on expected time. It began around the same time as the increase in Ecobee log entries. I have been unable to locate the cause. I have had to disable most of my lights because they wake people up in the middle of the nights. My First we're getting annoyed with all of my outside floodlights coming on and off throughout the night. I have been unable to isolate the problem. I'm looking at all options

Are suggesting that there are two thermostats, or are you referring to the thermostat and the little ancillary sensor? I only have one Ecobee. The remote sensor that came with the Ecobee will not stay connected so I thought I disabled it. And why the sudden increase in log activity?

I have been trying to diagnose why my lights throughout my home seem to turn on or off for no apparent reason. Although I have not discovered the reason why this is happening, one of the things I did learn during my investigations is that my IoX logs are chocked with Ecobee node server entries. Ecobee NS is creating simalar entries multiple entries within a single second. I would say 90% of my log entries are ecobee. It started on 10/28/2023. Between 10/28 and 11/14, over 17 days, there are 17,583 log entrees! over a thousand a day! This seems excessive activity on my IOX network. I am running IoX5.7.0 on Polisy with PG3x 3.2.16 and Ecobee Node service 3.1.5

Thanks. It is now working. I appreciate all your help

I will give it a try tonight. Thanks

Thanks for the reply. I'm running IoX 5.7.0 All I did was click on the Zigbee check box. Then clicked Restart IoX. after Admin console closed, I waited for IoX to restart and restarted Admin Console. It's still installing 6 hours later. BTW, when I click the Z-wave menu item on the top bar, it says Z-wave dongle not responding. (It used to show a dropdown menu)

I am trying to initialize zigbee capability. I did exactly as the above says. Then I reopened the Admin Console and a window popped up that said "initializing system" It slowly goes from 1% to 100%, closes then reopens the same window and starts the slow count all over again. Then it repeats again and again. Its still running for 2 hours. It says do not unplug or power off. How long do I give it before I try to shut it down - and how should I commence.

Thank you for your reply Bob. I found my mistake. When I migrated from my backup I clicked the file to load the file but I didn't click it again when the button changed to "Restore" I went back and did the process again, properly, and it is now working. Thank you for your offer of help.

I've gotten PG3x loaded on my Polisy so I can use the IR receiver I ordered. I followed the instructions in the newsletter from UD last week. But now none of my Node Servers will run. I first updated to 5.5.9 on Polisy then to PG3x version 3.1.24. I've properly rebooted. My IoX is running fine from my AS - except that none of the PG3 nodes are working. When I log into the Polisy, the dashboard says It's connected but all the Node Servers say Disconnected. I've tried clicking Start. I've tried clicking Restart. I've tried restarting Polyglot and I've tried rebooting the Polisy. Nothing starts the Node Servers and the logs for each of them are all empty.

True, but my vocal home control commands do not need the full capability that an online "Assistant" tries to provide. I'm comfortable continuing to go to Google or Amazon echo devices to make generalize inquiries, but I'd rather not have my home control devices reliant on the Internet.

I believe Home Assistant has a small team working on it also.

This is why we need a local voice Recognition server. I don't wanna rely on the Internet connection to hold my home. I also don't want to build my system around a third party like Amazon or Google that keep changing things. Once I have it working, I wanted to stay that way Unless I decide for some reason to up grade.