Shelly Binding

Sorry of this has been discussed already but I could not find it: since a couple of days both of my Shelly Plug-S no longer send anything other than 0 on the lastPower1 channel. I don’t exactly know when this started but I am on the OH3 release build right now so there have not been any changes to the binding recently on my end. It was running fine however for the first couple of weeks of OH3.

So I thought this could be related to a recent update of the Shelly firmware so I downgraded to 1.9.2 and removed/readded the thing but still I can’t get any value other than 0.

When I find the time I will try it with the latest Dev build but I was wondering if anyone else experienced this!?

  • check with devide-ip/status the value reported by the device,
  • consider a factory reset

3.0 release version is outdated, upgrade to DEV version, this pretty stable and can be done in 10 minutes, check the How to install

Latest DEV build: 2.5.13 - 3.1.0 - README - Installation - Bugs/Features - Firmware Index - Firmware Archive - API Doc
Note: The binding versions included in the final OH 2.5/3.0 distro releases are significantly older than the DEV build. Make sure you deleted older versions of the binding when installing the 2.5.13-SNAPSHOT or 3.1.0-SNAPSHOT if you are already on OH 3.

Thx for the info.
I’m going to update to version 2.5.12 and install you latest devbuild.
But first I have to order the shelly motion
Thanks for the effort also for the old 2.5 version.

Could you please let me know the name of the property in the status? I updated to the DEV build but it still does not show a value in OH.

I could factory reset of course, seems strange though that both are failing but again this could be due to a faulty firmware…

hi, I’ve downloaded the latest dev build in your autograph the 3.1.0 one,
but the shelly motion is still an unknown’ device

when i went trought paper gui earlier i had binding 3.1.0.M1, but the shelly motion is listed as ‘unkown device’ too

ny ideas?

Motion is def. supported by the DEV build. Make sure you deinstalled the version coming with OH

229 │ Active │  80 │ 3.1.0.202101212341      │ openHAB Add-ons :: Bundles :: Shelly Binding

this is the one i downloaded trough you autograph, is this te correct one?

you are right, it seems that my uoload script is broken since end of January
I updated 3.1-SNAPNOT


3.1.0 - README - Installation - Bugs/Features -

1 Like
openhab> bundle:list | grep Shelly
208 │ Active │  80 │ 3.1.0.202102202342      │ openHAB Add-ons :: Bundles :: Shelly Binding

Installed the new one you linked in your authgraph,
-> no longer visible true paperui as a binding.
-> shelly’s do seem to get ‘discovered and are in the inbox’

but the motion is still listed as shelly:unknown

PaperUI is not part of OH3, I‘m confused
it seems that you have some mix

use bundle:list on the OH console and make sure that there is no other version installed, sometimes the uninstall has left-overs

maybe you need to do a clean-cache

you need

  • OH3 (3.0.1 or current SNAPSHOT)
  • Shelly binding not installed in the UI
  • Both Californium jars in the addon folder
  • Binding 3.1.0-SNAPSHOT jar in the addon folder
  • delete all Shelly things

If you use password protection make sure to set the credentials in the binding settings, delete all things and then re-discover

You have to see the Binding in the UI, start the discovery from there and it brings up all yout Shellys in the Inbox incl the Motion.

Yeah I didn’t mean paper UI just web UI.
I have oh 3.1 from openhabian. (3.1.0.M1 - Milestone Build could that be the issue?)
(cache has been cleaned too)

The binding isn’t listed in the web UI, but it does seem to work except for the motion sensor

UPDATE:
it’s working now i found an old shelly addon generated file in the OH setup deleted the file and rebooted.
now: the binding is not visible under settings -> bindings
BUT
you can go to settings -> things -> + sign -> select shelly

  • is manual
    it should work in discover mode

you may need to wake up the Motion. Try a device reboot. The motion disables mdns 3min after restart

discovery mode is working:
vibration also works
in your readme I saw that there was a channel sensors#motion
but in the channels I can’t find this one :slight_smile:

Check the updated build

1 Like

Did so:
openhab> bundle:list | grep Shelly
196 │ Active │ 80 │ 3.1.0.202102211348 │ openHAB Add-ons :: Bundles :: Shelly Binding

but the option sensors:motion is still unknown :slight_smile:

Hi @markus7017 ,
I installed 2 spots ( Shelly DUO GU10 ) and they do not work with the binding.
I assume they are on your radar? Haven’t found some comments using the search function.
It is detected without IP address - can be fixed manually - then it is recognized as shellyunknown and I can get the power measurements, but cannot control it.
I am running on the 3.0.1 stable version.
Thanks!
PhiL

Please update to DEv build

Latest DEV build: 2.5.13 - 3.1.0 - README - Installation - Bugs/Features - Firmware Index - Firmware Archive - API Doc
Note: The binding version included in the final OH 3.0 distro is significantly older than the DEV build. I can’t make it in-time. Make sure you deleted older versions of the binding when installing the 2.5.13-SNAPSHOT or 3.1.0-SNAPSHOT if you are already on OH 3.

ok, verified - Allterco changed to JSON layout for the motion indicator, fixed & verified

1 Like

Yep, I can confirm it’s working now,
thx for the effort, keep up the good work!

Hi @markus7017,

thanks for providing that binding.
Now I am facing another challenge with Shelly Motion. I put the motion sensor into a room with no motion - but openHAB still reports motion. But that’s not true. Even the Shelly App does not report any motion, but OH log shows:

2021-02-22 12:31:50.989 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ShellyMotion244_LetzteBewegung' changed from 2021-02-22T12:16:49.000+0100 to 2021-02-22T12:31:50.000+0100
2021-02-22 12:46:52.715 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ShellyMotion244_LetzteBewegung' changed from 2021-02-22T12:31:50.000+0100 to 2021-02-22T12:46:52.000+0100
2021-02-22 13:01:53.331 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ShellyMotion244_LetzteBewegung' changed from 2021-02-22T12:46:52.000+0100 to 2021-02-22T13:01:53.000+0100
2021-02-22 13:16:53.952 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ShellyMotion244_LetzteBewegung' changed from 2021-02-22T13:01:53.000+0100 to 2021-02-22T13:16:53.000+0100
2021-02-22 13:31:55.803 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ShellyMotion244_LetzteBewegung' changed from 2021-02-22T13:16:53.000+0100 to 2021-02-22T13:31:55.000+0100

Because this status obviously change every 15 minute - I assume it polls the status of the Sensor?
But why does it report motion? Maybe I do have a wrong understanding?
Is there something mixed up with regards to “MotionTimestamp” and “last Update”? :slight_smile: