since my last postings about getting ioBroker in general connected with Pimatic I did some major steps.
I really like the VIS frontend, which is very flexible in design and e. g. bringing in floorplans with device control buttons and sensore in the right place, or maybe control icons/pics into a camera picture and so on and so on, works really cool.
In the end I also solved the problem with the rohrmotor24 shutter controls by setting up a simple buttons-workaround in Pimatic. Really simple!
Yes that all was time consuming but now looks definitely much more convenient for my ‘other users’ at home
… and also for me
So everything should work fine, but: …
I installed ioBroker on a test clone of my prod Pimatic environment (PI3B, stretch, node 10.16.3, npm 6.9.0, ConBee II / 433Mhz Ard-Nano RF). The idea was, to later on simply switch the dev environment into the new prod setup.
I did the whole development on the clone, while connected via NW to my prod Pimatic, which worked really well, incl. the permanent access to VIS from a 10,1" China tablet, hanging in the kitchen.
As node has already been installed in context of Pimatic, I for sure didn’t install a second instance while installing ioBroker. The setup worked well since now roughly 2 weeks, but yesterday, after a reboot the system didn’t come back and I have no clue why.
I already chatted with some guys in the ioBroker forum, but over there no one has experiences with the Pimatic installation incl. node.
So now my question here would be similar:
Does someone have experiences in running Pimatic and ioBroker on the same device (PI3B)?
Is there something special to consider e. g. in reference with the node(js) installation?
My driver here is, that as how I use ioBroker, the performance of a PI3B should be enough to run both on one system…
Thanks in advance
Happy that Pimatic is still running w/o ioBroker and doing its work in the background