tmorse305 Posted April 15, 2018 Posted April 15, 2018 I just got genmon up and running and it is working to a web page via port 8000. When I try to configure the port in NodeLink it cannot be changed from 9082. Is that the correct port or do I need to change it on the genmon end to 9082? The Main display in NodeLInk shows an endless stream of "GenMon Socket Error: Connection refused. [genmon1]". Is there further configuration on the genmon side to enable NodeLink to communicate? Any help appreciated thanks.
larryllix Posted April 15, 2018 Posted April 15, 2018 6 minutes ago, tmorse305 said: I just got genmon up and running and it is working to a web page via port 8000. When I try to configure the port in NodeLink it cannot be changed from 9082. Is that the correct port or do I need to change it on the genmon end to 9082? The Main display in NodeLInk shows an endless stream of "GenMon Socket Error: Connection refused. [genmon1]". Is there further configuration on the genmon side to enable NodeLink to communicate? Any help appreciated thanks. NodeLink serves it's webpages on port 8090 unless you change it.
tmorse305 Posted April 15, 2018 Author Posted April 15, 2018 I have NodeLink set to 8090, its the port for genmon running on the Pi that's the issue. genmon defaults to 8000 but NodeLink will not let me change it from 9082 in the setup.
io_guy Posted April 15, 2018 Posted April 15, 2018 Default looks like 9082 to me: https://github.com/jgyates/genmon/blob/master/genmon.conf
tmorse305 Posted April 15, 2018 Author Posted April 15, 2018 Agreed! I wasn't sure what port NodeLink was using for communication. I confirmed 9082 in my config file. Any ideas for troubleshooting why the connection is refused? is there other software besides genmon that needs to be running to make the connection? Thanks io_guy.
io_guy Posted April 15, 2018 Posted April 15, 2018 I know zero about genmon. Didn't you have issues connecting NodeLink to your DSC too? Networking issue?
tmorse305 Posted April 15, 2018 Author Posted April 15, 2018 Thanks io_guy, I'll reach out to the creator of genmon. I do have trouble connecting DSC to NodeLink. I'm using DSCLink for now since that works fine. Yet NodeLink can connect to my RainMachine without a problem so it seems like the networking is ok.
tmorse305 Posted April 16, 2018 Author Posted April 16, 2018 I contacted the developer of genmon, jgyates. He had me try the following to test the communication via port 9082. This is my setup: On Pi-1 I have NodeLink (and DSCLink) running On Pi-2 I have genmon running I loaded ClientInterface.py on Pi-1. This is a program provided by jgyates that allows access to genmon via port 9082. I ran this application and was able to access genmon and have it return my generator status. So the network connection between Pi-1 and Pi-2 seems to be ok. I started NodeLink via a putty terminal connection and went back to the NodeLink setup and added my generator back in. As soon as I added the generator I could see in the Putty window NodeLink trying to establish a connection to your default IP 127.x.x.x I forget what it is exactly. Maybe that's normal operation. I changed the IP and restarted NodeLink. It connected, I have no idea what is different as I have rebooted many times before. There is an error reported by ISY now that persists through multiple reboots, see the screen shot. How do I resolve this? Getting closer! Thanks.
tmorse305 Posted April 16, 2018 Author Posted April 16, 2018 Mono Updated, see screen shots. genmon is still working, DSC still a problem. The ISY error is intermittent, restarting the Pi will clear the error most times, see the screen shots with and without error. Any other thoughts on DSC? I tried the raw connection you had suggested in the other thread, not sure what the result should have been. If all else fails DSCLink still works like a champ. Thanks
io_guy Posted April 18, 2018 Posted April 18, 2018 Not sure. Next NodeLink version will have a little more error reporting on the socket, maybe it'll help discover the issue.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.