Panda88

Just released 0.6.5 It fixes the issue on my side You may need to refresh the node store for it to show up - it takes a while to propagate on its own

As it was said, they are the same. If you write new programs I would use the one WITHOUT legacy as some time in the future if we run of variables (there are limited variables we can use in a node server) I would sacrifice the legacy for new functionality - Note, this is not very likely to happen (there are still a lot available), but just in case

Triggering is fast in my exeriense - Note, you can trigger on both on and off and the node includes a time stamp in sec, so you can calculate the time it was on and off. I believe the trigger (message generated when a trigger occurs) will include a current power/energy draw report (causing the trigger) - I need to check, but the other devices do this

Just checked - Amazon/Blink has changed the authentication method again - need to figure out how it is done now Don't restart the node until a fix is in place

also note there is a new indoor high power switch that if i remember correct also supports power. i have it but have checked it yet.

currently it is supported. i could add a 24 hour or 1 hour average if that makes sense it reports current power and energy

Can you send (PM) me the full log including the PG3 long and install log?

I often find you need to run the upgrade more than once to everything installed correctly Did you reintall all nodes after the upgrade ? - I wonder if a library is missing - base_url is part of the library

I am working on it - - the motorized valves should be there already 5018 works, and I am working on 5009 and 5029 I am in the process of re-factoring the node, but I have them in the code - probably a few more weeks (Yolink is not consistent how these devices report data, so I have to refactor my code) Note, some of these devices (09,29) are a little difficult to handle, as they go to sleep without activity and then you cannot control them while they sleep (you need to press set, or there has to be activity ) - YoLink is working on a new FW that allow the app (API) to turn off the valve manually. Note, currently the devices need to be awake when you add them - I am working to improve this (part of the refactoring) Anyway, support will get there -

They are two different variables representing the same result so they are programmatically equivalent. I had to do this because people requested UDmobile to show motion in your case and UDmobile shows the ST variable (which for most nodes originally presented online) To make existing program run, I had to maintain the original variable (now named legacy) and then assign the same value to ST Online moved to a new variable in this case

I believe I updated both - 1.6.10 - if it does not show do a store refresh

Ok - I think we found the issue - minor bug in AC (and partially my fault) - Issue occurred when I moved key parameter to ST variable (to show status in UDmobile). I left the original value variable with the same name(to ensure existing programs would still work, but AC cannot handle two variable with same name in the same node - I updated the variable names so ST (shows in UDmobile) gets the original name, and I appended a (legacy) to the name of the original variable. It should not affect existing programs as it updates automatically, but I would suggest moving to the ST parameter (without legacy) when creating/editing/modifying programs Let me know if the issue is fixed in 1.6.10 - refresh store if it does not show yet

it is only when you create a program - correct?

Sure. Hopefully they can find something

Released 0.6.4 Uses the latest blinkpy (0.24.1) so features should be up to date It uses the new login credentials method. It is similar to old version, but it is no longer possible to save the 2FA code, so one will need to add new 2FA code every time node is started. I have tested for 24 hours and it seems token renews correctly Added a time stamp to cameras showing time for the latest poll of data Let me know if any issues occur Note, I have still not figured out how to automatically create the different networks automatically - one need to create them manually by copying the network names to configuration

files look ok - there is some issue with how 6.0 uses the inputs from PG3x - I have a ticket with udi, but no reply yet

OK - I have an updated Blink Node - what is the best way to test it I assume I can just make a new version, as the old ones do not work, but I could also release a version in the beta/non-production store - let me know There are some changes - it required 2FA key every time the node restarts - it is the new authentication from Blink I added a time stamp for latest update on cameras There is a longer delay than before - especially during start up - 10-15 sec or so before it moves along I have not been able to generate the network Names automatically under config - one will have to generate them manually by added a parameter for each network detected I tested it a little but there may still be bug, so let me know if you find issues

Do you know if this is the new HW revision - that is supposed to arrive end of the year ?

Can you send me (PM) a log with debug enabled and some key presses - I have the 3604 and is offers both long and short on each key - I also got the mine on/off and it seems to offer both long and short from each button

It provides a main node monitoring data as well as some control ( 'HONKHORN' : evHonkHorn, 'FLASHLIGHT' : evFlashLights, 'SENTRYMODE' : evSentryMode, 'DOORS' : evControlDoors, 'SUNROOF' : evControlSunroof, 'TRUNK' : evOpenTrunk, 'FRUNK' : evOpenFrunk, 'HOMELINK' : evHomelink, 'PLAYSOUND' : evPlaySound,and 2 sub-nodes - one to control and monitor climate 'WINDOWS' : evWindows, 'SUNROOF' : evSunroof, 'AUTOCON' : evAutoCondition, 'CABINTEMP' : evSetCabinTemp, 'DEFROST' : evDefrostMax, 'SEAT' :evSetSeatHeat, 'STEERINGW' : evSteeringWheelHeat, and one to control and monitor charging. 'CHARGEPORT' : evChargePort, 'CHARGECTRL' : evChargeControl, 'BATPERCENT' : evSetBatteryChargeLimit, 'CHARGEAMPS' : evSetCurrentChargeLimit,If you have a powerShare connection a node will be added allowing monitor and control of the power (mini power wall) ,'BACKUP_PCT' : setBackupPercent ,'OP_MODE' : setOperatingMode ,'GRID_MODE' : set_grid_mode ,'EV_CHRG_MODE' : set_EV_charge_reserve

Thanks - Still fighting some (what I believe is 6.0 related) bug on Yolink - I know what to do on the Blink server, just need to find the time

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