JKlinefelter

Makes sense. I guess for now it can at least be managed on the user end by making sure you don’t have any duplicated channels. e.g. you can’t have a sensor on T&H#1 and a sensor on SM#1. If you have more than 8 sensors you will be out of luck but I can’t imagine many setups do. As for my setup, I only have four external sensors so if I can just get the IoX to recognize the soil moisture key soilhum1, I should be good for my intended application. See my separate post on missing keys.

I'm working on automating my garden watering schedule using a WS-5000 and a soil moisture sensor and the Soil Moisture key (SoilHum1) is not recognized by the node server. Here is the log output: Node 1 is the weather station main that has an online / offline key. Node 2 is the main sensor array (WS-5000), the nodeserver recognizes 18 keys. I believe the unrecognized "lastRain" key and the "eventrainin' keys belong here. Node 3 is the indoor temp and humidity sensor (WH32B). It appears to be recognizing all the keys. Node 4 is titled "one" and is the Soil Moisture sensor (WH31SM). The only key recognized is the battery. SoilHum1 is unrecognized and belongs here. This is the one I really need. Node 5 is titled "two" and is a temperature probe sensor (WH31P). It appears to be recognizing all the keys. Node 6 is titled "three" and is an outdoor temp and humidity sensor (WH31E). It appears to be recognizing all the keys. I'm not sure what the remaining unrecognized keys are but they probably belong in the main sensor array node. It would be really great if the SoilHum1 key could be recognized. I've loaded profiles, restarted the admin console, and restarted the node server multiple times without success. Thanks.

I'm troubleshooting a new WS-5000 and had a similar problem described here. I have a theory on what the problem is that may help resolve this issue in future updates. I'm not a python programmer so forgive me if I butcher the lingo. The WS-5000 (and presumably the WS-2000) adds sensors within different categories (T&H, soil moisture, etc.) In my case I have two T&H external sensors and one soil moisture sensor. The T&H sensors can be programmed to a channel, but the soil moisture sensors automatically get assigned a channel in the order they are detected by the panel. (See the attached screen shot of my Ambient panel). So my initial setup had T&H assigned to channel 1, T&H assigned to channel 2, and Soil Moisture assigned to channel 1 (in the soil moisture series of channels). The Ambient Polyglot recognized a node called "one" and it appeared in the Admin Console but it was dead... there was no data showing. When I moved the sensor on T&H channel 1 to T&H channel 3, I got data on all three of my sensors, similar to what EWhite reported. So it seems what is happening is the Ambient Polyglot is seeing two sensors on "channel 1" and getting confused at the Admin Console interface. I see from EWhite's log he has two soil moisture sensors. They will automatically get assigned to Soil Moisture channels 1 and 2. So if you have T&H sensors also assigned to T&H channels 1 and 2, then the Ambient Polyglot is seeing two channel 1's and two channel 2's and seems to be confused.

I have a new Serena roller shade and the Caseta node server isn't recognizing it as a supported device. Here is the error log: 2023-04-01 17:53:05,536 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: Unsupported device type: SerenaRollerShade 2023-04-01 17:53:05,536 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: To get support for this device added, please send the following to the developer: 2023-04-01 17:53:05,537 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: { "device_id": "2", "current_state": 0, "fan_speed": null, "tilt": null, "zone": "1", "name": "Family Room_Shades", "button_groups": null, "occupancy_sensors": null, "type": "SerenaRollerShade", "model": "SYRJ-S2A13-XX", "serial": 70463700