you could setup log filters (standard OH feature), check the RRADME (advanced)
And what you recommend for that? Profiles/JS transformation as mentioned above?
Great stuff markus7017, with the new DEV 3.3 Binding, which supports the TRV.
I have now copied, my production system to a dev Pi HW System with a different IP-adress and installed the DEV binding. The TRV was found without any problems and I was able to add him in the system with all chanels.
Really great stuff Markus.
Then I have added two Switches. One, which toggle the TRV 0 position or 100 position to the valve.
The other should send a āauto-tempā, to come back to normal auto-operation-mode. But this seems to be not accepted. So I send now 23 to the target temperature chanel, to bring them back to auto-temp.
Is there a possibilty to have auto-temp and manuell as values to send the the TRV?
BR
Jochen
Very, very good job Markus !!!
1 Like
Hi and thank you for this great binding. I have started with a Shelly 2.5 and four Plug S, which worked fine. A very professionell binding! Now Iām installing Plus 1 Shellys and realized that they are not supported by this binding. Is there a chance they will be supprted soon, or is it better to replace them with old Shelly 1?
1 Like
Support for the Plus series will take a while. Iām super busy and canāt find the time. That hurts, because Iām committed to the Shelly products & binding. Maybe someone else could help
1 Like
I got my Shelly i4 today. Can I help with anything?
I have one more question. I set unicast on all my shellys.
Now I am in the process of setting up openhab3 and the Shellys receive updates although the unicast IP is different.
I thought with setting an unicast address the shelly should not communicate with another host.
that is related to CoIoT protocol.
Your shelly device still searches for updates over http protocol (if it has access to the internet)
How can I help to add the Plus 1? Is there something like a textfile where I can add devices?
where do you see the traffic? If you enabled unicast you should see only coiot traffic (udp) and http for the API, beside maybe ntp or an http request to the shelly firmware repository
thatās what I said
I could turn off lights but couldnāt turn them on anymore. Is ok.
Now I have moved to openhab3 completely. With changed unicast IP Adressā¦
My old sitemap works. I have to learn the pages in openhab3.
All Shellys are working fine.
Can I help with Shelly i4?
did you set auto brightness in the thingās setting to on?
There is still no alternative to Shelly 2.5 for roller shutter operation. The gen2 devices are still limited to 1-channel relay switches (Shelly Plus series) and the DIN relay switches (Shelly Pro series).
An news in Shelly 1 Plus support? Is the v2 API with optional digest authentication already supported (e.g. Shelly Pro 4PM already utilizes this)?
I am using the Shelly Plus 1 as a gate opener and currently I need to call an external curl command from openhab (because internal HTTP handlers donāt support digest authentication).
Hey, is it possible to set the upper/lower temperature threshold via the Shelly binding with a Shelly-1 temperature addon? So far I change it via http call which works but blows up my code. I would like to clean up my code a bit. It looks like I can only read the current temperature and the upper/lower thresholds but not set them.
The TRV supports now the āboosterā function. Will this be added to the binding, and when markus7017?
Would be nice to have a OH3 button to use the booster before leaving thne office and arreive in a nice and warm homeā¦
I donāt see a booster function on the device webpageā¦
Which is not rolled out actually 