tazman Posted January 7, 2023 Posted January 7, 2023 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
bpwwer Posted January 7, 2023 Posted January 7, 2023 Are you using wi-fi on the eisy? If so, the eisy's wi-fi implementation is currently incompatible with some node servers, including WeatherFlow.
tazman Posted January 7, 2023 Author Posted January 7, 2023 5 minutes ago, bpwwer said: Are you using wi-fi on the eisy? If so, the eisy's wi-fi implementation is currently incompatible with some node servers, including WeatherFlow. 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?
bpwwer Posted January 7, 2023 Posted January 7, 2023 15 hours ago, tazman said: 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? PG3(x) was never designed to support the ability to change it's IP address. This is mainly due to the fact that to support bi-directional communication between ISY and PG3 both need to know the IP address of the other so if the IP address changes, both need to be reconfigured and there isn't really an API to allow that re-configure to happen. Now that shouldn't effect node servers starting when switching from wi-fi to cable but without seeing the logs, I don't know why they didn't start, but this is something I can try to reproduce. 1
tazman Posted January 7, 2023 Author Posted January 7, 2023 12 minutes ago, bpwwer said: PG3(x) was never designed to support the ability to change it's IP address. This is mainly due to the fact that to support bi-directional communication between ISY and PG3 both need to know the IP address of the other so if the IP address changes, both need to be reconfigured and there isn't really an API to allow that re-configure to happen. Now that shouldn't effect node servers starting when switching from wi-fi to cable but without seeing the logs, I don't know why they didn't start, but this is something I can try to reproduce. 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.
Jimbo.Automates Posted January 7, 2023 Posted January 7, 2023 PG3(x) was never designed to support the ability to change it's IP address. This is mainly due to the fact that to support bi-directional communication between ISY and PG3 both need to know the IP address of the other so if the IP address changes, both need to be reconfigured and there isn't really an API to allow that re-configure to happen. Now that shouldn't effect node servers starting when switching from wi-fi to cable but without seeing the logs, I don't know why they didn't start, but this is something I can try to reproduce.Can't it use localhost instead of an IP address when it sees ISY and PG3 are on the same machine? I actually changed all mine to localhost per Michel when I reconfigured my network addresses a while back.Sent from my Pixel 6 Pro using Tapatalk 2
tazman Posted January 7, 2023 Author Posted January 7, 2023 42 minutes ago, Jimbo.Automates said: Can't it use localhost instead of an IP address when it sees ISY and PG3 are on the same machine? I actually changed all mine to localhost per Michel when I reconfigured my network addresses a while back. Sent from my Pixel 6 Pro using Tapatalk Just for information I have localhost set right now and have also tried with 127.0.0.1
Jimbo.Automates Posted January 7, 2023 Posted January 7, 2023 Just for information I have localhost set right now and have also tried with 127.0.0.1You mean all slots in the ISY admin console Node Server configurations?Sent from my Pixel 6 Pro using Tapatalk
tazman Posted January 7, 2023 Author Posted January 7, 2023 3 minutes ago, Jimbo.Automates said: You mean all slots in the ISY admin console Node Server configurations? Sent from my Pixel 6 Pro using Tapatalk Just for the ISY in PG3x
tazman Posted January 7, 2023 Author Posted January 7, 2023 @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.
bpwwer Posted January 7, 2023 Posted January 7, 2023 4 hours ago, Jimbo.Automates said: Can't it use localhost instead of an IP address when it sees ISY and PG3 are on the same machine? I actually changed all mine to localhost per Michel when I reconfigured my network addresses a while back. Sent from my Pixel 6 Pro using Tapatalk It can and does. There was a bug initially where it would switch it back to the external IP address when doing verification of installed node servers but that's fixed in 3.1.18 But remember, PG3 was designed when most (all) were still using a i994.
bpwwer Posted January 7, 2023 Posted January 7, 2023 3 hours ago, tazman said: @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. WeatherFlow won't work if the eisy is using wi-fi. Currently the internal bridge that's created for the wi-fi network blocks most ports and broadcast messages, thus the UDP packets from WeatherFlow hub are never seen by the eisy. I believe this effects any node server that's using UDP broadcasts. So node servers that send out broadcasts to search for devices on the network will likely fail when using wi-fi. In my case, switching to an ethernet cable caused WeatherFlow to start receiving data almost immediately. I didn't have to restart it even.
tazman Posted January 8, 2023 Author Posted January 8, 2023 1 hour ago, bpwwer said: WeatherFlow won't work if the eisy is using wi-fi. Currently the internal bridge that's created for the wi-fi network blocks most ports and broadcast messages, thus the UDP packets from WeatherFlow hub are never seen by the eisy. I believe this effects any node server that's using UDP broadcasts. So node servers that send out broadcasts to search for devices on the network will likely fail when using wi-fi. In my case, switching to an ethernet cable caused WeatherFlow to start receiving data almost immediately. I didn't have to restart it even. 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?
Jimbo.Automates Posted January 8, 2023 Posted January 8, 2023 5 hours ago, bpwwer said: It can and does. There was a bug initially where it would switch it back to the external IP address when doing verification of installed node servers but that's fixed in 3.1.18 But remember, PG3 was designed when most (all) were still using a i994. Yeah, for sure I realize that when it was envisioned PG would be running on different machines talking to the ISY, but now that it can be on the same machine that makes sense. But mine was someone configured to an IP not valid on my LAN 192.168.1.127, I changed it to localhost, restarted and it's good now.
bpwwer Posted January 8, 2023 Posted January 8, 2023 13 hours ago, Jimbo.Automates said: Yeah, for sure I realize that when it was envisioned PG would be running on different machines talking to the ISY, but now that it can be on the same machine that makes sense. But mine was someone configured to an IP not valid on my LAN 192.168.1.127, I changed it to localhost, restarted and it's good now. The wi-fi setup on the eisy is a little different. I didn't realize this until I started talking with @Michel Kohanimabout why WeatherFlow wasn't working. The actual wi-fi connection is made through a VM and you don't get to see that configuration at all on the eisy. Instead, the eisy creates a virtual network and bridges that to the wi-fi in the VM. So while the wi-fi will get a IP address on your local network, the eisy only sees the IP address of it's virtual network. It was probably that virtual network IP you saw configured (173. something). Because of this PG3x (and node servers) can't actually get access to your local network directly, it all goes through the virtual network via the bridge. Initially, that bridge was pretty locked down and didn't allow much through it. I believe @Michel Kohanimhas figured out how to make it more transparent so things like WeatherFlow will work. However, using wi-fi on the eisy is going to impose some limitations. For example, you'll never be able to connect PG3x to an i994 over wireless. 2
bpwwer Posted January 8, 2023 Posted January 8, 2023 17 hours ago, tazman said: 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? It should switch seamlessly between wireless and wired. At least when everything else is configured correctly. With PG3x 3.1.18, I was able to connect the cable and WeatherFlow immediately started working. No restarts/reboots/re-installs/etc. needed. 1
Jimbo.Automates Posted January 8, 2023 Posted January 8, 2023 Thanks @bpwwer , that explains it.Sent from my Pixel 6 Pro using Tapatalk
tazman Posted January 8, 2023 Author Posted January 8, 2023 3 hours ago, bpwwer said: It should switch seamlessly between wireless and wired. At least when everything else is configured correctly. With PG3x 3.1.18, I was able to connect the cable and WeatherFlow immediately started working. No restarts/reboots/re-installs/etc. 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.
Solution Jimbo.Automates Posted January 9, 2023 Solution Posted January 9, 2023 3 hours ago, tazman said: 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. I had initially enabled WiFi, but switched to Ethernet and kept having problems. I just reset networking with the 4 button pushes described in the user guide and it seems better so far. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Reset_Networking 1
tazman Posted January 9, 2023 Author Posted January 9, 2023 1 hour ago, Jimbo.Automates said: I had initially enabled WiFi, but switched to Ethernet and kept having problems. I just reset networking with the 4 button pushes described in the user guide and it seems better so far. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Reset_Networking 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! 2
Recommended Posts