garybixler

Setting the humidifier setpoint doesn't seem to work from the Admin Console. It can be set using Skyport and the change shows up on the Admin Console (GV1). Thanks.

Just wondering if anyone has been able to get the ThirdReality Zigbee Smart Outlets to work at monitoring power of the plugged in device. The on/off functions fine but no nodes for energy usage. Thanks

I did use the Alexa Venstar skill in the past but after I moved I thought I would try to keep access local and within the UD environment. The previous versions of the ISY skill as I remember didn't really support a thermostat. Skyport makes it very easy to configure the thermostats and remotely control them. The one setting on the thermostat that needs to be turned on is 'Local API" in settings.

I set up a Venstar thermostat on the eisy. All works fine. When I add that thermostat to the portal it is acknowledged by Alexa and added to the device list. The problem is that when I send an oral command to that device, like set mode heat the NS doesn't seem to understand what was received. Alexa shows waiting for UD. Also the current room temperature isn't received by Alexa. Shouldn't this work? Thanks. Log: 2026-02-02 15:10:30.282 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2026-02-02 15:10:30.283 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2026-02-02 15:10:30.282 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2026-02-02 15:10:30.283 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2026-02-02 15:10:30.283 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '86a3e7c1', 'cmd': 'CLIMD', 'value': '1', 'query': {}} from Polyglot 2026-02-02 15:10:30.283 Command udi_interface.node ERROR node:runCmd: node 86a3e7c1 command CLIMD not defined

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

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 command2026-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

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

Can this node server also control the humidity set point? Thanks

To start eisy-ui just type https://1.2.3.4

I had some flickering issue and found it to be that the Instron switch was adjacent to a dimmer in the switch box. Another solution may be to install these devices. https://www.insteon.com/collections/accessories/products/led-flicker-glow-eliminator

I have two Syncrolinks and they both don't always follow the Holdoff seconds set in their configuration. They may turn on or off instantly at any time. I'll probably correct this by using a program but was wondering if this may be an issue with the Syncrolink. Thanks

I keep getting this error when trying to 'Scan for Bluetooth devices'. Thanks V.6.0.4 Also V.6.0.3 New Text Document (3).txt

I did receive this response to 'does a Roku stick respond to query broadcasts?'. Just some info. I'll check to see if the broadcasts are making it from ethernet to the wi-fi network Thanks Yes, the Roku Streaming Stick (HD versions included) does respond to network query broadcasts using the Simple Service Discovery Protocol (SSDP). This protocol allows programs and devices on your local network (such as the official Roku mobile app or smart home systems) to automatically discover the Roku device and its IP address. Update. I have found it works fine when connected to the 5GHz Wi-Fi network.

I have a Roku ultra that has no problem being discovered by the Roku NS but I just received a Roku streaming stick HD but it can't be discovered by the NS. I see the broadcast being sent out but no response from the Roku stick. I do have the allow app to control the Roku enabled. Just wondering if there are issues with the streaming sticks. The ultra is on Ethernet while the stick is on Wi-Fi, but both are on the same network. Thanks

Thanks so much. Just ordered.