Just set up my Yolink plugin (latest version) with UAID, secret key. I see 9 nodes (flowsmart, temp sensor, water sensors x 5, hub, setup) in the dashboard/details, but in the AC, I only see Yolink hub (connected, online) and Yolink setup (node server online, ready). None of the data in the flowsmart, temp sensor, water sensors show up in the AC. Attached is log.

YoLink_2-7-2026_91728_AM.zip

Can you try to include a restart in the log file - just restart with debug enabled

I can see some errors, but not sure what causes them - it is like data is not reported correctly

Sometimes PG3 has an issue and need to be restarted - I think it relates to both solutions uses MQTT (but just guessing)

Thanks. Here is a new log after restart (waited about 5 minutes). Do I need the MQTT plugin?

YoLink_2-7-2026_122029_PM.zip

Interesting. After the restart (one of several over the past day), I now see the flowsmart as a separate node in the AC, not under the yolk hub.

all nodes are separate. hub is just a node

Are you sure it is not working after restart = no ERRORs reported - the should show as individual nodes

I see a leakSensor a temperature sensor and the water controller (and a hub) - They all report data

There is still an issue with the leak sensor Ibelieve - Yolink updated the API so some data is reported differently (basic leak detection should still work) - I am working on an update for the node and it will get fixed with that release (it is a bigger update as I am changing the internal structure of the data - to allow easier changes when Yolink change the reported data)

Yes, after the restart, the water controller, temp sensor and i leak sensor (out of 5) are showing as individual nodes.

@SHM have you restarted the admin console? Also, make sure that you're only accessing PG3 via the eisy_ui portion now. There's been mention from others that UD is suggesting only to access PG3 via eisy_ui interface because of how the licenses and ISY connections are being made. It's always been suggested that anytime you do something in PG3 to have the java admin console closed and when you're done changing things in PG3 to log out and then re-launch the java admin console. Since admin console only reloads or refreshes new nodes when it first runs. Anything you might have added if you had admin console open wouldn't appear there until that was restarted.

Interesting. That explains it. On my last log harvest with restart, I had opened the plugin after launching only PG3.

So going forward, I should only access plugins from the eisy-ui interface?