Hi all,
I’m stuck with scripts…
When I execute a script nothing happens.
Even when I’m trying to test one in the web interface like log(‘Hello’);
In the console field on the bottom of the screen, the message “Script output will appear here.” disappears when I click on the Test button and then…nothing…
I’m on Mac, I tried Safari & Edge, I restarted the app and my Homey Pro 2023 but nothing changes.
don’t know what to do,
Someone is having the same issue ?
I’m progressing:
I restarted my Homey and the app several times as you proposed (thank you).
It works on my iPad but not on my work MacBook computer (neither with safari nor Edge).
Starting to be a bit weird…though I have some proxy & firewall config on this computer which could explain that ?
I’ll test tonight with my personal MacBook computer (which has none of these configurations) to confirm that.
Here below you can see what’s happening when I click on the “play” button.
I tried everything I had in mind.
It works on my iPad (last versions of chrome & safari) but not on my Apple computers (last version of chrome & safari as well)
I tried with my pro & personal one (without any proxy nor firewall nor vpn on my personal one)
I tried to deactivated every possible extensions to be sure (adBlock and others).
So, I don’t know what’s going on, webpage bug ?
Someone ? Athom ?
Well, after rebooting almost everything, I can execute scripts on chrome on Mac OS and chrome and safari on iPad os
Good enough for me, though really weird
Thank you !
Problem: as discovered in inspection mode, websocket connection to node server (using your Homey’s personal hostname) could not be established. The problem, i think off, relates in combination with networkproviders who have incorporated CGNat resolution, like Caiway / Delta in the Netherlands.
Solution for Safari: I figured out that once I enabled a valid VPN connection (in my case Hotspot Shield) before trying, logging with output to the console works as usual. The state of a valid server network resolution remains cached apparently, because closing and reopening browser page had no negatieve effect.