App is just receiving byte arrays filled with zeros, I had not found any examples of such behavior. When I’ll have more time - Ill prepare some debug builds with different connection options - maybe it can help.
Hi the latest beta version notification cannot working from the hardware side !
Please send logs, there were no changes in last builds except for some bugfixes
Hello Alex i have sent log files earlier this week. Were they helpful? is there more i can do to enable you to find the problem?
Since updating to 2.27.6 (latest Android beta), my device tiles have been arranged by alphabetic order. Is there any way I can change them back to the way they were?
See here… it was a fix from the previous chaotic ordering.
Ah, thanks @Gunner.
Do you know if the ordering is based on the name or template ID? It would be nice to be able to rearrange them without having “A - Lounge lights”, “B - Bedroom lights”
It is based on the devices’ names. So you can just rename devices. Maybe I’ll find another better way to sort out this issue.
Any chance you could allow us to rearrange the devices by moving them up/down on the device tiles settings tab?
There will be sorting options for Blynk2, not sure we will introduce them in current app.
I think it is the first time I see this “announcement”. Work “in progress”? Or just plans for future?
@BlynkAndroidDev, could you somehow provide me a link to the pre-LATEST (beta)version. I got a strong feeling latest version broke something within image widget. I’m not sure (I’m using it only since very recently) but it seems latest version reacts with a HUGE delay to :
blynk:setProperty(42, "urls", "http://192.168.1.131/snr/SNR-0001.png") blynk:virtualWrite(42, 1)
The above is called >4s after updated image is placed on server, the updated image IS accessible,yet the BLYNK delays its update in widget by few dozens of minutes (after some another run). I think it was ok before.
may be related to this:
Is the URL you are setting the same each time? If so, perhaps it is not flushing the cached image.
blynk:setProperty(42, "urls", "http://192.168.1.131/snr/someotherfile"); blynk:setProperty(42, "urls", "http://192.168.1.131/snr/SNR-0001.png");
Lets hope Blynk2 launches soon.
Yes, this workaround came into my mind, but I’d prefer a software fix.
I may try that with some nice “waiting” graphic and when new graphs are ready, refresh widgets again.
Is Blynk “1” bad?
Blynk “1” is awesome but there are several little things like this which are … frustrating…
Please send me the log, it could be possible that pin write is received before set property.
not sure blynk 2 will be free
Log has been sent. Slightly different syntax on last attempts though:
socket.sleep(4) blynk:setProperty(42, "url", 2, "http://192.168.1.131/snr/SNR-0001.png") blynk:setProperty(43, "url", 2, "http://192.168.1.131/snr/bitbin-0001.png") blynk:virtualWrite(42, 2) blynk:virtualWrite(43, 2)
The #1 image is chosen during “waiting” period,and it works.