-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing 2.11.0 #868
Comments
I don’t know if it is intentional in the alpha builds. But the check for updates and revert to stock are missing. |
no, it's a bug - fixed in alpha3 |
There is a problem with the Shelly 2.5 firmware. It is introduced between alpha1 and alpha2. I tested it with 3 different shelly, each with a different installed version. So I think the problem is the new firmware and not the old one. Observed things:
|
I'm also having the same behaviour from the script, i left the script running all night (while [[ 0 -eq 0 ]]; do python3 flash-shelly.py -m keep -y -i 3 -a --variant alpha; sleep 20; clear; done) and none of the 2.5 were updated. But all the 1PM are completely fine. |
I would like to see the output of that if poss, as it should have timed out. add Thx |
Looks like the crash is the script trying to update my 3d printer. Attachment the debug log and also the console output. Console output: admin@iMac tools % python3 flash-shelly.py -m keep -y -i 3 -a --variant alpha --log-file debug.log Host: http://shellydimmer-D3E51C.local Host: http://Bomba-Casa-Maquinas.local Host: http://Musica-Duplo.local Host: http://Luz-Casa-Maquinas.local Host: http://shellydimmer-D3EB09.local Host: http://Wc-cave.local Host: http://quarto-direita.local Host: http://Suite-Banheira.local flash-shelly version: 2.8.0 During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Devices found: 8 Upgradeable: 2 Flashed: 0 |
please try version 3.0 beta of the script #686 |
Now it crashes trying to update one 2.5 (i believe that this is due to what timoschilling was reporting on the firmware problem with 2.5). admin@iMac Downloads % python3 flash-shelly.py -m keep -y -i 3 -a --variant alpha --log-file debug.log Host: http://quarto-direita.local Host: http://Bomba-Casa-Maquinas.local Host: http://Luz-Casa-Maquinas.local Host: http://shellyplug-s-51D7C0.local Host: http://shellyem-C45BBE5FE4C8.local Host: http://Lavandaria.local Host: http://shellydimmer-D3E51C.local Host: http://Musica-Duplo.local flash-shelly version: 3.0.0 During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Devices found: 8 Upgradeable: 1 Flashed: 0 |
|
hm, sorry, i don't understand - alpha3 cannot update? |
@rojer it seem to going from 2.10.1 direct to alpha3, (I have not tried myself, getting rooms re-plastered here, everything upside down atm.) |
@rojer im not able to flash a 2.5 with 2.10.1/2.10.0/2.9.x to 2.11.0-alpha3. The upload via script, via curl and via UI didn’t work. Would work mean UI stops at 0% progress and curl/script getting a connection reset. |
ah, you're right. 2.5 firmware size has crossed the magic 716KB. 2.5 is the biggest of them and i did not happen to have one on hand for testing the alpha. |
i dropped rpc-service-ota and this freed up some space, so 2.5 should fit again. pushed alpha4, please give it a go. |
Hi! I have one question regarding 1 plus integration: does it uses Wi-Fi, Bluetooth or both to connect to a HomeKit hub (iPad, HomePod etc)? Because since it has a Bluetooth connection it might be handy to use it as a fallback only. Also regarding this, is it possible to completely disable Bluetooth module and use only Wi-Fi in the settings? This should save some power while also preventing collision interference when a lot of IoT devices are present. Thank you! |
Did I do something wrong when I try to do the firmware upgrade from my shelly 1 plus?
It says "Not Found"?! |
so, situation with bluetooth is kinda unfortunate. i tried it, and it works but it doesn;t work seamlessly with wifi. once a bluetooth accessory, always a bluetooth accessory. accrding to apple, having accessory available on both BLE and IP transports is not supported. so when wifi becomes available, hub still insists on using BT, which in practice is slower and less responsive. additionally, bridge mode is not available over bluetooth and we use "bridge" mode to expose multiple accessories. so, in short, at the moment BLE is not supported. it's not much of a problem since when setting up shelly-hk, it's already connected to wifi.
plus series cannot be upgraded this way, see instructions here. |
@rojer so basically the 1 plus with HomeKit has Bluetooth completely disable? It’s not an issue for me, actually. I’d rather have Bluetooth off and all on Wi-Fi to prevent network collisions than having a lot of Shelly’s using both Wi-Fi and Bluetooth. |
@miguelpruivo correct, currently bluetooth is not enabled in shelly-hk frmware. |
Hi all! |
based on wifi 1
try all usable APs (RSSI > -90) for wifi 1 first, from best to worst, then wifi 2.
nothing much. APs will be deduplicated.
this will be the case during initial setup. however, not after connection was established. |
Hello all, i've installed alpha4 on a shelly 1PM before setup it on HomeKit, and every time i click setup i receive a request timeout (the interesting bit is that it was discoverable in the home app but i didn't knew the code). This specific device is with RSSI -86 which could not help, but with 2.10.1 i manage to setup it perfectly. |
@bmpalmeida I noticed something similar, try do make a reset and retry then. |
pushed beta4. if everything goes well, this will be the last one. |
Updated a ShellyBulbDuo to the latest beta and it does not report correctly the power state or turns on/off. Tried rebooting it several times. Edit: Reverted to beta3 and all is ok now. |
For me everything works fine with beta4 version. I'm using for Garage Door opener. Thank you @rojer! |
Shelly UNI works fine so far with beta4 |
@hughfr4nc15 probably my bad, most likely broke |
@hughfr4nc15 actually, i was able to test the CCT controller in emulation (with 889f850) and it works fine, home app is in sync with web ui and transitions seem to work correctly. can you open |
@rojer: @hughfr4nc15 is right. you removed this line here: 13b1e2c#diff-2d3789d1c8b513abd98feaa6d455d9e2c5b68c1f372cb5933b571b5e3ad44b16L71 you added this in the white controller, 13b1e2c#diff-71ecb80d663c8bde307126569c514099165cb25ccd0e789b8729af858331bc67R33 but not in cct nor in rgbw code |
@kirbema thanks Mark! yes, you[re right, thanks! pushed beta5 with the fix, @hughfr4nc15 please update and confirm. |
@rojer I can confirm, the issue is gone on RGBW2 with update from beta4 to beta5 |
I have around 50 devices, 1PM, 2.5, rgbw2, and all of them are really stable with beta5, except one. I’ve tried wifi power saving mode 2 in all of them, and i don’t notice any difference in performance, except this one. I revert power save to disable, and looks like it is more stable, but i manage to catch the core dump which i sent via email to @rojer just an update. It crashes in a way that I need to power cycle it for having working again. Not even the physical buttons work. Seems only stable with power saving disable. |
@bmpalmeida i took a quick look at the dump - device ran out of memory, memory full of what looks like network traffic. it seems familiar, someone reported something like this before... |
@rojer @markirb I have tested identify on a Duo, Vintage and Color Bulb, all with the same effect: Identify via HomeKit setup didn't work, via RPC it works. Here is a log from a HomeKit setup identify request:
|
@timoschilling I only tested with RGBw2 via Eve. Can it be that the SetIdentifyCB is not called on Duo and ColorBulb? It is on vintage, so it should work there? |
@markirb I tested it again:
|
Failed means that there is no Callback registered. @rojer I see that these lines cannot work, as the accessory is created beforehand, and never registers the callback. But @timoschilling for me the Light flashes correctly on RGBW2. The callback seems to be there, otherwise it would also fail. |
Logs from the RGBW2 in RGB mode:
When I use
|
shelly_sys_led_btn.c is wrong. Ok so we know, same error as in Vintage and co: this only works for non-primariy accessories as in my case. |
see #1009 and mongoose-os-libs/homekit-adk#9 |
ok, thanks to @markirb we have identify for bulbs working. i pushed beta6 and very much hope this will be the last one. |
Will Plus 2PM be supported? |
not in this release |
I have tested the latest beta on my ColorBulb, Duo and Vintage and it works well! |
pushed 2.11.0. it's a biggie! |
What's new:
/ota?url=...
method.alpha5:
alpha6:
alpha7:
alpha8:
alpha9:
beta1:
beta2:
beta3:
beta4:
beta5:
beta6:
The text was updated successfully, but these errors were encountered: