Jimbo.Automates Posted August 15, 2023 Posted August 15, 2023 I'm stumped... It's in your nodes list you sent me for sure <node flag="0" nodeDefId="e868e786c5_2"> <address>n002_e868e786c5_2</address> <name>Main Level</name> <family instance="2">10</family> <parent type="1">n002_e868e786c5</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>n002_e868e786c5</pnode> </node>
pjjameso Posted August 15, 2023 Author Posted August 15, 2023 Dont suppose the node definition is too long? Wonder if anyone else has come across this using ambient weather. Thanks again for taking a look at the issue.
Jimbo.Automates Posted August 15, 2023 Posted August 15, 2023 7 minutes ago, pjjameso said: Dont suppose the node definition is too long? Wonder if anyone else has come across this using ambient weather. Please send the notification, then download log package from notification NS and email it to me.
pjjameso Posted August 16, 2023 Author Posted August 16, 2023 Hi Jimbo, Im out of town for the next two weeks. I will send upon my return. 1
Jimbo.Automates Posted August 17, 2023 Posted August 17, 2023 FYI I tested a long node name like yours thru the notification node server and it worked fine. The $sys is parsed by the IoX before being passed to the NS so will likely need @Chris Jahn to look into it. Sent from my Pixel 6 Pro using Tapatalk
Recommended Posts