Preview and Beta: Amazon Echo Control

Thank you again so very much @J-N-K for your help with repairing this binding once again!

I installed the updated .jar, cleaned my cache, restarted openHAB a few times, restarted my system. Everything seemed to be working - the “LastVoiceCommand” feature started working once again in the Beta binding and I was encouraged! I checked on the EchoControl “Smart Home Devices” and many of them were just showing as “NULL” so I then, perhaps stupidly, decided I might as well try the additional update step that was posted by ThomasOH in the socket error thread, and did seem to succeed in updating my gson-2.8.5.jar file.

However, now I’m getting strange results, both good and bad,

The logs show openHAB as online / the systemd status shows as “Active” which is a good sign. The most promising sign of all is that my Echo devices are showing as recognized in the log and more awesomely the Smart Home Devices / lights / groups are showing as “ONLINE” again, which is wonderful! I think everything may be fixed! However, updating the gson broke something and now I can’t access the web interface whatsoever. And while everything shows as “ONLINE” and defined and active in the log, none of my commands are registering. Trying to find more log information but not showing errors anywhere that I can find… Just totally unable to access openHAB in the browser now though.

I’ve reset cache and rebooted again, tried running through openHABian setup again, running the tweaks/improvements there, but still can’t make it work. It shows as online. Are there any other places I should look for error messages, or any other suggestions you have?

Edit: I finally had some errors start to show up. “sudo systemctl status openhab2” shows the following errors:

openhab2.service - openHAB 2 - empowering the smart home
   Loaded: loaded (/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/openhab2.service.d
           └─override.conf
   Active: activating (start-post) (Result: exit-code) since Sat 2020-06-20 13:58:16 CDT; 1min 40s ago
     Docs: https://www.openhab.org/docs/
           https://community.openhab.org
  Process: 4818 ExecStartPre=/bin/bash -c /usr/bin/find ${OPENHAB_CONF} -name "*.rules" -exec /usr/bin/rename.ul .rules .x {} \; (code=exited, status=0/SUCCESS)
  Process: 4834 ExecStart=/usr/share/openhab2/runtime/bin/karaf ${OPENHAB_STARTMODE} (code=exited, status=127)
 Main PID: 4834 (code=exited, status=127); Control PID: 4835 (sleep)
    Tasks: 1 (limit: 4290)
   Memory: 2.7M
   CGroup: /system.slice/openhab2.service
           └─4835 /bin/sleep 120

Jun 20 13:58:16 HomeServer systemd[1]: Stopped openHAB 2 - empowering the smart home.
Jun 20 13:58:16 HomeServer systemd[1]: Starting openHAB 2 - empowering the smart home...
Jun 20 13:58:16 HomeServer karaf[4834]: /usr/share/openhab2/runtime/bin/karaf: 247: [: Illegal number:
Jun 20 13:58:16 HomeServer karaf[4834]: /usr/share/openhab2/runtime/bin/karaf: 247: [: Illegal number:
Jun 20 13:58:16 HomeServer karaf[4834]: /usr/share/openhab2/runtime/bin/karaf: 95: [: Illegal number:
Jun 20 13:58:16 HomeServer karaf[4834]: /usr/share/openhab2/runtime/bin/karaf: 296: [: Illegal number:
Jun 20 13:58:16 HomeServer karaf[4834]: /usr/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory
Jun 20 13:58:16 HomeServer systemd[1]: openhab2.service: Main process exited, code=exited, status=127/n/a

Seems perhaps a Java issue? I can try reinstalling java via openHABian. When I used openHABian a moment ago in an attempt to repair everything, it asked me if I wanted to try the Beta (lol) JDK/java update and I selected yes. Maybe that’s causing this issue.