Bounz,
Thank you so much for your answer!
The problem is that I’m trying to configure Alexa only via App on the phone, without any devices.
Please, could you tell me if this is possible, or is an echo device essential?
Alternatively, I was thinking of buying the new “Echo Input”, so that I can place it on the ceiling and connect it to my audio system. Please can you tell me if anyone has already tested Echo Input compatibility?
P.S. I installed HB on two different RPIs. A RPI2 with HG V.1.br526 and RPI3 with HG V.1.1stable527. I used the same file and the installation system, but in the RPI2, I encountered the same problem as @Petediscrete.
I tried to follow the instructions, but in the RPI2, could not display the field to change the port, but only the precompiled IP address field with the word “NotUsed”.
Rob.
Unfortunately no, you need a compatible device to discover virtual devices exposed from HG.
Quick googling didn’t answer the question. You can be the first to try this device and then share the results with the community. At least you’ll be able to use it as a regular Alexa device at home or in a car 
It’s quite strange. Could you try and reinstall the HGEB interface using this file https://github.com/davidwallis3101/HomegenieEchoBridge/releases/download/HomegenieEchoBridge-v1.0.22/MIG-EchoBridge.zip?
@alzy, @Petediscrete,
Really strange.
I can dim and turn lights on/off without any problem.
Could you look in logs for commands sent by Alexa?
This is an example from my HG logs for the command “Alexa, turn off Hall lights”:
2019-02-03 20:45:51.7663 Info LightsController PUT called. Updating light with idc0377c37-2499-4df7-9493-52a02cf9ad35]...
2019-02-03 20:45:51.7663 Info Finding device with id [c0377c37-2499-4df7-9493-52a02cf9ad35]...
2019-02-03 20:45:51.7663 Info Found device named [Hall lights] with id [c0377c37-2499-4df7-9493-52a02cf9ad35].
2019-02-03 20:45:51.7663 Info Alexa request: {"on": false}
2019-02-03 20:45:51.7663 Info Replacing IntensityValue for request "http://10.0.1.10:8090/api/HomeAutomation.ZWave/3/Control.Level/${intensity.percent}"
2019-02-03 20:45:51.7663 Info Request contained [${intensity.percent}] percent value. Scaling and Replacing with intensity [0].
2019-02-03 20:45:51.7736 Info Replacing IntensityValue for request ""
2019-02-03 20:45:51.7736 Info Empty request. No intensity value to replace.
2019-02-03 20:45:51.7736 Info Performing HTTPRequest URL:[http://10.0.1.10:8090/api/HomeAutomation.ZWave/3/Control.Level/0], Method: [], ContentType: [], Body: []
2019-02-03 20:45:51.7736 Info WebServiceGateway 10.0.1.10 HTTP GET 200 /api/HomeAutomation.ZWave/3/Control.Level/0 [OPEN]
2019-02-03 20:45:51.7841 Debug ZWaveMessage (RawData=01-0A-00-13-03-03-26-01-00-05-11-D5)
2019-02-03 20:45:51.7841 Debug ZWaveMessage (Direction=Outbound, Header=SOF, NodeId=3, Type=Request, Function=SendData, CommandClass=SwitchMultilevel, CallbackId=17, CallbackStatus=NotSet)
2019-02-03 20:45:51.7841 Info HomeAutomation.ZWave 3 ZWave Node Status.Level 0
2019-02-03 20:45:51.8077 Info WebServiceGateway 10.0.1.10 HTTP GET 200 /api/HomeAutomation.ZWave/3/Control.Level/0 [CLOSED AFTER 0.026 seconds]
2019-02-03 20:45:51.8182 Info HTTPRequest returned with StatusCode [OK] and ReasonPhrase [OK],
2019-02-03 20:45:51.8182 Info LightsController PUT: Successfully updated state of device via HTTP request.
2019-02-03 20:45:52.0469 Info LightsController called (// GET api/{userId}/lights/{id}) Retrieving light with id[c0377c37-2499-4df7-9493-52a02cf9ad35]...
2019-02-03 20:45:52.0469 Info Finding device with id [c0377c37-2499-4df7-9493-52a02cf9ad35]...
2019-02-03 20:45:52.0469 Info Found device named [Hall lights] with id [c0377c37-2499-4df7-9493-52a02cf9ad35].
2019-02-03 20:45:52.0469 Info LightsController GET: Returned DeviceResponse for device named[Hall lights], with id [c0377c37-2499-4df7-9493-52a02cf9ad35]
2019-02-03 20:45:52.0469 Info Creating a device response object with name[Hall lights], id [c0377c37-2499-4df7-9493-52a02cf9ad35].
Also right now HG-EB interface uses dim URL for devices of type Dimmer, and on/off URL for Switches.
Here is log for: Alexa Desk Lamp on
Alexa desk Lamp Off
Hope I captured what you need!
logs
2019-02-03 14:43:15.8282 Info SSDP Discovery Packet detected.
2019-02-03 14:43:15.8287 Debug Sending SSDP setup information to 192.168.1.9:62206
2019-02-03 14:43:16.3132 Debug 55-00
2019-02-03 14:43:16.3142 Debug Command succesfull
2019-02-03 14:43:16.3169 Info HomeAutomation.X10 B16 - Status.Level 0.77
2019-02-03 14:43:16.4446 Info WebServiceGateway 192.168.1.8 HTTP GET 200 /api/HomeAutomation.X10/B16/Control.Level/78 [CLOSED AFTER 3.767 seconds]
2019-02-03 14:43:16.4461 Info HTTPRequest returned with StatusCode [OK] and ReasonPhrase [OK],
2019-02-03 14:43:16.4469 Info LightsController PUT: Successfully updated state of device via HTTP request.
2019-02-03 14:43:16.5669 Info LightsController called (// GET api/{userId}/lights/{id}) Retrieving light with id[7fad71c9-aea6-4513-b712-f4c5cc726b4d]...
2019-02-03 14:43:16.5669 Info Finding device with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d]...
2019-02-03 14:43:16.5678 Info Found device named [Desk Lamp] with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d].
2019-02-03 14:43:16.5678 Info LightsController GET: Returned DeviceResponse for device named[Desk Lamp], with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d]
2019-02-03 14:43:16.5678 Info Creating a device response object with name[Desk Lamp], id [7fad71c9-aea6-4513-b712-f4c5cc726b4d].
2019-02-03 14:43:18.7033 Info WebServiceGateway 192.168.1.152 HTTP GET 200 /api/HomeAutomation.HomeGenie/Config/Interfaces.List/ [OPEN]
2019-02-03 14:43:18.7293 Info WebServiceGateway 192.168.1.152 HTTP GET 200 /api/HomeAutomation.HomeGenie/Config/Interfaces.List/ [CLOSED AFTER 0.026 seconds]
2019-02-03 14:43:21.0688 Info LightsController PUT called. Updating light with id7fad71c9-aea6-4513-b712-f4c5cc726b4d]...
2019-02-03 14:43:21.0706 Info Finding device with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d]...
2019-02-03 14:43:21.0727 Info Found device named [Desk Lamp] with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d].
2019-02-03 14:43:21.0782 Info Alexa request: {"on": false}
2019-02-03 14:43:21.0806 Info Replacing IntensityValue for request "http://192.168.1.8:80/api/HomeAutomation.X10/B16/Control.Level/${intensity.percent}"
2019-02-03 14:43:21.0826 Info Request contained [${intensity.percent}] percent value. Scaling and Replacing with intensity [0].
2019-02-03 14:43:21.0845 Info Replacing IntensityValue for request ""
2019-02-03 14:43:21.0861 Info Empty request. No intensity value to replace.
2019-02-03 14:43:21.0877 Info Performing HTTPRequest URL:[http://192.168.1.8:80/api/HomeAutomation.X10/B16/Control.Level/0], Method: [], ContentType: [], Body: []
2019-02-03 14:43:21.1048 Info WebServiceGateway 192.168.1.8 HTTP GET 200 /api/HomeAutomation.X10/B16/Control.Level/0 [OPEN]
2019-02-03 14:43:21.1106 Debug 04-EC
2019-02-03 14:43:21.1200 Debug F0-00
2019-02-03 14:43:21.1210 Debug Received checksum F0-00, expected F0
2019-02-03 14:43:21.1210 Debug 00
2019-02-03 14:43:21.5532 Debug 55-00
2019-02-03 14:43:21.5538 Debug Command succesfull
2019-02-03 14:43:21.5555 Debug 86-E4
2019-02-03 14:43:21.5698 Debug 6A-00
2019-02-03 14:43:21.5698 Debug Received checksum 6A-00, expected 6A
2019-02-03 14:43:21.5707 Debug 00
2019-02-03 14:43:24.5691 Debug 55-00
2019-02-03 14:43:24.5700 Debug Command succesfull
2019-02-03 14:43:24.5729 Info HomeAutomation.X10 B16 - Status.Level 0.04
2019-02-03 14:43:24.7234 Info WebServiceGateway 192.168.1.8 HTTP GET 200 /api/HomeAutomation.X10/B16/Control.Level/0 [CLOSED AFTER 3.619 seconds]
2019-02-03 14:43:24.7252 Info HTTPRequest returned with StatusCode [OK] and ReasonPhrase [OK],
2019-02-03 14:43:24.7260 Info LightsController PUT: Successfully updated state of device via HTTP request.
2019-02-03 14:43:24.8178 Info LightsController called (// GET api/{userId}/lights/{id}) Retrieving light with id[7fad71c9-aea6-4513-b712-f4c5cc726b4d]...
2019-02-03 14:43:24.8178 Info Finding device with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d]...
2019-02-03 14:43:24.8186 Info Found device named [Desk Lamp] with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d].
2019-02-03 14:43:24.8186 Info LightsController GET: Returned DeviceResponse for device named[Desk Lamp], with id [7fad71c9-aea6-4513-b712-f4c5cc726b4d]
2019-02-03 14:43:24.8186 Info Creating a device response object with name[Desk Lamp], id [7fad71c9-aea6-4513-b712-f4c5cc726b4d].
2019-02-03 14:43:25.8361 Info SSDP Discovery Packet detected.
2019-02-03 14:43:25.8368 Debug Sending SSDP setup information to 192.168.1.9:62206
2019-02-03 14:43:27.5120 Info SSDP Discovery Packet detected.
2019-02-03 14:43:27.5128 Debug Sending SSDP setup information to 192.168.1.9:63931
2019-02-03 14:43:27.5353 Info SSDP Discovery Packet detected.
2019-02-03 14:43:27.5359 Debug Sending SSDP setup information to 192.168.1.9:63932
2019-02-03 14:43:27.6468 Info SSDP Discovery Packet detected.
2019-02-03 14:43:27.6468 Debug Sending SSDP setup information to 192.168.1.9:63931
2019-02-03 14:43:27.6735 Info SSDP Discovery Packet detected.
2019-02-03 14:43:27.6741 Debug Sending SSDP setup information to 192.168.1.9:63932
2019-02-03 14:43:27.7561 Info SSDP Discovery Packet detected.
2019-02-03 14:43:27.7568 Debug Sending SSDP setup information to 192.168.1.9:63931
2019-02-03 14:43:27.7835 Info SSDP Discovery Packet detected.
2019-02-03 14:43:27.7841 Debug Sending SSDP setup information to 192.168.1.9:63932
2019-02-03 14:43:28.7027 Info WebServiceGateway 192.168.1.152 HTTP GET 200 /api/HomeAutomation.HomeGenie/Config/Interfaces.List/ [OPEN]
2019-02-03 14:43:28.7119 Info WebServiceGateway 192.168.1.152 HTTP GET 200 /api/HomeAutomation.HomeGenie/Config/Interfaces.List/ [CLOSED AFTER 0.009 seconds]
2019-02-03 14:43:31.9005 Debug 5A-00
2019-02-03 14:43:31.9028 Debug C3
2019-02-03 14:43:31.9276 Debug 5A-03-02-AA-A2
@Bounz, I just ordered Echo Input from Amazon. Tuesday, when I receive it, I will immediately inform you if it works.
About the port field error, I’ll try immediately to reinstall HB, but I think it’s the same file I used for the installations I’ve already done some days ago on RPI2 and RPI3…
@Bounz quote=“alzy, post:124, topic:63”]
HTTPRequest URL:[http://192.168.1.8:80/api/HomeAutomation.X10/B16/Control.Level/0],
[/quote]
Ok I understand the formula intensity 255 / percent 100 to give a base line Dim if I’m correct here. Now the HTTP request Control.Level/0 is requesting the device to be dimmed to 0 not turned off. Surely the HTTP request should have been Control.Off
The MIG requests would be Control.On for on, Control.Off for off and Control.Level/x where x is a number between 1 and 99. Surely 100 is On and 0 is off.
Is this logic following correctly.
When I played with my programs and Ha-bridge (simular code) dim 100% was Off dim 0 did nothing for X10. Other protocols didnt follow the same logic probably because x10 has both dim & brighten commands Also a dim 100% didnt truely turn off a x10 device so once dimmed to 100 the controler still seen the device as on.
My testing confirms that level 0 is not OFF. The Alexa command for off dims light to where it appears to be off, but testing with an incandescent bulb showed that hours after Alexa dimmed lamp to zero the bulb was still warm. An off command needs to be sent , not a level/0
We could have a problem here using X10. I’m looking at the MIG commands x10 v ZWave. @Bounz is testing on ZWave as you can see from his logs.
@Bounz could you compare MIG commands for ZWave and X10 to see any possible issues. Maybe that’s why David didn’t include the option for dimming in the HGEB in the first place.
Sorry - I was sunning myself in mauritius… Feel free to approve your own pull requests 
I trust you!
I didnt include the option for Dim as I didnt have any devices that support dimming!
@David_Wallis Strange that two users who deploy X10 are suffering similar symptoms while @Bounz who is using ZWave reports no problems.
Your v21 works perfectly on X10
Not sure if you’ve seen the flurry of activity from Gene in your absence. I think he has asked if you could include HGEB in the packages repo.
Well, looks like we should call Control.Off whenever Alexa’s request doesn’t contain bri field, despite is it a dimmable module or not.
So the Control.Level/x command request should read Control.Off as its is in v21. How did you refactor the code in v22 that caused this strange behaviour.
@Tuicemen, @Petediscrete, @alzy
Merged the fix, please try the newest version: https://github.com/davidwallis3101/HomegenieEchoBridge/releases
Will do. I’ll let you know the outcome.
@Bounz everything working as expected with v23. Lights now turning on and off and will Dim to level requested.
Fast work @Bounz. Bit like the old days!!!
Thanks again.
@Bounz I don’t currently utilize dimming so I can’t test that but the others seem to have it working now.
Thanks for digging into it.
Looks like dimming is working now! Thanks for the help!