I had to turn off the fuse to the HS3 and Phoscon Raspberries, so I politely turned them off first. HS3 by using the Tools->System->Shutdown system. And Phoscon, or rather it's Linux by sudo shutdown now. Then I turned off the mains fuse, did my job and turned it on again.
And JowiHue could not find the bridge! It presented the IP to the bridge being what my home system use ( this is in my summer house ). I cannot see why, as both Raspberries with their software have been started from scratch. Not this being a copy of the one at home. The PC I use to manage them is the same though.
Anyway, I just deleted the bridge and started scan for new bridge. That does not seem to work.
I run HS3 on Raspberry as mentioned. After this problem I updated Jowihue to 2.1.1.11. I believe it was 2.1.1.10 when the problem started.
So I searched for help and found this: http://www.vuyk.info/hs/jowihue/connectbridge. But I am unable to find the dialog mentioned there!
I can VNC to Phoscon and see that it's web interface shows the nodes are connected, so I know Phoscon is running. Also the Phoscon app connected through the browser on the PC.
The power down was to install a new light fixture. Not to change anything in HS3 or Phoscon.
Regards
Einar Sjaavik
Edit: Additional info.
I enabled logging in Jowihue and it seems it is actually looking for the bridge I deleted!
The IP should be 192.168.88.42 ( Bridge ).
I would rather not set the IP range identical to my home network to circumvent the problem.
Edit 2: Tried to make JowiHue.ini file in /usr/local/HomeSeer/Config. That did not do anything.
Edit 3: Progress ??
What I did: First see Edit 2.
- restarted DeConz.
- Then the bridge appeared in JowiHue Configuration.
- I clicked for it to register. Nothing much happened.
- I restarted DeConz. Nothing....
- In DeConz Gateway Advanced I clicked Authenticate app.
- Then the log file indicated it found it and started registering devices.
- Then the bridge disappeared from JowiHue configuration.
- I did the same again a couple of times.
- And finally the bridge is back and working!??
I will now stop logging options in JowiHue and copy the logfile to PC in case it may contain a clue to what happened and wht did not happen.
And JowiHue could not find the bridge! It presented the IP to the bridge being what my home system use ( this is in my summer house ). I cannot see why, as both Raspberries with their software have been started from scratch. Not this being a copy of the one at home. The PC I use to manage them is the same though.
Anyway, I just deleted the bridge and started scan for new bridge. That does not seem to work.
I run HS3 on Raspberry as mentioned. After this problem I updated Jowihue to 2.1.1.11. I believe it was 2.1.1.10 when the problem started.
So I searched for help and found this: http://www.vuyk.info/hs/jowihue/connectbridge. But I am unable to find the dialog mentioned there!
I can VNC to Phoscon and see that it's web interface shows the nodes are connected, so I know Phoscon is running. Also the Phoscon app connected through the browser on the PC.
The power down was to install a new light fixture. Not to change anything in HS3 or Phoscon.
Regards
Einar Sjaavik
Edit: Additional info.
I enabled logging in Jowihue and it seems it is actually looking for the bridge I deleted!
The IP should be 192.168.88.42 ( Bridge ).
I would rather not set the IP range identical to my home network to circumvent the problem.
Code:
homeseer@HS3Pi3v6:/usr/local/HomeSeer/Logs $ cat JowiHue.log (web_config.postBackProc) Debug: Config:Debug: checked (web_config.postBackProc) Debug: Config:id: Debug (web_config.postBackProc) Debug: oTabConfig (web_config.postBackProc) Debug: Config:oTabs: oTabConfig (web_config.postBackProc) Debug: Config:id: oTabConfig (web_config.postBackProc) Pressed button for immediate scan for bridges - scanni ng started (web_config.postBackProc) Debug: Config:id: obtnScan (web_config.postBackProc) Debug: Config:btnScan: Submit (web_config.postBackProc) Debug: Config:id: timer (web_config.postBackProc) Debug: Config:id: timer (MyBridges.BridgeCheckIP) Debug: IP address 192.168.1.32 not responding: The ope ration has timed out. (UPNP.Bridgescan) Debug: End search for bridges
Edit 3: Progress ??
What I did: First see Edit 2.
- restarted DeConz.
- Then the bridge appeared in JowiHue Configuration.
- I clicked for it to register. Nothing much happened.
- I restarted DeConz. Nothing....
- In DeConz Gateway Advanced I clicked Authenticate app.
- Then the log file indicated it found it and started registering devices.
- Then the bridge disappeared from JowiHue configuration.
- I did the same again a couple of times.
- And finally the bridge is back and working!??
I will now stop logging options in JowiHue and copy the logfile to PC in case it may contain a clue to what happened and wht did not happen.
Comment