Andy P Posted January 5 Posted January 5 Any guess on why some yolink devices are missing the name in the node info (xray and rest/status) and others are not. For example, this leak sensor: <properties> <property name="Sensor Temperature" uom="17" formatted="72°F" value="72" id="CLITEMP"/> <property name="" uom="25" formatted="Dry" value="0" id="GV0"/> <property name="" uom="25" formatted="High" value="4" id="GV1"/> <property name="" uom="25" formatted="DON/DOF" value="0" id="GV2"/> <property name="Connection State" uom="25" formatted="Online" value="0" id="GV20"/> <property name="Nodeserver Status" uom="25" formatted="Connected" value="1" id="ST"/> </properties> It is not a problem with the admin console because that has all the names right: This Temp Humidity sensor has all the names filled in: <properties> <property name="Battery Level" uom="25" formatted="High" value="4" id="BATLVL"/> <property name="Current Rel Humidity (%)" prec="1" uom="51" formatted="43.3%" value="433" id="CLIHUM"/> <property name="Sensor Temperature" prec="1" uom="17" formatted="73.2°F" value="732" id="CLITEMP"/> <property name="Low Temp Alarm" uom="25" formatted="Normal" value="0" id="GV1"/> <property name="Low Temp Limit" prec="1" uom="17" formatted="64.4°F" value="644" id="GV10"/> <property name="High Temp Limit" uom="17" formatted="95°F" value="95" id="GV11"/> <property name="Low Humidity Limit" uom="51" formatted="0%" value="0" id="GV12"/> <property name="High Humidity Limit" uom="51" formatted="100%" value="100" id="GV13"/> <property name="High Temp Alarm" uom="25" formatted="Normal" value="0" id="GV2"/> <property name="Connection State" uom="25" formatted="Online" value="0" id="GV20"/> <property name="Low Humidity Alarm" uom="25" formatted="Normal" value="0" id="GV4"/> <property name="High Humidity Alarm" uom="25" formatted="Normal" value="0" id="GV5"/> <property name="Battery Alarm" uom="25" formatted="Normal" value="0" id="GV7"/> <property name="Alarm triggered" uom="25" formatted="Normal" value="0" id="GV8"/> <property name="Command Setting" uom="25" formatted="DON/DOF" value="0" id="GV9"/> <property name="Nodeserver Status" uom="25" formatted="Connected" value="1" id="ST"/> </properties> I have the latest everything and restarted everything. Andy Quote
Panda88 Posted January 5 Posted January 5 i’ll try to see if can find something in the node def setup files. there may be something missing 1 Quote
Panda88 Posted January 6 Posted January 6 I found the difference - I use global naming for some of the common parameters - these do not seem to propagate to the REST - but works with AC. Not sure if global naming is supported but it works with AC Maybe ask UDI if it is a bug or if I cannot use global naming I'll fix it if global naming is not supported (but it is some extra work (and a lot of testing) - Quote
Andy P Posted January 8 Author Posted January 8 ok, thanks, I opened a ticket, will let you know. Quote
Panda88 Posted January 8 Posted January 8 i believe it is real. it is not the nls file is parsed. i am using global definition for some common nodes. it seems the rest does not pick this Quote
bmercier Posted January 8 Posted January 8 2 minutes ago, Panda88 said: i believe it is real. it is not the nls file is parsed. i am using global definition for some common nodes. it seems the rest does not pick this Yes I've seen that. But my question is - Were you able to reproduce the problem? Quote
Andy P Posted January 8 Author Posted January 8 This was the response I received from the ticket: Chris Jahn replied 3 hours ago Hi Andy, We are in the process of fixing and enhancing the NLS capabilities for node servers. Problems like this are fixed in the new code. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.