Skip to content
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.8.0 #498

Closed
rojer opened this issue Feb 14, 2021 · 60 comments
Closed

Testing 2.8.0 #498

rojer opened this issue Feb 14, 2021 · 60 comments

Comments

@rojer
Copy link
Contributor

rojer commented Feb 14, 2021

Starting the 2.8 release cycle.

What are we testing:

Firmware: http://rojer.me/files/shelly/2.8.0-alpha6/

This was referenced Feb 14, 2021
@rojer

This comment has been minimized.

@timoschilling

This comment has been minimized.

@danny1605
Copy link

Hello i have extensively tested the 2.8.0-alpha1 version with a shelly 1 HAP Service Type Valve. I couldn't find any errors. Can I leave the alpha version installed until the current version comes out? Many thanks again for the migration

@rojer
Copy link
Contributor Author

rojer commented Feb 14, 2021

thanks @danny1605 . leave it on the device, once 2.8.0 is released you will be able to update to it via regular update check.

@BlancoDeMallloca

This comment has been minimized.

@andyblac

This comment has been minimized.

@BlancoDeMallloca

This comment has been minimized.

@andyblac
Copy link
Collaborator

Valve support seems ok for generic and irrigation, but Faucet and Shower Head do not work on my Shelly1, i just get no response.

@BlancoDeMallloca
Copy link

BlancoDeMallloca commented Feb 16, 2021

Tested the doorbell mode in a test environment and seems to work fine. No issues discovered.

@emartife

This comment has been minimized.

@timoschilling

This comment has been minimized.

@emartife

This comment has been minimized.

@timoschilling

This comment has been minimized.

@DerKoller-eu

This comment has been minimized.

@timoschilling
Copy link
Collaborator

@DerKoller-eu sounds wrong, but is actual expected behaviour. Input Mode: Detached means that there is not "connection" between the input and the output of the shelly.

Hotfix: create a HomeKit automatisation which turns on your "Shelly-Doorbell" in HomeKit when the Doorbell is triggered.

For the longterm we can add a explicit mode for that.

@rojer
Copy link
Contributor Author

rojer commented Feb 23, 2021

pushed alpha2

@rojer

This comment has been minimized.

@rojer

This comment has been minimized.

@andyblac andyblac pinned this issue Feb 23, 2021
@lieberjott
Copy link

