My downstream programming broke and I found the reason is that the device names now have a 'F' after their name, like this - used to be yomotionsens and now it is yomotionsensF for some reason?

<node flag="128" nodeDefId="yomotionsensF">

<address>n008_8b4c020013c921</address>

<name>Motion Kitchen</name>

<family instance="8">10</family>

<hint>0.0.0.0</hint>

<parent type="3">32793</parent>

<type>0.0.0.0</type>

<enabled>true</enabled>

<deviceClass>0</deviceClass>

<wattage>0</wattage>

<dcPeriod>0</dcPeriod>

<startDelay>0</startDelay>

<endDelay>0</endDelay>

<pnode>n008_8b4c020013c921</pnode>

</node>

Also true for <node flag="128" nodeDefId="yovibrasensF"> and <node flag="128" nodeDefId="yoleaksensF"> and <node flag="128" nodeDefId="yothsensF">

But not for <node flag="128" nodeDefId="yodoorsens">

It is not just in the admin console, it is also in the polyglot console

Node Name 3	Address	NodeDef	Primary Node	Hint	Enabled	Is Primary	Delete
Fan HVAC 1	8b4c0100097447	yovibrasensF	8b4c0100097447	0x00000000	true	true

Each node used to cover operation for both Celsius and Fahrenheit (selection by user at startup). However, there is a bug in the PG3x not supporting this correctly in some cases. Thus, I had to split each node that deals with temperature into two nodes (selected startup) - one operating in C and the other operating in F. I had to give them different names, thus the letter F added to the name for the F setting node (if user selected F as temp unit). Yolink operates internally in C, so it seemed most natural to change the F node's name - thus the added F to the name.

The same is also the case for Liter vs Gallon in does measuring water volume (adding a G)

OK< thanks, I adjusted the code to strip off the F and everything is working again!

Appreciate the response. Thanks, Andy