pgattu

The following solved the issue for me. SSL Error 'ee key too small' I've had several linux users run into the error 'ee key too small' when trying to start Polyglot. sudo nano /etc/ssl/openssl.cnf Change the line: CipherString = DEFAULT@SECLEVEL=2 to CipherString = DEFAULT@SECLEVEL=1

I upgraded Polyglot from 2.2.3 to 2.2.11 via the Polyglot user interface since it prompted me to upgrade in the user interface. Polyglot is installed on a Raspberry Pi. I see the following messages in .polyglot/log/debug.log 4/11/2021, 16:58:25 [polyglot] debug: Created PID file: /home/pi/.polyglot/polyglot.pid 4/11/2021, 16:58:26 [polyglot] info: Starting Polyglot.... 4/11/2021, 16:58:26 [polyglot] info: Settings: Polyglot Version 2.2.11 4/11/2021, 16:58:26 [polyglot] info: Settings: Retrieved config from database 4/11/2021, 16:58:26 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 4/11/2021, 16:58:26 [polyglot] debug: TLS: Found Keys and Certificate data in database. Exporting to /home/pi/.polyglot/ssl/ 4/11/2021, 16:58:27 [polyglot] debug: Checking for DB Maintenence needs... At the command line when I start "./polyglot-v2-linux-armv7", I am seeing the following SSL error: 4/11/2021, 16:58:25 [polyglot] debug: Created PID file: /home/pi/.polyglot/polyglot.pid 4/11/2021, 16:58:26 [polyglot] info: Starting Polyglot.... 4/11/2021, 16:58:26 [polyglot] info: Settings: Polyglot Version 2.2.11 4/11/2021, 16:58:26 [polyglot] info: Settings: Retrieved config from database 4/11/2021, 16:58:26 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 4/11/2021, 16:58:26 [polyglot] debug: TLS: Found Keys and Certificate data in database. Exporting to /home/pi/.polyglot/ssl/ 4/11/2021, 16:58:27 [polyglot] debug: Checking for DB Maintenence needs... 4/11/2021, 16:58:27 [polyglot] debug: DB Version Found: 2 no maintenence necessary. 4/11/2021, 16:58:27 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883 4/11/2021, 16:58:27 [polyglot] error: Startup error. Shutting down: Error: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small 4/11/2021, 16:58:27 [polyglot] info: Polyglot shutdown complete with code: 1 Looks like the upgrade was unsuccessful, but it did not report any errors in the UI. The admin UI does not load. How can I fix the issue?

Hmmm... maybe I misunderstood the purpose of the forums. I thought it can be used to get a wider range of solutions for hardware/software issues. Anyway, I will take this issue offline and work with UDI tech support team.

I am attaching the error log for the past few days. ISY error log.txt

There are many devices setup for voice control. I am not a new user. I had the voice control setup for a few years now and it has been working until recently.

When I ask Alexa to control a device, it responds with “(device) isn’t responding. Please check its network connection and power supply.” Things I tried to resolve the issue, but haven’t worked: 1) reboot ISY 2) disable ISY skill and enable it Anyone had this issue and know how to resolve it?

I just added an Insteon Motion Sensor II to my home -- it is managed by ISY 994i. The motion sensor is supposed to turn on the lights when there is motion and after 30 seconds of timeout, it is supposed to turn off the lights in a room. The light turns on upon motion in the room. However, the light turns off in 30 seconds even though the room is occupied and there is motion. Insteon manual suggests to set the motion sensor in "Occupancy mode" using Insteon hub. I don't use Insteon hub. My ISY admin console does not have this setting for occupancy mode. How can I have the motion sensor keep the lights on when the room is occupied.

I just bought the iRobot Roomba 980. This has built-in wi-fi. Has anyone integrated ISY 994i with Roomba? If yes, how did you do it? I have the ISY 994i with Z-wave and IR Pro.

I just bought the Roomba 980. This has built-in wi-fi. Has anyone integrated ISY with Roomba? If yes, how did you do it? I have the ISY 994i with Z-wave and IR Pro.