tazman

@firstoneI would first like to say thank you for creating this node server! I received my FLIRC adapter today and tried to setup the node server but was unable to complete it. I shutdown eisy installed the FLIRC adapter, started eisy then installed the node server from the store and tried running the commands I copied from the github site and it seemed like the first command worked but then the other 2 failed. I assume if I use the Flirc Kodi device in Harmony I don't have to do anything to the FLIRC adapter before using it?? [admin@eisy ~]$ curl https://raw.githubusercontent.com/firstone/eisy-ir-poly/main/reset_flirc.sh -o reset_flirc.sH % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 170 100 170 0 0 266 0 --:--:-- --:--:-- --:--:-- 266 [admin@eisy ~]$ chmod +x reset_flirc.sh chmod: reset_flirc.sh: No such file or directory [admin@eisy ~]$ sudo chmod +x reset_flirc.sh Password: chmod: reset_flirc.sh: No such file or directory [admin@eisy ~]$ sudo ./reset_flirc.sh sudo: ./reset_flirc.sh: command not found [admin@eisy ~]$ @Geddyif you would like I guess you could create a section in the PG3 area for this new node server and move this there.

Thank you that was very helpful!

@MWaremando you know a way to watch the pkg program as it runs or a log that I can look at after to monitor if there are any problems?

This sounds interesting! I assume we can get a generic adapter like this https://www.amazon.com/Universal-Remote-Control-Receiver-Raspberry/dp/B01NBRBWS6/ref=sr_1_1_sspa?crid=S0BU68DGO9YX&keywords=Flirc+IR+USB&qid=1673840873&sprefix=flirc+ir+usb%2Caps%2C166&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUExVTBVRzVMMEZPQjlQJmVuY3J5cHRlZElkPUEwNDE3NjAwMVVLRjBTRlk4U0ZZTCZlbmNyeXB0ZWRBZElkPUEwMDc1NzI5MllTQU9JNTJTOUUxMSZ3aWRnZXROYW1lPXNwX2F0ZiZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU= then we would be able to load the old codes that were used for ISY and are available in Harmony for it?

I have Sensative window/door sensors that shows open and idle so this seems like a issue with certain class of device. I'm hesitant to open a ticket because I'm pretty sure UDI is aware of the problem and it feels like I would just be piling on what they are aware of.

You can scroll through them on UD Mobile. If the item has a numeric value you could pass it on to a variable to be able to see it. There are ways around this depending on what you are trying to accomplish.

You will also need the wire adapter kit UDI sells to connect your serial PLM to the USB port on eisy.

What hardware and software versions are you running on? Have you checked the PG3 log and restarted PG3 after install?

No is there anything in the log file that might shed some light on what is happening?

I would wait for the next update that is supposed to help with the Z-Wave stuff that is expected soon. If not I think your next step would be a ticket with UDI.

Thank you @Jimbo.Automatesthat allowed it to connect to the portal I did notice the eisy was showing connected on both wireless and wired on my router. Thank you @bpwwer for all you do on here, I appreciate all the work you do to get the system so robust for us!

Did you try to exclude the Z-Wave devices before you add it?

Did you try to remove before you add?

When I plugged the ethernet cord in it switches the IP addresses for the services but for some reason it will not connect to the portal. I sent a message to @Michel Kohanim through the ticket system so I'm sure he can help me get it sorted out either wired or if there is a fix for the WiFi in the near future. Thank you for helping me through this @bpwwer.

So it sounds like to get WeatherFlow working I need to change to a wired and when I go to a wired connection the eisy won't connect to the portal so that causes PG3x to fail. So my next step is to go back to UDI to get eisy working with the ethernet cable?

@GJ Software ProductsYes Chris said they were having trouble with the dongle being recognized properly but it seems to be impacting people differently.

@Jimbo.Automatesthis does not seem to be an issue of PG3X talking to IoX because the data does not load in the Weatherflow log so apparently the NS is having trouble getting out of the eisy to collect the data.

Just for the ISY in PG3x

Just for information I have localhost set right now and have also tried with 127.0.0.1

Than you for the information! I can run wireless or wired I just don't know what direction I should go. I don't want to create work for anyone to figure out a problem that is low priority. I am able to use this node server right now so it's not a big deal but I do want to get everything on one machine eventually and I do want to help with anything I can but I am fine if you think I should just wait and the fix will come in the future and this is low priority.

I think what you are missing after you check the Z-Wave support and restart you have to migrate to the matter board for it to show up in the menu.

Yes I am using WiFi I guess that is why @Michel Kohanim was trying to check things out with the ethernet cord plugged in but scary to me is none of the node servers would start with the ethernet cord plugged in. I assume that this is something that should be fixed in the future?

Hello @bpwwer, @Michel Kohanim and I agreed I would take my last 2 issues pertaining to node servers to the authors and WeatherFlow is one I still can not get to work on PG3x. I can install them on PG3 on the Polisy and have them work with IoX on bot devices but if WeatherFlow is on PG3x on the eisy it will not populate data. I am curious if anybody has WeatherFlow installed on PG3x and working at this time? At least I can keep a working version of this running on my Polisy so if there is anything I can do to help let me know what you need and I will do my best to get you the information you request. Thank you Tom

In the AC go to Node Servers Configure pick the node you want to delete and there is a delete button at the bottom.

@asbril the red banners show it's not connected sometimes a refresh of the browser will work and if not logout then log back in should fix it.