@Petediscrete, Thanks for your answers.
Obviously, before installation and during the tests with HGHB I LEFT UPNP DISABLED.
As I told you, this is a cool installation of HG, in a new SD Card.
The X10 error, I think it simply derives from the fact that I do not have any X10 device. All my devices are physically connected to RPI via cable and two-way relay. (One for the command and one for the status signal). So in my HG the X10 interface is disabled.
I use the push button of the classic home switches (Bticino), which are also connected to the 2-way relay.
As for the interaction between the GPIO that commands the relay and the GPIO that reads the status of the switch, it’s all thanks to Bounz who helped me creating a program to do this…
Just follow the instructions I advised in the last post.
The HGEB program was put together by @David_Wallis as you probably know. You may want to message him to see if he could shed any further light on your setup and problem or possibly message @Bounz
I configured my setup as I advised you and the only devices I use in HG are X10 which are discovered by Alexa and working fine.
@Petediscrete, thanks for everything. I know that Bounz has some family commitments during this period. I’m continuing to test. I reinstalled everything again, but nothing.
Please, do you know what this endless repetitive error means when debugging HG?
2019-02-28 17:54:20.1619 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1654 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1686 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1728 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1768 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1808 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1869 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1914 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1951 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.1996 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.2035 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.2085 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.2123 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.2158 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
2019-02-28 17:54:20.2199 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8099
The service is not binding to port 8099. I assume this relates to the HGEB service. Try change to a different port for both HG and HGEB. Again both port numbers must match to establish a connection.
Try messaging the HGEB author @David_Wallis and see what he makes of your problem. The instructions I provided to you are exactly the same as I used to get the HGEB service working.
If you can open the HG api without having to sign in the HGEB service should connect to HA without a problem.
Hi @Petediscrete. Strangely this error repeated infinitely is also present with HGEB deactivated.
As you advised me I will try further port numbers. (I tried with ports from 8085 to 8089).
“If you can open the HG api without having to sign in the HGEB service should connect to HA without a problem.”
Please, could you kindly describe the procedure?
Hello @IanR, ECHO Input.
The problem is that the HGEB icon remains Dark Gray …
UPNP Emulator recognizes devices, so I think HGEB should recognize them as well. (The problem with UPNP Emulator is that at every RPI restart, the devices stop working, so you need to delete and search again for new devices).
Excuse me @Petedescrete, I think I did not correctly interpret your previous message. I did not intend to ask you the procedure to install HGHB of which I have already read several times the many explanations in previous posts.
In reference to the Username, I do not know what the reason is, but, also after the new installation, it is automatically set to “Admin”. I tried to remove it from the “Maintenance” menu, but I could not.
Thanks again for all your suggestions.
Hi @petediscrete, As I said, even after the new installation the user name has been automatically set to “admin”. I tried to disable it via the “maintenance” menu, but I could not remove it.
Do you know a method to remove it by editing a file?
(I had also tried to modify the file “Systemconfing.xml” replacing “Admin” with “”. But the “Admin” user is reproposed immediately afterwards).
Try changing admin to something else, save it and restart HomeGenie. If that new user name holds try deleting it and then try installing HGEB and configuring it and enabling it before you restart HG again. This will mean that when you install, enable HGEB and start the discovery service there will be no user name or password present in HG.
@Petediscrete. I believe a step forward has been made. I managed to delete the admin user by changing it to another name before deleting it. Thank you.
The problem is that the icon is still dark gray and I have no more ideas on what tests I can do. I have also tried to changed many settings on the router, but nothing.
I think the problem lies in the error that is repeated to infinity “HTTP binding failed” that I can not understand what it depends on. I changed all the possible ports, and I get the error in both raspberry, even with HGEB disabled.
These are the errors from the log after the last configurations, please, maybe you have some ideas?:
sudo mono HomeGenie.exe
2019-03-03 01:27:59.5608 Debug Adding Gateway WebServiceGateway
2019-03-03 01:27:59.6007 Debug Setting Gateway options
2019-03-03 01:27:59.6060 Debug WebServiceGateway: BaseUrl=/hg/html
2019-03-03 01:27:59.6156 Debug WebServiceGateway: HomePath=html
2019-03-03 01:27:59.6156 Debug WebServiceGateway: Host=+
2019-03-03 01:27:59.6156 Debug WebServiceGateway: Port=8094
2019-03-03 01:27:59.6156 Debug WebServiceGateway: Username=
2019-03-03 01:27:59.6171 Debug WebServiceGateway: Password=
2019-03-03 01:27:59.6171 Debug WebServiceGateway: HttpCacheIgnore.1=^.*\/pages\/control\/widgets\/.*\.(js|html)$
2019-03-03 01:27:59.6197 Debug WebServiceGateway: HttpCacheIgnore.2=^.*\/html\/index.html
2019-03-03 01:27:59.6197 Debug WebServiceGateway: UrlAlias.1=api/HomeAutomation.HomeGenie/Logging/RealTime.EventStream:events
2019-03-03 01:27:59.6219 Debug WebServiceGateway: UrlAlias.2=hg/html/pages/control/widgets/homegenie/generic/images/socket_on.png:hg/html/pages/control/widgets/homegenie/generic/images/switch_on.png
2019-03-03 01:27:59.6219 Debug WebServiceGateway: UrlAlias.3=hg/html/pages/control/widgets/homegenie/generic/images/socket_off.png:hg/html/pages/control/widgets/homegenie/generic/images/switch_off.png
2019-03-03 01:27:59.6219 Debug WebServiceGateway: UrlAlias.4=hg/html/pages/control/widgets/homegenie/generic/images/siren.png:hg/html/pages/control/widgets/homegenie/generic/images/siren_on.png
2019-03-03 01:27:59.6230 Debug WebServiceGateway: EnableFileCaching=false
2019-03-03 01:27:59.6460 Debug Adding Interface Protocols.UPnP Version: 1.0.6945.30619
2019-03-03 01:27:59.6663 Debug Setting Interface options
2019-03-03 01:27:59.7250 Debug Adding Interface HomeAutomation.ZWave Version: 1.0.6937.38455
2019-03-03 01:27:59.7279 Debug Setting Interface options
2019-03-03 01:27:59.7327 Trace HomeAutomation.ZWave: Port=
rmmod: ERROR: Module lirc_atiusb is not currently loaded
rmmod: ERROR: Module ati_remote is not currently loaded
rmmod: ERROR: Module rc_ati_x10 is builtin.
System.IO.FileNotFoundException: Could not find file "/usr/local/bin/homegenie/lib/mig/x10_security_modules.xml".
File name: '/usr/local/bin/homegenie/lib/mig/x10_security_modules.xml'
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x0021a] in <8f2c484307284b51944a1a13a14c0266>:0
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
at System.IO.File.OpenRead (System.String path) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
at MIG.Interfaces.HomeAutomation.X10.DeserializeModules (System.String fileName, System.Collections.Generic.List`1[T] list) [0x00018] in <c86d986153dd46358f54499cd8a040dd>:0
2019-03-03 01:28:00.0530 Debug Adding Interface HomeAutomation.X10 Version: 1.0.6937.38455
2019-03-03 01:28:00.0560 Debug Setting Interface options
2019-03-03 01:28:00.0758 Trace HomeAutomation.X10: Port=
2019-03-03 01:28:00.0758 Trace HomeAutomation.X10: HouseCodes=A
2019-03-03 01:28:00.0928 Info HomeAutomation.X10
2019-03-03 01:28:00.1161 Debug Adding Interface HomeAutomation.EchoBridge Version: 1.0.22.0
2019-03-03 01:28:00.1198 Debug Setting Interface options
2019-03-03 01:28:00.1211 Trace HomeAutomation.EchoBridge: IPAddress=192.168.1.31
2019-03-03 01:28:00.1231 Trace HomeAutomation.EchoBridge: Port=8094
2019-03-03 01:28:00.1293 Debug Adding Interface Protocols.MqttBrokerService Version: 1.0.5767.27418
2019-03-03 01:28:00.1321 Debug Setting Interface options
2019-03-03 01:28:05.8048 Info HomeAutomation.HomeGenie.Automation 16 Automation Program Program.Status Added
2019-03-03 01:28:05.8287 Info HomeAutomation.HomeGenie.Automation 20 Automation Program Program.Status Added
2019-03-03 01:28:05.8326 Info HomeAutomation.HomeGenie.Automation 26 Automation Program Program.Status Added
2019-03-03 01:28:05.8415 Info HomeAutomation.HomeGenie.Automation 34 Automation Program Program.Status Added
2019-03-03 01:28:05.8484 Info HomeAutomation.HomeGenie.Automation 73 Automation Program Program.Status Added
........
2019-03-03 01:28:09.8713 Info HomeAutomation.HomeGenie.Automation 100 Automation Program Program.Status Idle
2019-03-03 01:28:09.8787 Info HomeAutomation.HomeGenie.Automation 142 Automation Program Program.Status Running
2019-03-03 01:28:09.8802 Info HomeAutomation.HomeGenie.Automation 146 Automation Program Program.Status Background
2019-03-03 01:28:09.9021 Debug Event propagation halted - parameter manipulated by automation program 'Pushsafer' (146) (Name=Program.Status, OldValue=Running, NewValue=Background)
2019-03-03 01:28:09.9157 Info HomeAutomation.HomeGenie.Automation 1000 Automation Program Program.Status Idle
2019-03-03 01:28:09.9198 Info HomeAutomation.HomeGenie.Automation 1010 Automation Program Program.Status Idle
2019-03-03 01:28:09.9311 Info HomeAutomation.HomeGenie.Automation 1017 Automation Program Program.Status Idle
2019-03-03 01:28:09.9342 Info HomeAutomation.HomeGenie.Automation 1002 Automation Program Program.Status Idle
2019-03-03 01:28:09.9378 Info HomeAutomation.HomeGenie.Automation 1005 Automation Program Program.Status Idle
2019-03-03 01:28:09.9473 Info HomeAutomation.HomeGenie.Automation 1004 Automation Program Program.Status Idle
2019-03-03 01:28:09.9558 Info HomeAutomation.HomeGenie.Automation 1011 Automation Program Program.Status Idle
2019-03-03 01:28:10.0458 Info HomeAutomation.HomeGenie.Automation 1012 Automation Program Program.Status Idle
2019-03-03 01:28:10.0546 Info HomeAutomation.HomeGenie.Automation 1014 Automation Program Program.Status Idle
2019-03-03 01:28:10.0732 Debug Starting Gateway WebServiceGateway
2019-03-03 01:28:11.8779 Info HomeAutomation.HomeGenie.Automation 88 Automation Program Program.Status Running
2019-03-03 01:28:11.9002 Info HomeAutomation.HomeGenie.Automation 1010 Automation Program Program.Status Setup
2019-03-03 01:28:11.9280 Info HomeAutomation.HomeGenie.Automation 144 Automation Program Program.Status Setup
2019-03-03 01:28:11.9573 Info HomeAutomation.HomeGenie.Automation 1005 Automation Program Program.Status Setup
2019-03-03 01:28:11.9867 Info HomeAutomation.HomeGenie.Automation 180 Automation Program Program.Status Setup
2019-03-03 01:28:12.0154 Info HomeAutomation.HomeGenie.Automation 1000 Automation Program Program.Status Running
2019-03-03 01:28:14.4765 Info HomeAutomation.HomeGenie.Automation 100 Automation Program Program.Status Running
2019-03-03 01:28:17.4566 Info HomeAutomation.HomeGenie.Automation 144 Automation Program Program.Status Idle
2019-03-03 01:28:17.5182 Info HomeAutomation.HomeGenie.Automation 180 Automation Program Program.Status Idle
2019-03-03 01:28:17.7175 Error System.Net.Sockets.SocketException (0x80004005): Address already in use
at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in <bd46d4d4f7964dfa9beea098499ab597>:0
at System.Net.EndPointListener..ctor (System.Net.HttpListener listener, System.Net.IPAddress addr, System.Int32 port, System.Boolean secure) [0x0004a] in <bd46d4d4f7964dfa9beea098499ab597>:0
at System.Net.EndPointManager.GetEPListener (System.String host, System.Int32 port, System.Net.HttpListener listener, System.Boolean secure) [0x000be] in <bd46d4d4f7964dfa9beea098499ab597>:0
at System.Net.EndPointManager.AddPrefixInternal (System.String p, System.Net.HttpListener listener) [0x00064] in <bd46d4d4f7964dfa9beea098499ab597>:0
at System.Net.EndPointManager.AddListener (System.Net.HttpListener listener) [0x00030] in <bd46d4d4f7964dfa9beea098499ab597>:0
2019-03-03 01:28:17.7337 Warn Error starting Gateway WebServiceGateway
2019-03-03 01:28:17.7363 Debug Disabling Interface Protocols.UPnP
2019-03-03 01:28:17.7669 Debug Disabling Interface HomeAutomation.ZWave
2019-03-03 01:28:17.8061 Debug Disabling Interface HomeAutomation.X10
2019-03-03 01:28:17.8097 Debug Enabling Interface HomeAutomation.EchoBridge
2019-03-03 01:28:17.8275 Info Starting HGEchoBrige Version 1.0.22.0
2019-03-03 01:28:17.8971 Info Mig: Connecting to Homegenie API [192.168.1.31:8094] to discover valid devices
2019-03-03 01:28:17.9002 Info Log: Connecting to Homegenie API [192.168.1.31:8094] to discover valid devices
2019-03-03 01:28:17.9042 Error System.TypeLoadException: Could not load type 'MIG.Interfaces.HomeAutomation.Api.HgApiHelper' from assembly 'MIG-EchoBridge, Version=1.0.22.0, Culture=neutral, PublicKeyToken=null'.
at MIG.Interfaces.HomeAutomation.EchoBridge.Connect () [0x0008c] in <1fd2a1daff0b4d9896d231c38ba9a35a>:0
at MIG.MigService.EnableInterface (System.String domain) [0x0003e] in <01eec8bfa28f444d82b2dc82f7810fbf>:0
at MIG.MigService.StartService () [0x00093] in <01eec8bfa28f444d82b2dc82f7810fbf>:0
2019-03-03 01:28:17.9357 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8094
2019-03-03 01:28:17.9388 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8094
2019-03-03 01:28:17.9414 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8094
2019-03-03 01:28:17.9442 Info HomeAutomation.HomeGenie 0 HTTP binding failed. SystemInfo.HttpAddress +:8094
@roberto1979 the answer is in the log. You are trying to connect to a port that is already in use.
Configure HG to use a port that is not already in use by some other service on your LAN. Then configure HGEB to use the same number you used in HG.
Now that you have figured how to clear the user name and password in HG I suggest that you start with a fresh install of HG. Then clear the user name and password and from there follow the procedure to install HGEB.
@Petediscrete, thank you for your kindness to always answer the questions.
The truthfulness of your answer is indeed obvious. However, having tested many ports, I can not explain how all the ports can already be used, and from which services. I will try immediately with additional ports, but in your opinion there is perhaps the possibility that the ports are not in use but perhaps somehow blocked by the router, by the Nat, or for some other reason on the lan? Would you like to tell me kindly if there is a way to check from the terminal the ports in use (or those not used) in the lan? (Similar to “netstat -lnptu/-lt” but doing a search across the entire Lan?