Shellyforhass: [BUG] | [FR] New CoAP description in FW 1.8

[vistalba]

As stated here, there will be a breaking Change with Firmware 1.8.

https://www.facebook.com/groups/ShellyIoTCommunitySupport/permalink/3002067616559249/

As ShellyForHass is using CoAP I think a update is needed.

[chemelli74]

We are already working on making ShellyForHASS compliant to new firmware specs.
Stay tuned.

Simone

[robinostlund]

Any updates on this one? As they have started to roll out the updates 😊

[mrulke]

saw the dev release. happy help with testing as i have updated my dimmer 2 to the 1.8 firmware to stop flickering.
do I just copy the dev branch over the top of the current install?

[Tom7320]

I can confirm that it definitely is a breaking change with 1.8.0. Unfortunately I updated all my Shellys to 1.8 and now I can't control them anymore from HA. Since I have a lot of Shellys I would like to ask if there is another easy way to fix the issue without waiting for the next ShellyForHASS release? I would also suggest rating this issue as a bug instead of a feature request. Log:

Error receive CoAP Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/pyShelly/coap.py", line 182, in _loop self._root.update_block(device_id, device_type, File "/usr/local/lib/python3.8/site-packages/pyShelly/__init__.py", line 242, in update_block block.update(data, ipaddr) File "/usr/local/lib/python3.8/site-packages/pyShelly/block.py", line 92, in update dev.update(data) File "/usr/local/lib/python3.8/site-packages/pyShelly/switch.py", line 46, in update self._update(state > 0, {'last_event' : self.last_event, TypeError: '>' not supported between instances of 'NoneType' and 'int'

[vistalba]

@Tom7320
Just downgrade your all affected shelly‘s?

http://[IPOFSHELLY]/ota?url=[URLTOOLDERFIRMWARE]

You just need the older FW files hosted on a Webserver and replace the values above.
Important: use the correct FW file per device. You need to execute it once per device. Battery operated devices need to be waked up before hitting the URL.

[artkrz]

No offence guys, but CoAP changes were announced in advance and making ShellyForHASS ready for it should be priority. I realise you're probably doing this in your free time and I'm grateful but this should be fixed and fv rollback isn't really an option for all since 1.8 fixed major issues with dimmer overloading and other shelly device restart problems.

[Tom7320]

Well I agree. I don't want to downgrade. And I certainly can wait a couple of days. It's just that I can not control my shutters anymore, and we have over 35°C today.... 🔥

[vistalba]

Please be patient.
I‘m waiting too.
8 days ago they announced that change. I‘m sure the developers of ShellyforHASS didn‘t wait for that change and now have to fix a lot of things (in their free time) for every device.
8 days is not a lot of time, so downgrade Shelly FW to < 1.8 if controling in HA is important to you or wait until new Shellyfor HASS version is ready. I know it‘s not nice but it is how it is at the moment.
I‘m sure the devs know about the importance of this issue.

[vistalba]

Well I agree. I don't want to downgrade. And I certainly can wait a couple of days. It's just that I can not control my shutters anymore, and we have over 35°C today.... 🔥

Downgrade.... 2.5 in roller shutter really didn‘t have any issues as I‘m using it too. So „i don‘t want to...“ really doesn‘t matter.

[Tom7320]

What's the newest firmware before 1.8.0? 1.6.1? There was no 1.7?

[Tom7320]

Never mind. Found it. https://www.shelly-support.eu/index.php?shelly-firmware-archive/

[vistalba]

@Tom7320 depends on device. My 2.5 is on v1.7.4 at the moment which is working fine with HA.

Didn‘t find that Version... but I‘ve found two for you...

http://1.2.3.4/ota?url=http://archive.shelly-support.eu/v1.7.7/SHSW-25_build.zip

http://1.2.3.4/ota?url=http://archive.shelly-support.eu/v1.7.0/SHSW-25_build.zip

Just replace 1.2.3.4 with the IP of the Shelly 2.5 you want to downgrade.

[Tom7320]

Downgraded. Works again. Thx a lot!

[GoNzCiD]

I have updated several devices and I'm having this error too, I'm going to test the dev version as @mrulke said...

[hakana]

saw the dev release. happy help with testing as i have updated my dimmer 2 to the 1.8 firmware to stop flickering.
do I just copy the dev branch over the top of the current install?

dev branch is just for development team to share code, it is very unstable. Please not use!

[Soylor]

