macbannai

WOW! Thank you so much for helping. I removed the "bridges" key variable and it was successful to auto discover the hub. However, I did have to go through the restart process of the NS a couple times because the blue banner wouldn't clear, but the moment I pressed the Hue hub button and the light blue banner on the NS went away I knew something was different. The NS logs however did not report anything during all this except the same as I posted above, but the event viewer in the admin console went crazy xxxx_huegrp references which was confirmation PG3 and the Hue hub were communicating. That officially worked, I'll post this on the other one so a solution is presented.

Deleted the nodeserver, re-added it. I've added the bridges key variable only and right now this is the only thing that shows up in the nodeserver logs: 2023-08-22 20:36:00,331 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-08-22 20:36:15,377 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-08-22 20:36:15,379 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-08-22 20:36:30,384 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-08-22 20:36:30,386 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

I can certainly try re-installing the nodeserver again. I have had the IP reservation in place since PG2 and using the same key variable "bridges" to map it to the reserved IP. However, the only thing that changed from the PG2 to PG3 version is that I can no longer add the configuration variables for login and password into the nodeserver config so that it can authenticate to the Hue hub (see PG2 config attached). My PG3 version is also 3.2.2

Hi@Geddyever since I upgraded to Polyglot 3x, my node server no longer is able to see the Hue devices other than it connecting to the bridge. Since that upgrade it's been unable to go further, my understanding was that an updated node server version hasn't been developed for PG3 yet. As you can see, I've even posted in that channel where you shared the link and there have been no responses. How are you using the node server to populate the lights into the admin console?

Has anyone made any progress on re-integrating with their Philips Hue hub since upgrading to IoX and the new zMatter upgrade?

For the tokenFilePath, how to I access root in order to create the new directory for the token.txt file. Also, how do I know if the user running the polyglot will have read/write access?

I'm on PG3x and the node server sees the bridge, but I'm unable to pull any of the bulbs. The log keeps showing the following messages: INFO phue:connect: Error opening config file, will attempt bridge registration ERROR hue:connect: IP Address OK. Node Server not registered. What/where does my Node Server need to register? Any idea how I can register my node server?

I didn't have issues with PG2, but setting up PG3 I've added the 'bridge' key and the log accepts it, but keeping seeing this error message: INFO phue:connect: Error opening config file, will attempt bridge registration ERROR hue:connect: IP Address OK. Node Server not registered. I've made multiple attempts of pressing the bridge button to initiate discovery, but keep getting the above error messages. Any suggestions?

Checking into this, I purchased the remootio device and it works well to open and close my gate. I noticed they posted a lot of their information on their API and was curious to see if anyone was able to setup an integration to their ISY with it? Is this a use-case for my polisy? https://github.com/remootio/remootio-api-documentation/blob/master/websocket_api_v2_specification.md

Understood lilyoyo1, I would be curious if it's possible to leverage access to their API through their WizPro? https://docs.pro.wizconnected.com/#introduction If not, I'll keep looking.

I'd like to control the color changing bulbs I have with Wiz just like I am able to with Philips Hue. I'm curious if anyone has had any success in creating a nodeserver to integrate polisy with the Wiz multi-color smart lights? https://www.wizconnected.com/en-US/consumer/ From their website it appears the integrate with IFTT, Alex and Google.

I'm looking to revive this thread to see if there's been any advances on the above request. I have a couple Yale z-wave locks that I'm considering adding to the Ring z-wave hub mostly for UI (wife thing) purposes, but I would like to take action from the ISY based on events triggered from code unlocks or other user interactions with the lock. Has the nodeserver expanded to add some of their other products and does it allow for the enablement of viewing z-wave lock status?

OK Stu, I just performed the test requested. What was originally connected to the motion sensor load was the 'yellow' wire, I removed the 'yellow' sense wire and touched it to the line and it did activate the micro module and turn on the flood lights. So the micro module is doing it's part. You asked about the specific MS, this is the standard Heath Zenith MS that comes in the box with the mounted floodlight sockets, it shows model number SH-5412, also after speaking with the Heath Zenith support line and they said that the motion sensor doesn't work with relays and only halogen lights. Also speaking with Insteon they suggested that the motion sensor may be giving less than 120v which would cause the result of the micro module not to activate --- which could be a helpful proof from your test suggestion. It sounds like I can still keep the same light mount, but just order a motion sensor that supports the micro module relay, like the cooper or RAD. Is that everyone's best suggestion?

Alright, I have switched out the motion light, this one does not have the dual brite functionality. I re-checked the wiring, the line is connected to both the motion sensor and the micro module. The load from the motion sensor is connected to the yellow sense wire on the micro module, the load from the micro module is connected to each of the lights and still when motion is sensed the micro module won't turn on, I can however turn the light on/off from the ISY. Am I missing anything?

That is certainly a bummer for me, so if I had this version in the link below, would the sense wire turn on the micro module, thus turn on the lights? http://www.lowes.com/ProductDisplay?catalogId=10051&catalogId=10051&langId=-1&langId=-1&productId=50236471&storeId=10151&storeId=10151