on my search for a smarter UI, esp. to have the chance to built it up with less stuff than meanwhile in my Pimatic frontend is shown , I found interesting treats about the usage of the ioBroker (VIS) interface.
But now I’m struggeling how to get that running.
I read about a respective plugin, but couldn’t find it at all. I only found the Git repository which I then cloned to my test-raspi, but then I got lost. Up to now, I only installed my plugins via the Primatic frontend.
Is there somewhere a tutorial how to get this working?
Howto install the ioBroker plugin?
Hi, Pimatic has no ioBroker plug-in. IoBroker has a Pimatic plug-in to integrate Pimatic.
So first install ioBroker, add plugins and then you can already show devices in vis.
I only use ioBroker because of the Alexa integration via the Pimatic plugin and for phone calls via the tr064 plugin. With a PI4- 4GB everything runs smoothly. VIS is too time consuming and the design is fragmented.
Translated with www.DeepL.com/Translator (free version)
Pimatic, my hobby.
I nearly searched 1 hour in direction of Pimatic itself, but now it becomes clear
Thanks very much Jens, you saved my Friday evening 😀
Use Iobroker parallel .(because of Alexa and vis)
Super is but Iqontroler adapter, is super simple .
Pimatic is as an adapter and overmines almost all devices.
Almost __only my roladen control Rohrmotor24 not !I can not control it _too bad.
Oh, good to know, as im using exactly the same shutter controls
Has someone already reached out to the ioBroker community to get a solution for this?
@arnold and @mwittig
as I have now been completely successful setting up Pimatic and ioBroker VIS on one Raspi4B, for you here the hint, that I got my rohrmotor24 shutter devices also steered via VIS.
I used a little workaround for this:
I simply created two button-devices (each per floor) and created within them 3 buttons per shutter (up/stop/down). Now I trigger this buttons, and not the shutter themself, by VIS, which then trigger my shutters by a respective little rule per button. It needs a bit diligent work to set it up and not loose the overview, as all that stuff looks quiet similiar, but it works super.
For sure, steering the shutters by time-, or sun-trigger, is done further on by Pimatic directly, without all that additonal buttons and rules.
I understand that pimatic needs it’s own echo support in the cloud. I’m still working on this.
Hi, If you look at the supported devices of pimatic-homeduino, rohrmotor24 is supported (shutter4), but you probably know why that isn’t working?
you probably know why that is
Well, the shutters are for sure working by pimatic-homeduino, so within Pimatic itself for me everything is fine.
They only do not work, manually triggered, from the ioBroker VIS frontend. Here I have the same experiences as the other ones an set up the explained work around.
Or did I get your question wrong?
@bertreb, yes this is correct for now.
For sure having now some addtional adapters in ioBroker, this might become interesting.
But my driver really first has been VIS, as meanwhile my Pimatic frontend is getting a bit too overloaded, what let the acceptance of my ‘users’ decrease…
And getting some addtional info embedded in a more convenient form, weather, birthday- and waste-calendar, is really a cool feature.
I also implemented 3D floor plans, which let the users now find all devices much more quicker than searching in a list e. g. the right shutter buttons. For sure a lot of work, but that was also for me the reason to get it in the end all in all running on only device.
… and the 4GB Raspi4B has especially enough RAM. I tracked that, and also the CPU-load, upfront on basis of the before running 2 Raspi3Bs.
Yes, i understand. If you use your home automation system with a lot of ui interaction and several different users, something like iobroker looks better.
I follow a low-gui approach for ‘normal users’. The pimatic gui is for ‘system management’.
I automate a much as possible (lights, thermostat, alarm, cameras, energy, etc). If user interaction is needed its done via specific physical buttons, telegram messages (birthdays, waste-calendar, etc), sounds and dashboards/reports stored in the cloud.
But if you want to post some of your screens, it’s always nice to see what others are doing!
Got your point, and also for me, Pimatic stays for management in the background.
There are some hidden-links in the VIS frontend, from where I also directly can access the Pimatic frontend. Non of my setup has a cloud connect, as on the one hand site, I’m a bit old fashioned when it goes in my private environment and, just this week, we had here a roughly 4 hours complete internet blackout, inkl. also ~1 hour also no connect via mobil. I keep also all other data inhouse, which I know, is at least not always the truth, but it makes me feel better
What I like most in my setup is that current combination. Pimatic with it’s really cool and userfriendly rule-engine, where I also automated meanwhile a lot of stuff here. And VIS as an easy to manage very flexibel WEB frontend.
I got all that set up without any Java/Coffee or developer knowledge, only on basis of my little linux expertise, which I learnd here, and also in the ioBroker forum, well supported by people like you
With regard to screen posting, I’m a bit shy, as for sure that would show where we implemented what sensors here. And the original driver behind all that setup was, that we had a try to break in our house now rougly two and a half years ago. After that I started to investigate and now it became a kind of hobby
… good night for now, talk to you again soon …