I set up the Venstar CT thermostat and communications works fine using the Admin Console. After adding it to the Portal Alexa discovered it with no problem. The issue is that when I issue a command using Alexa it repeats the command like it had been executed but when I check the device on Alexa it says it is waiting for UDI. It is defined as a thermostat on the Portal with no other choice available. Any suggestions would be apricated.

I did delete and re-add it to the portal.

I rebooted the eisy.

Version 6.0.4

The falling is what I see after a command is issued via Alexa.

2026-01-31 18:20:37.406 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command

2026-01-31 18:20:37.406 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command

Edited Saturday at 11:22 PM1 day by garybixler

Also logged the following after a command to set mode to heat.

026-01-31 18:46:20.793 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message command

2026-01-31 18:46:20.793 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command

2026-01-31 18:46:20.793 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'c0a81e4b', 'cmd': 'CLIMD', 'value': '1', 'query': {}} from Polyglot

2026-01-31 18:46:20.793 Command udi_interface.node ERROR node:runCmd: node c0a81e4b command CLIMD not defined

@garybixler

there is an alexa skill that works great without UDI. Thats my MO but Venstar plugin for UDI control

I had used that prior to moving but this time I thought I would try to keep the communications local.