Quick question: Manual calibration for roller shutters (#449) won't be yet added?

@andyblac

This comment has been minimized.

@rojer
Copy link
Contributor Author

rojer commented Feb 23, 2021

correct. won't make it into 2.8 but will be in 2.9

@basroovers
Copy link

@DerKoller-eu sounds wrong, but is actual expected behaviour. Input Mode: Detached means that there is not "connection" between the input and the output of the shelly.

Hotfix: create a HomeKit automatisation which turns on your "Shelly-Doorbell" in HomeKit when the Doorbell is triggered.

For the longterm we can add a explicit mode for that.

I just tested the alpha3 version. Using an automation makes sense if you want something like a condition based on time of day (e.g. don't ring gong in the middle of the night). In order to get my gong sounding "properly" I needed to configure the auto off to a sub seconds delay.

@rojer
Copy link
Contributor Author

rojer commented Mar 6, 2021

pushed alpha4. fixed layout for roller shutter section, plus networking changes in the backend (reverted to LWIP 1.4, reportedly it's more stable)

@pivale
Copy link

pivale commented Mar 8, 2021

Lost http conectivity to most of my devices after alpha5. I can't access them by browser and update-script fails to connect.
I can ping them all though, so they are still alive and responsive.

Power cycling didn't help...

@andyblac
Copy link
Collaborator

andyblac commented Mar 8, 2021

Lost http conectivity to most of my devices after alpha5. I can't access them by browser and update-script fails to connect.
I can ping them all though, so they are still alive and responsive.

Power cycling didn't help...

and i bet homekit still works.

@danny1605
Copy link

the same problem, a connection via browser is no longer possible.

@andyblac
Copy link
Collaborator

andyblac commented Mar 8, 2021

can someone confirm something in alpha5, i think webui issues is linked with number of HAP connections, I can access webui, with no issues if HAP connections is 3 or less, as soon i hit 4 problems start, webui is hit and miss, the more HAP connections device has the worse it gets, over 5 and you loose total webui access.

@col-tom

This comment has been minimized.

@pivale
Copy link

pivale commented Mar 9, 2021

Lost http conectivity to most of my devices after alpha5. I can't access them by browser and update-script fails to connect.
I can ping them all though, so they are still alive and responsive.
Power cycling didn't help...

and i bet homekit still works.

Yep, only http server seems to be affected... Homekit is still working

@pivale
Copy link

pivale commented Mar 9, 2021

can someone confirm something in alpha5, i think webui issues is linked with number of HAP connections, I can access webui, with no issues if HAP connections is 3 or less, as soon i hit 4 problems start, webui is hit and miss, the more HAP connections device has the worse it gets, over 5 and you loose total webui access.

how can I help confirm that? currently all my shellys are unavailable (although working...)

@danny1605
Copy link

danny1605 commented Mar 9, 2021

i have the same problem too, after the update to alpha5.
Unbenannt

@andyblac
Copy link
Collaborator

andyblac commented Mar 9, 2021

can someone confirm something in alpha5, i think webui issues is linked with number of HAP connections, I can access webui, with no issues if HAP connections is 3 or less, as soon i hit 4 problems start, webui is hit and miss, the more HAP connections device has the worse it gets, over 5 and you loose total webui access.

how can I help confirm that? currently all my shellys are unavailable (although working...)

reboot, open log screen in separate tab, keep an eye on it for connections

@danny1605
Copy link

@andyblac
I can't see anything conspicuous, but the connection is lost
Unbenannt

The log screen at the time when the connection was no longer possible -->

1800676022 shelly_main.cpp:554 Up 1800.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1808676025 shelly_main.cpp:554 Up 1808.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1816676223 shelly_main.cpp:554 Up 1816.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1824675996 shelly_main.cpp:554 Up 1824.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1832676242 shelly_main.cpp:554 Up 1832.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1840676007 shelly_main.cpp:554 Up 1840.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1848675886 shelly_main.cpp:554 Up 1848.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1856675936 shelly_main.cpp:554 Up 1856.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1864676188 shelly_main.cpp:554 Up 1864.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1872676050 shelly_main.cpp:554 Up 1872.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1880676166 shelly_main.cpp:554 Up 1880.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1888676201 shelly_main.cpp:554 Up 1888.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1896675928 shelly_main.cpp:554 Up 1896.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0
1904675910 shelly_main.cpp:554 Up 1904.67, HAP 0/4/12 ns 4, RAM: 21164/37448; st 0; 0.1: st:0 in_st:0 inm:0 ininv:0

@andyblac
Copy link
Collaborator

andyblac commented Mar 9, 2021

@andyblac
I can't see anything conspicuous, but the connection is lost

yup, 4 HAP connections, as i said above soon as i hit 4 connections i get issues.

@rojer
Copy link
Contributor Author

rojer commented Mar 9, 2021

that's useful, thank you! i think i have an idea why

@rojer
Copy link
Contributor Author

rojer commented Mar 9, 2021

Thanks to eagle eyed @andyblac this is now fixed - there was a limit on number of TCP connections, set to 5.
I pushed alpha6, please try it.

@andyblac
Copy link
Collaborator

andyblac commented Mar 9, 2021

Thanks to eagle eyed @andyblac this is now fixed - there was a limit on number of TCP connections, set to 5.
I pushed alpha6, please try it.

so far so good, i'll keep an eye on it

@pivale
Copy link

pivale commented Mar 10, 2021

Thanks to eagle eyed @andyblac this is now fixed - there was a limit on number of TCP connections, set to 5.
I pushed alpha6, please try it.

Anyway we can reserve one connection always for webserver/script purposes?
It would prevent us from being left out, like now...

@andyblac
Copy link
Collaborator

Thanks to eagle eyed @andyblac this is now fixed - there was a limit on number of TCP connections, set to 5.

I pushed alpha6, please try it.

Anyway we can reserve one connection always for webserver/script purposes?

It would prevent us from being left out, like now...

HAP is limited to 12 connections, we have 20 TCP connections available now, no need too

@pivale
Copy link

pivale commented Mar 10, 2021

Cool, great to know 👍 Thanks for the info

@rojer
Copy link
Contributor Author

rojer commented Mar 11, 2021

ok, i think 2.8 is ready. any objections?

@andyblac
Copy link
Collaborator

ok, i think 2.8 is ready. any objections?

all good here.

@danny1605
Copy link

ok, i think 2.8 is ready. any objections?

all of my 20 shellys work very well with the alpha 6 version. thank you for that

@pivale
Copy link

pivale commented Mar 11, 2021

All seems to be working as intended here with alpha6.
Only strange behaviour was my shelly plug S going into AP mode (1st time it happened)... Not sure it's even related

log attached, if useful
shellyplug-s-tomada.log.zip

@andyblac
Copy link
Collaborator

i'll close this one, now 2.8.0 has been released.

@andyblac andyblac unpinned this issue Mar 11, 2021
@rojer
Copy link
Contributor Author

rojer commented Mar 11, 2021

@pivale

59453953491 shelly_input.cpp:76     Input 0: change (state 1)
59460215133 shelly_main.cpp:554     Up 59460.20, HAP 0/4/12 ns 4, RAM: 22588/38616; st 30; 0.1: st:1 in_st:-1 inm:-1 ininv:0
59463964293 shelly_input.cpp:76     Input 0: long (state 0)
59463973460 shelly_main.cpp:216     0: Reset sequence detected

looks like noise on button input.

@rojer
Copy link
Contributor Author

rojer commented Mar 11, 2021

submitted a fix, this will become 2.8.1. damn, i should've looked first

@rojer
Copy link
Contributor Author

rojer commented Mar 11, 2021

@timoschilling i'm flipping logic of 023159d back to "noisy button by default".

@andyblac
Copy link
Collaborator

submitted a fix, this will become 2.8.1. damn, i should've looked first

haha, i know whats like 🤣

@timoschilling
Copy link
Collaborator

@rojer as it's still configurable, it's fine for me. Maybe would you like to document why the noisy button is need and on which device.

@rojer
Copy link
Contributor Author

rojer commented Mar 11, 2021

rather, where it was observed. makes sense.

ok, pushed 2.8.1. i think 2.8.0 was the shortest lived release :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests