Panda88

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

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)