Tassos wrote:

The reboot option is high on my list as well. As far as the stability of the connection is concerned I am encountering zero problems. My Halo is always connected except if I restart my router, in which case (sometimes) it gets the previous IP+1 (192.168.1.180 before the restart, 192.168.1.181 after the restart). Restarting the BLI solves the issue. I am using the velop system of linksys with 2 mx5300 nodes. One as a router and the other as a child node. Wi-Fi coverage is excellent throughout the house and Wi-Fi speed is very fast especially to Wi-Fi 6 enabled products. I don't know if this is of any help to you Beojeff.

I alway set fixed IP”s in my router on all BLI Stuff, why don”t you set it fixed Tassos? Saves hassle and you know where to look.

Login to view image

I am burning the fireplace hence the 18 vs 22C

chucky wrote:

Tassos wrote:

 

The reboot option is high on my list as well. As far as the stability of the connection is concerned I am encountering zero problems. My Halo is always connected except if I restart my router, in which case (sometimes) it gets the previous IP+1 (192.168.1.180 before the restart, 192.168.1.181 after the restart). Restarting the BLI solves the issue. I am using the velop system of linksys with 2 mx5300 nodes. One as a router and the other as a child node. Wi-Fi coverage is excellent throughout the house and Wi-Fi speed is very fast especially to Wi-Fi 6 enabled products. I don't know if this is of any help to you Beojeff.

 

 

I alway set fixed IP”s in my router on all BLI Stuff, why don”t you set it fixed Tassos? Saves hassle and you know where to look.

I've set static IP addresses for my Halos and the BLI, but the problem of the BLI losing connection with the Halos is still recurring.

Tassos wrote:

maybe you can start with it…

I would try it this way

Make a Resource named "Nest" for example of the type Thermostat and address "1".

 

function(event, engine) 

  local Temp_query=engine.query("your_area/your_zone/THERMOSTAT_2SP/Nest/TEMPERATURE")

  local temp = Temp_query[1].get_number("VALUE")

 

engine.fire("your_zone/your_area/Halo remote/your_Halo/SET_TEXT?BUTTON=497f6eca-6276-4993-bfeb-000000810xxx&TEXT="..tostring(temp))

end

 

But in so far I can look into the Nest/BLI capabilities, I'm not sure it will work. Reading the Help file one should expect it will though.

 

OR try this line instead of the above one

  local Temp_query=engine.query("your_area/your_zone/THERMOSTAT_2SP/Nest/State/TEMPERATURE")

 

Interesting would be to see what happens, what info you get, in Tools/Monitor, when you press the button

 

 

 

Carolpa wrote:

Tassos wrote:

maybe you can start with it…

I would try it this way

Make a Resource named "Nest" for example of the type Thermostat and address "1".

 

function(event, engine) 

  local Temp_query=engine.query("your_area/your_zone/THERMOSTAT_2SP/Nest/TEMPERATURE")

  local temp = Temp_query[1].get_number("VALUE")

 

engine.fire("your_zone/your_area/Halo remote/your_Halo/SET_TEXT?BUTTON=497f6eca-6276-4993-bfeb-000000810xxx&TEXT="..tostring(temp))

end

 

But in so far I can look into the Nest/BLI capabilities, I'm not sure it will work. Reading the Help file one should expect it will though.

 

OR try this line instead of the above one

  local Temp_query=engine.query("your_area/your_zone/THERMOSTAT_2SP/Nest/State/TEMPERATURE")

 

Interesting would be to see what happens, what info you get, in Tools/Monitor, when you press the button

 

 

 

I knew you were good with lua but I didn't know you are fast as well!!!😁🤒

I will check as soon as I get home. Just for the record I think that from the moment nest was bought by google it started being more a liability than an asset in home automation. My main complain is that the home/away function doesn't work as it should. I tried everything that is posted on the web, everything that my mind could thought but still it works when it feels like working. Not reliable at all. Migrating to google account is not an option since I am going to lose connectivity with the BLI. Pitty!

chucky wrote:

Tassos wrote:

 

The reboot option is high on my list as well. As far as the stability of the connection is concerned I am encountering zero problems. My Halo is always connected except if I restart my router, in which case (sometimes) it gets the previous IP+1 (192.168.1.180 before the restart, 192.168.1.181 after the restart). Restarting the BLI solves the issue. I am using the velop system of linksys with 2 mx5300 nodes. One as a router and the other as a child node. Wi-Fi coverage is excellent throughout the house and Wi-Fi speed is very fast especially to Wi-Fi 6 enabled products. I don't know if this is of any help to you Beojeff.

 

 

 

