Panda88

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.

Can you PM me a log with Debug enabled?? - is there a space before the 5 in Local_client_ID I cut and paste to email and email it to my self I would remove the picture with your credentials - you can always PM me

I think I found the issue - at least my current version (internal) does not show this - I am working on another bug I want to fix at the same time - The above is more cosmetic - there should be no functional issues