Panda88

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