Panda88

i see one getState (poll), which does not seem to generate a change in ST an does not send DON I see one .Report (actual keypress around 9:20 - it sets ST to 1 and sends DON That is all I can see in the log (by simple searching) - If you did not press the remote @ 9:20 I do not know why it is sending a keypress "event": "SmartRemoter.Report", "time": 1782048005629, "msgid": "1782048005628", "data": { "event": { "keyMask": 1, "type": "Press" }, "battery": 3, "version": "1404", "devTemperature": 13, "beep": false, "loraP2PHash": 0, "loraInfo": { "devNetType": "A", "signal": 0, "gatewayId": "", "gateways": 1 } }, "deviceId": "d88b4c01000e0a19"

Do you have an actual keypress in the log? I need a little more time to analyze the log - it seems the device is sending data but time not updating (which I do not check for), but I need a little more time For 2 You can specify what even/control a short press, and long press sends for each button in the button sub node. E.g. Short press send DON and Long press sends DFOF fast off) - there are 4 options to select for each button or an option to toggle DON/DOF of DFON/DFOF for each press. You can then control on those events - note if you have the on/off remote you cannot only specify an event for the push (as it does not determine long or short press) e.g. program for long press on key 3 s FOB1 Key3Long - [ID 0093][Parent 000E] If 'SY Fob1 / SY Fob1 key3' is switched Off Then Set 's Indoor Light / s MediaRoom / s Mediaroom Front' Off Else - No Actions - (To add one, press 'Action')

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)

Try 0.6.17 - just released - I am travelling so cannot test, but latest API supposedly fixes the issue Let me know

Just waiting for an official release

I need a log with debug enabled to identify the issue - you can PM it to me

i’ll take a look. I confirmed - there is an issue with the API changing I hope a workaround will be available soon, and I'll update the node

i know there are some issues with udMobile that is supposed to be fixed with next release. it may be related to that. if AC works with the same devices i believe it is udMobile related

Could there be someone around having another hub - YoLink devices will work with any hub it sees - not only the ones registered to you. but they need a connection to show data (unless you use the LocalHub) Did you try to sync UDmobile? It does sound a little like an issue on your side, but cannot say for sure

Can you define what the different APPs you mention are - is it UDmobile, The AC, the new eISY or ? I assume the YoLink app is the one from YoLink/YoSmart on your phone ? Sometimes you need to reboot/restart the eISY/Polisy for things to fully deploy (never found the pattern)

Can you enable debug in the PG3x console - restart the node server wait 5-10 min and then download the log and send it to me - I can see if there are errors during initilization - It sounds to me like the yolink node is not installed correctly

OK - I have updated the leakSensor icon to be irrigation - I made the Water related devices irrigation as well Made the hubs GenericCtrl, made the remote controllers Output, made the doorsensors DoorLock, and made the soilSensor Weather If you do a reinstall it should overwrite the existing definitions - I did not rev the version number, as there are no code changes. Below is a list of what is available (incl the icon) - Let me know if others should be changed

I do not think anything has changed - The current and the old both use Input as the icon. The only thing I could think of using is irrigation (the options are above) - I can try to contact UDI to see if there are new icon definitions. It seems it is eisy picking the icon if it showed water drop - maybe you can try to contact UDI for their input as well - they often try to make things "smart"

1.5.58 is released - mostly fixes to the yolink Thermostat

Can you send me a log where you issue a control event - It is supposed to send DON DOF

As it is said - its core is a vibrationSensor so it is already supported Wish they made it for rat-traps as well

1.8.56 released Minor bug fixes. Water meter measure was off for some meters (correction factor) and old thermostat issue. Was trying to fix the UDmobile issue with labels not showing, but it is believed to be a known issue with current udx release, so hopefully it will get fixed with an upcoming release of this Does anyone have issues with scenes not triggering from sensors? One user has this issue, but I cannot reproduce it here. May be the same udx issue mentioned above (but less sure about this one)

You can easily have multiple hubs - You only need the local hub if you plan your system to operate without internet access (for mission critical operation). Not sure there is a big difference in speed I would say unless you need its benefits, I would not buy the localHub - if you think you have marginal coverage, you can always buy another "normal" hub

Most likely it is the schedules - yolink operated schedules are now separate child nodes (I did not look at log yet)

Can you send me another log with it working - it may help identify the issue

Working to get some help - Have other experienced this One temporary solution should be to use status (not control) of the motion sensor in a program to trigger your scenes - I assume that would work - from the log I can see status changing - adds a small delay but not significant

I have contacted UDI to see if they have any idea

There are 5 of your door sensors that do not register the DON/DOF (triggers for scenes or actions) - others do not have this issue - You can see what they are if you look in nodes in pg3 interface Line 5763: 2026-05-12 01:43:43.741 Command udi_interface.node ERROR node:runCmd: node 8b4c01000e752f command DOF not defined Line 5764: 2026-05-12 01:43:43.781 Command udi_interface.node ERROR node:runCmd: node 8b4c01000e735a command DOF not defined Line 7098: 2026-05-12 02:16:54.781 Command udi_interface.node ERROR node:runCmd: node 8b4c01000a41c7 command DOF not defined Line 7099: 2026-05-12 02:16:54.824 Command udi_interface.node ERROR node:runCmd: node 8b4c04000354c2 command DOF not defined Line 9269: 2026-05-12 02:40:37.239 Command udi_interface.node ERROR node:runCmd: node 8b4c0200013692 command DOF not defined Is there anything unique about them? It must be coming from PG3 as other door sensors are using the same code and work well - Is this related to the zwave devices not working - e.g. are these doorsensors paired with ZWave in scenes or similar?

Yes - I can see this in your log the node reports it does not know the trigger commands to scenes. I do not see this in other logs which is strange, Could you try an thing - try to back up system, delete the node , reinstall it and restore the backup I also need to look at linking - it seems to be needed for zigbee/zwave, but I have never needed to use it before - maybe something has changed

udimobile has stricter rules for the node definitions than AC. I need to find a bug somewhere - I do see it on my side as well (Not a big user of UDImobile so I did not check) Do you know how to run the java console and see if there an any warnings when you start AC. Also, did you check if there is an update to PG3 (from the AC)