21 minutes ago, DeepBass9 said:

I.m trying to install SSH on the pi but get this error:

Hi DeepBass9

The way to enable SSH on a Pi is to use the "raspi-config" - see https://www.raspberrypi.org/documentation/configuration/raspi-config.md

21 minutes ago, DeepBass9 said:

The time I would save by automating things compared to the time I have wasted on home assistant are rapidly becoming indistinguishable.

Aaah, but would it have given you the same sense of achievement or as much "fun"? 😛

Edited August 6, 20196 yr by NigelL

I'm starting to imagine a 4 pound hammer making contact with the pi.

8 minutes ago, DeepBass9 said:

I'm starting to imagine a 4 pound hammer making contact with the pi.

😂  I can appreciate the frustration when nothing is working and all the documentation one can find is out of date - so does not help solving the problem.

I have Home Assistant running successfully on a Pi3B with a Z-Wave network so may be able to assist with some pointers.

Regards, Nigel

Zwave sounds interesting. But first to get the pi to work!

I'm using HassOS.

Edited August 6, 20196 yr by DeepBass9

@DeepBass9 - you posted a picture a bit back of the basic network with the PI, PC, etc.  Could you perhaps extend that to show the smart devices such as the plug as well?  But this time add IP addresses to each.

Generally, devices in different subnets can't speak to each other, unless there's a static path defined between the two or some kind of routing protocol in place. 

I have given up on the devices for the time being. I an just trying to get the Pi to connect to the network and to be able to see the pi from both the wired and wireless network.

It can be a problem with the network itself. I have a Win10 computer and Win7 laptop maybe they are confusing the issue. The network has never really work properly. 

Can you ping the PI from the laptop if the laptop is connected to the router with a cable and the wifi is disconnected?

Can you ping the PI from the laptop if the laptop is only connected to Wifi? 

 

The PI is still on 192:168:0.111 ?

Laptop's wired IP is 192.168.0.x
Laptop's Wifi IP is 192.168.2.y

?

Hi DeepBass9

Your earlier screenshot of the Access Point shows that it has the DHCP server enabled - so will issue IP addresses to all WiFi devices and devices connected to its downstream LAN ports. These IP addresses will be in the 192.168.2.x range.

Your Satellite Internet Modem (your gateway to the internet) is likely to also have its own DHCP server enabled - so it issues IP addresses to all the devices on the LAN in the 192.168.0.x range.  The Access Point probably therefore has a 192.168.0.x WAN IP address. The routing between sub-nets is therefore done inside the Access Point.

Assuming this is the case, this means that your WiFi devices will have access to the Internet but be completely isolated from any devices on the upstream LAN (PC, Pi etc.).

I think (but am not certain) that the way to fix this will be to modify the Access Point so that it operates in a simple "bridge" mode. 

EDIT: What model Access Point are you using?

Edited August 6, 20196 yr by NigelL

OK, now that is strange I can the Home assistant page on 192.186.0.111, but can't ping it? Refresh the browser and it is there but can't ping.

4 minutes ago, NigelL said:

Hi DeepBass9

Your earlier screenshot of the Access Point shows that it has the DHCP server enabled - so will issue IP addresses to all WiFi devices and devices connected to its downstream LAN ports. These IP addresses will be in the 192.168.2.x range.

Your Satellite Internet Modem (your gateway to the internet) is likely to also have its own DHCP server enabled - so it issues IP addresses to all the devices on the LAN in the 192.168.0.x range.  The Access Point probably therefore has a 192.168.0.x WAN IP address. The routing between sub-nets is therefore done inside the Access Point.

Assuming this is the case, this means that your WiFi devices will have access to the Internet but be completely isolated from any devices on the upstream LAN (PC, Pi etc.).

I think (but am not certain) that the way to fix this will be to modify the Access Point so that it operates in a simple "bridge" mode. 

OK, let me try that:

 

Ideally you want a single DHCP server on your network - so that all LAN and WiFi devices get IP addresses on the same sub-net.  They will then all be able to "see" each other and have access to the internet.  

So I have these options : 

What make and model is the wireless access point?  The devices doesn't always use the same names for functions - would be easier if we could look at its datasheet/user manual.

Do you have a link to the Wireless Router manual? I don't want to recommend something that may break your network !

Don't worry, the network is already broken!

Its a Canyon 300N.

17 minutes ago, DeepBass9 said:

OK, now that is strange I can the Home assistant page on 192.186.0.111, but can't ping it? Refresh the browser and it is there but can't ping.

 I see you swapped round the 192 and 168  😉

Mystery solved. The network has scrambled my brian.

The router is canyon 300n wireless ap router cnp-wf514n3. I'm looking for a manual now.

Can't you remove the Toto switch and plug everyting into the Canyon router?

And then switch off DHCP on the satellite internet modem?

No, its in a different part of the house, and doesn't have enough ports.

Also, the Canyon doesn't seem to have a WAN port, so my idea wouldn't have worked. 🙈

1 minute ago, Tacet said:

And then switch off DHCP on the satellite internet modem?

I have no idea how to do that. I tried to switch of DCHP on the wireless router but that didn;t change anything.

What make and model is the satellite internet modem?

The satellite modem is a hughes hn9600.

In the meantime I may have made some progress. I moved the cable from the switch to the AP from the WAN port to a normal port. Now the wireless AP comes up with an IP of 192.168.0.5. 

 

You can now try to disable the DHCP on the Canyon again - see if the devices connected to it get their IPs from the Hughes.