I dis solve it until new shellyforhass is published using Shely DDD and rest API.
Configured as Entities instead of devices but working fine until new version available.

[IATkachenko]

We are already working on making ShellyForHASS compliant to new firmware specs.
Stay tuned.

@chemelli74, @hakana, hello.
Is any public activity available for this? Community may take a part too.

ps. Bumping pyShelly to master@github version is solving my issues.

[chemelli74]

We are already working on making ShellyForHASS compliant to new firmware specs.
Stay tuned.

@chemelli74, @hakana, hello.
Is any public activity available for this? Community may take a part too.

Working hard on the release, please be patient a little bit more.

ps. Bumping pyShelly to master@github version is solving my issues.

We kindly ask not to mix up things testing with master/dev/whatever.
Thx for the cooperation.

Simone

[vistalba]

@chemelli74 What's your best guess for FW 1.8 support?

[EvTheFuture]

@chemelli74 What's your best guess for FW 1.8 support?

I would rather ask @chemelli74 if there is something we can do to help, testing, coding, whatever?

[artkrz]

No hard feelings guys, I do appreciate your work and was happy with this integration so Thank You. However, I'm done waiting and looks like MQTT is the way forward. To others that don't want to wait any longer, remember, this is free software, you can always go elsewhere. Good luck.

[mathewmeconry]

Is there a way that I can help you guys to get this update done? Testing, developing or something else?

[msekoranja]

The biggest pain is not knowing about progress, timeline. A day, a week, a month or never - it's OK (this is a open-source project), it is just good to be informed.

[kauha]

I'm also stuck on 1.8+ on RGBW2 and for some reason downgrade doesn't work (tried hosting the file on LAN too..) so a timetable would be nice. Also willing to help in progress if possible

[radubatori]

@kauha Downgrading RGBW2s did not work for me as well, but enabling MQTT and using something like this is a good enough workaround for now. I know it's not ideal and I hope this great library gets updated soon.

[stevearmitage]

The Facebook post today states that you can access them beta from here today or HACS tomorrow. I'll download the HACS update tomorrow. Thanks for keeping the plugin updated.

[NickDePooter]

After installing the Beta version I still keep getting this errors:

2020-08-27 20:13:13 ERROR (Thread-141) [pyShelly] Timeout connecting to http://192.168.0.224/status [192.168.0.224]
2020-08-27 20:13:23 ERROR (Thread-142) [pyShelly] Timeout connecting to http://192.168.0.224/status [192.168.0.224]
2020-08-27 20:13:23 ERROR (Thread-143) [pyShelly] Timeout connecting to http://192.168.0.224/status [192.168.0.224]

Any ideas or people with the same issue?

[Soylor]

Every thing fine after dowgradimg to 1.7 firmware

El jue., 27 ago. 2020 20:21, NickDePooter [e-mail]
escribió:

After installing the Beta version I still keep getting this errors:

2020-08-27 20:13:13 ERROR (Thread-141) [pyShelly] Timeout connecting to
http://192.168.0.224/status [192.168.0.224]
2020-08-27 20:13:23 ERROR (Thread-142) [pyShelly] Timeout connecting to
http://192.168.0.224/status [192.168.0.224]
2020-08-27 20:13:23 ERROR (Thread-143) [pyShelly] Timeout connecting to
http://192.168.0.224/status [192.168.0.224]

Any ideas or people with the same issue?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/StyraHem/ShellyForHASS/issues/366#issuecomment-682113897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGF646TUJZW6UOZ2Y7UYK3SC2P4HANCNFSM4PV2ATBQ
.

[thecem]

Thanks a lot! EM3 are working!
But shelly 2.5 FW 1.8.3 and 1.8.0 in shutter mode do not have status, only after boot it is for a few seconds visible (the shutters working in homebridge-shelly an are calibrated).
So if the shutter is closed you have only the possibility to close it, because ha 0.104.4 is assuming all are open...

[vistalba]

Thanks a lot! EM3 are working!
But shelly 2.5 in shutter mode do not have status, only after boot it is for a few seconds visible (the shutters working in homebridge-shelly an are calibrated).
So if the shutter is closed you have only the possibility to close it, because ha 0.104.4 is assuming all are open...

Is reported here: https://github.com/StyraHem/ShellyForHASS/issues/399

[chemelli74]

Support for firmware 1.8 added in 0.2.0b1 version.

If you have any further issue, please open a specific and detailed issue.

Simone