Panda88

I think I found the bug - try .1.6.9 - just released

@Javi Is there any way to figure out what Family 10 and Instance 60 refers to? I guess the node (family) is in slot 10 but how do I know what Instance is - It would make debugging easier

OK - back to testing again

Can you enable debug in the log and do a few actions and PM me the log - I can take a look It does appear something has changed in 6.0 with how AC works with temperatures - I am still battling this - I do see the same issue I think it is related to having multiple definitions for editors - I have one for unknown and one for actual data - I believe there are some tickets already filed In general, I recommend using the alarms in yolink sensors, but getting the status should work as well

Not all yolink devices support local connection - you need to look at their specs There is no inherent 10 text messages limit - I think I just defaulted it to 10 during initialization

A comment on battery life - I do not think the alarms use significantly more battery - the measurement happens anyway inside the sensor and it is the sensor that decides to send data - My understanding the "schedule" of the temp sensor depends on rate of change and a window (no update if temp remains inside this window), and if nothing changes, it will update once per X hours, The wireless communication (sending data) is where the power is spent Note for pool sensor, yolink has a floating pool temp sensor - The first one I had leaked so they replaced it - 2nd one has been good this far

I am not sure with the sensors - you can get their value in the alexa app - not sure if it can be spoken (never tried) For the UDI integration you can implement home automation around the sensors - you can check the values with if-then, or you can use the build in alarms in Yolink to trigger (preferred due to faster reaction) to trigger something) - it is much like the existing insteon devices. The speaker hub allows up to 10 predefined (specified during setup of node) sentences to be played (in programs) There is a list of Yolink devices supported but not a list of what they individually do - YoLink has more devices types than what insteon supports (most are supported in the node) - In general they work similar (but I feel they are more reliable than Insteon as long as internet is up - localHub version enables support without internet access) One exception is for dimmer scenes - I made an attempt but the control is too different between Insteon and YoLink to make it identical (it is the same with other devices like Zwave etc) - naturally you can program dimmer levels etc, but scene operations are not perfect

I believe I finally found the issue - I no longer see it on my side after sync to UDmobile

YoLink create their own Alexa components The plugin creates the devices like other existing device - you can give the trial a try - Note, there is a Yolink (clould only) and a YolinkLocal ( that requires the localHUb and is a little more complicated to setup) nodeservers - If you plan to move to the local hub later it may make sense to get/try the local version (there is unfortunately no way to upgrade later)

Is there a way to find the line or what nodedef that is having the issue - this particular node server has a lot of nodedefs I did look, but have not identified where it is missing I have one nodedef without ST - could that cause it?

it is a new purchase i believe it is safer to use a new slot but you coul try and back anf the restore after installing the new node Others have more experinse here

I am still looking for the ST issue - I have not identified where it happens and there is not much in the error from UDmobile -I'll keep looking LocalHub requires yoLinkLocal - it is a superset of the original Yolink node (doing both local cloud) - I did not find a way to add an upgrade to existing users

I pushed a simple fix - I believe for the ST and SME error is UDM - If you reinstall it should pick it up - Note, it is not a new version - just typos in a text file

I have not released the fix for this yet - fighting another issue - and I combined the fix with this thinking it would be an easy fix :-( - not easy to separate it now but I am getting closer to fixing it

😀

I think I have to bite the bullet and change the node to use asyncio - the API version I use is too far behind. It will be an effort but I'll start look at it after I finish my yolink update

It seems something has changed - breaking the existing log in I'll take a look to see if it can easily be fixed but need to understand the changes needed first - they are changing to a new authentication scheme it seems The latest underlying API uses asyncIO which is a big change to the code, so it may take some time I need to finish my YoLink update first

I think there is a bug - somehow the unit is not changed even when I specify it - I will have a fix in the next release - it is something in the updated console program (my guess) that requires a different handling than before - there is also an issue with F and C they way I have handled in the past Are you really having temperatures down to -40f - I have that as a minimum for the temperature - do I need to support lower than -40 - Not sure the sensor works that low Yes - the outlet seems to be offline - press the set button -it usually fixes it

I can see a lot of Errors - it is a device being offline - maybe try to press the SET button Nothing else obvious - I believe the issue relates to the console code where something has changed - I doubt we can get them to fix it as they are working on a new version

What version are you using? Can you send me a log with debug enabled - I looked in the code, and see no reason it would not work The logic is really not in the node (it presets both values being possible) - it is interface not accepting it (I believe) - there should be no node action when creating the program. Do you see unknown as an option in the drop down?

Can you send me a log with debug enabled and then restart the system I have no issues last week when split my system in two - remember do not restart system after you update the F2A code - you save and wait

I think I found a solution - I can create two nodes one for F and one for C and select them dynamically The only issues is the water sensors that have the same issue but besides temperature they have water volume (4 units) so it creates 8 nodes I'll try to get it done in next release, but you will need to fix your code then

I do not believe it works - it is internal to the console - it does not convert - only show the unit of the number provided My only solution would be to overwrite node definitions - not select between the units as I do now It has not been an issue for be as I work in C

I think the only way is to make two different node definitions - it may be possible, and I can take a quick look to replace one on the fly - if so it is an option - I will not start developing two sets of nodes for each device

I agree it is confusing - I actually think it is a bug in the console - I use a special method to specify temperature - I specify an option for F and an option for C (and an option for unknown as text)- otherwise I would need to generate 2 versions of any node that has different unit support (and code for each of them) The unit defaults to C (as this is what YoLink uses as default) and is changed (forced) to F whenever data is accessed - Console knows both exists and I believe in this case believe it selects the default - It may be there is something I can do to fix this (besides having one C variable and one F variable in the node), but I do not know how to.