Hi everybody,
I am just doing my first step with selenium and the respective node. So I installed Selenium-hub and selenium-standalone-chrome in a docker container on my Synology. Installation was without any problem and both containers are up and running.
I added node-red-contrib-selenium-webdriver to my node-red installation (which I added as an adapter of I-broker). Node-red (and some further flows) is working fine without any problem.
Then I created a basic flow: inject => open-web => debug with an open-web node configured as server http://192.168.178.3:32772 and chrome as browser. After deploying the open-web shows "connected" as status.
But when triggering that flow after some seconds I get the message "connection lost" ... and reestablished. The msg.payload is empty.
...
Any ideas about that???
PS: The log file (ioBroker adapter in debug) says:
++++
The selenium node hasn't been updated in quite some time, maybe you could try https://flows.nodered.org/node/node-red-contrib-puppeteer-new? It has been recently created and it uses Puppeteer which is a more modern browser automation framework than Selenium/WebDriver. I haven't used either though so can't give any further hints.
You should also look at WebDriver IO nodes (node-red-contrib-wdio) - they are stable,simple, and fast. The Puppeteer nodes are still in alpha I believe and may be missing some features you need.
Hi Paul,
in GitHub the comment says "Experimental nodes to work with selenium 2.0 webdriver bindings - uses webdriverio" - with no further explanation. Any ideas about which further components (apart from node-red-contrib-webdriverio) I have to install?
Rainer