I alway set fixed IP”s in my router on all BLI Stuff, why don”t you set it fixed Tassos? Saves hassle and you know where to look.

I have set a fixed IP on my router since the last time you proposed. In both cases fixed or dhcp enabled I never had issues with the Halo except when I restart the router. My guess (maybe wild) is that the Halo given that it has both 2.4 and 5 GHz wifi connectivity (of which I am not sure), it "switches" bands which does not justify IP change but you might lose a bit of the responsiveness or if you have coverage from two access points at the spot you have it installed it "switches" access point which it could lead to a different IP. I believe that it is a network issue.

beojeff wrote:

I've set static IP addresses for my Halos and the BLI, but the problem of the BLI losing connection with the Halos is still recurring.

I think the issue is not the Halo but the BLI. It crashes or gets onresponsive on all my ipads as soon as open something else and go back to the app. This is also on my BV”s or Beosounds. I just start up the bli app again. I am used to it but it is an issue Which needs to fixed. On the Beolink gateway I never had this issue and was always more stable.

Could be that Tasso his network uses mesh, I had issues as wel but now cabled, my network is really stable, cost a fortune though to get somebody in to fix it. No mesh for me, it sucks.

@tasso, if you have a extensive router with more professional settings you could try and only let you Halo connect to 2.4 or 5 GHZ. I am pretty sure that 2.4 will work better as it has longer range. ( could be under preferences fixed ip of the Halo on your router)

It is a shame i still haven”t got one though. ❓

chucky wrote:

beojeff wrote:

 

I've set static IP addresses for my Halos and the BLI, but the problem of the BLI losing connection with the Halos is still recurring.

 

 

 

I think the issue is not the Halo but the BLI. It crashes or gets onresponsive on all my ipads as soon as open something else and go back to the app. This is also on my BV”s or Beosounds. I just start up the bli app again. I am used to it but it is an issue Which needs to fixed. On the Beolink gateway I never had this issue and was always more stable.

 

 

Could be that Tasso his network uses mesh, I had issues as wel but now cabled, my network is really stable, cost a fortune though to get somebody in to fix it. No mesh for me, it sucks.

 

 

@tasso, if you have a extensive router with more professional settings you could try and only let you Halo connect to 2.4 or 5 GHZ. I am pretty sure that 2.4 will work better as it has longer range. ( could be under preferences fixed ip of the Halo on your router)

 

 

It is a shame i still haven”t got one though. ❓

 

 

Hello chucky,

I never had any issues with my Halo. 🙂

Thanks for the suggestion though.😁

 

Carolpa wrote:

I would try it this way

Make a Resource named "Nest" for example of the type Thermostat and address "1".

 

function(event, engine) 

  local Temp_query=engine.query("your_area/your_zone/THERMOSTAT_2SP/Nest/TEMPERATURE")

  local temp = Temp_query[1].get_number("VALUE")

 

engine.fire("your_zone/your_area/Halo remote/your_Halo/SET_TEXT?BUTTON=497f6eca-6276-4993-bfeb-000000810xxx&TEXT="..tostring(temp))

end

 

But in so far I can look into the Nest/BLI capabilities, I'm not sure it will work. Reading the Help file one should expect it will though.

 

OR try this line instead of the above one

  local Temp_query=engine.query("your_area/your_zone/THERMOSTAT_2SP/Nest/State/TEMPERATURE")

 

Interesting would be to see what happens, what info you get, in Tools/Monitor, when you press the button

 

 

 

Hello Carolpa, I tried both but the return an error in line 5. I played around a bit and tried with the "real" resource as well but no luck.

 

chucky wrote:

beojeff wrote:

 

I've set static IP addresses for my Halos and the BLI, but the problem of the BLI losing connection with the Halos is still recurring.

 

 

 

I think the issue is not the Halo but the BLI. It crashes or gets onresponsive on all my ipads as soon as open something else and go back to the app. This is also on my BV”s or Beosounds. I just start up the bli app again. I am used to it but it is an issue Which needs to fixed. On the Beolink gateway I never had this issue and was always more stable.

 

 

Could be that Tasso his network uses mesh, I had issues as wel but now cabled, my network is really stable, cost a fortune though to get somebody in to fix it. No mesh for me, it sucks.

 

 

@tasso, if you have a extensive router with more professional settings you could try and only let you Halo connect to 2.4 or 5 GHZ. I am pretty sure that 2.4 will work better as it has longer range. ( could be under preferences fixed ip of the Halo on your router)

 

 

It is a shame i still haven”t got one though. ❓

 

 

At any rate, this is still an issue worth brining up to Khimo.