dantoronto Posted November 27, 2023 Share Posted November 27, 2023 sorry. I thought you sent me a note to move this to this topic. Yes, you solved my problem. Perfectly. Thanks Link to comment
Solution Jimbo.Automates Posted November 27, 2023 Solution Share Posted November 27, 2023 6 hours ago, dantoronto said: sorry. I thought you sent me a note to move this to this topic. Yes, you solved my problem. Perfectly. Thanks No worries. For others info the problem was solved in another thread. https://forum.universal-devices.com/topic/42457-elk-m1-with-eisy-and-alexa-voice-control/#comment-375488 Link to comment
dantoronto Posted November 28, 2023 Share Posted November 28, 2023 One last (I hope!!) question. Not sure if I misunderstood your instructions. In my ELK, you advised that under M1WEP Setup / TCP/IP Settings, I should enable non-secure port and set it to 2101. Which I had. And that in the configuration for the ELK Node, under host, you said to put in the IP address for my ELK with ":2101", e.g. 192.168.xx.yyy:2101". And this all now works!! My question is whether on the first page of my ELK account details, I have have for the "Port to use for connecting", I should/must have it set to the non secure port or can I have it set to the secure port. All the material I have read or seen has that setting as the secure port. Am I less secure? And will the connection work if that setting is the secure port? You had previously said: > Host: the IP Address for the ELK with 2101. 192.168.50.xx:2101 Please confirm with ElkRP2 that unsecure port is allowed and is set to 2101. That is correct. and yes, if someone is able to get onto your LAN they can connect to the unsecure port, but they still need a user code to arm/disarm. I could allow connecting via the secure port, but then would have to store the username/password in PG3 which does not yet have a secure way to store the data. Thanks much Link to comment
Recommended Posts