Panda88

1.8.60 is released - fixing ghost presses for SmartRemoter remote

can you send log of what you have so i can see what is happening

sounds good

I did release it as a beta of the production, but I can try again - maybe not change the name just released with same name ad production in beta

OK - I found a way to patch it - what is the easiest way to test - If I issue a version in the beta store of local, can you try to update to that and see if that works before I do a full release I added one in the best store yolinkLocalSR - should be able to install over the existing node Once you confirm the fix, I can make a full release

Sorry - I need Debug enabled :-(

Thanks - please push few before switcing - I think you need to restart the node for it to register as local device

Can you also make a log with a keypress - when on local hub - I do not have a remote to access (an not on local hub) - YoLink confirmed that the current firmware sends the last event (without the event time) on its heartbeat (4 hours), so I need to see if I can identify a different way to distinguish the heartbeat from a real event

yes it should be the case

On problem 1 I can see that it happens every 4 hours (exactly) - seems to indicate it is YoLink generated (assuming you do not have a poll on a 4-hour tick) - I really wonder if it is a YoLink issue with the local hub - It sends a report that the key is pressed - even if it is not - I have not seen this with my remote (which is not local yet) I'll contact then and ask - can you try to run it non-local and see if it still happens

i see one getState (poll), which does not seem to generate a change in ST an does not send DON I see one .Report (actual keypress around 9:20 - it sets ST to 1 and sends DON That is all I can see in the log (by simple searching) - If you did not press the remote @ 9:20 I do not know why it is sending a keypress "event": "SmartRemoter.Report", "time": 1782048005629, "msgid": "1782048005628", "data": { "event": { "keyMask": 1, "type": "Press" }, "battery": 3, "version": "1404", "devTemperature": 13, "beep": false, "loraP2PHash": 0, "loraInfo": { "devNetType": "A", "signal": 0, "gatewayId": "", "gateways": 1 } }, "deviceId": "d88b4c01000e0a19"

Do you have an actual keypress in the log? I need a little more time to analyze the log - it seems the device is sending data but time not updating (which I do not check for), but I need a little more time For 2 You can specify what even/control a short press, and long press sends for each button in the button sub node. E.g. Short press send DON and Long press sends DFOF fast off) - there are 4 options to select for each button or an option to toggle DON/DOF of DFON/DFOF for each press. You can then control on those events - note if you have the on/off remote you cannot only specify an event for the push (as it does not determine long or short press) e.g. program for long press on key 3 s FOB1 Key3Long - [ID 0093][Parent 000E] If 'SY Fob1 / SY Fob1 key3' is switched Off Then Set 's Indoor Light / s MediaRoom / s Mediaroom Front' Off Else - No Actions - (To add one, press 'Action')

Each node used to cover operation for both Celsius and Fahrenheit (selection by user at startup). However, there is a bug in the PG3x not supporting this correctly in some cases. Thus, I had to split each node that deals with temperature into two nodes (selected startup) - one operating in C and the other operating in F. I had to give them different names, thus the letter F added to the name for the F setting node (if user selected F as temp unit). Yolink operates internally in C, so it seemed most natural to change the F node's name - thus the added F to the name. The same is also the case for Liter vs Gallon in does measuring water volume (adding a G)

Try 0.6.17 - just released - I am travelling so cannot test, but latest API supposedly fixes the issue Let me know

Just waiting for an official release