You just need to add an Alexa or Google Assistant paletteâ in Node Red. Node Red can be installed just as they describe here. I canât remember the name of the one I found that worked well enough so you might need to investigate a few (there are a fair few).
The Google Assistant one I have just acts like a intermediary so you add the connection for the intermediary in google home and this is just a small program on a cloud server which then connects to your Node Red (likely on the iHost).I think the Alexa connection might be more direct. It works fine. It is just a pain to set up.
Please Note, when using the Alarm function of the iHost, when updating the new version the alarm is triggered (due to a lost Zigbee connection??)
This is very annoying as I am remotely performing the update!
Hi @ward .
I have the same problem as salvo80.Today I also did a hard reset of iHost and reconfigured everything but I donât see any options to update to 1.13.2.
Please support me because I keep having to redefine devices via matter every few days and itâs becoming unbearable.
A possible cause is due to your ISP/proxy service. Can you please try to use other internet services and wait at least 5 mins after it successfully boots up.
It could clear potential problems with broken connections between our update servers and your devices.
@ward And what should I do? Unplug the ihost and go ask some neighbors? No, I have no way of trying elsewhere ISP. If ihost supported the wifi connection I could try from mobile⊠but I know that canât be connected to a wifi network.
@salvo80 which ISP provider do you have? I have TIM (te lo chiedo giusto per evitare giri inutili).
@liberaccio i also have TIM but i dont think the problem reside in the isp, i will try to disble pihole on my main server⊠but really is the only device that have problem in my network⊠also, imho, you should be able to download and install the firmware⊠like⊠almost all the device i have. fingercrossed.
Hi @salvo80 , What kind of router you have I have Unify UDM its security IPS automatically created two rules blocking inbound and out to iHost when had IPS set to highest. I had to enabled those to get update come to my iHost. It is more than likely this is the cause if the only device having issue. Hope this help do check and let other know if this is the case. If you have pihole you can check in the blocking logs and enable the connection by whitelist iHost IP
hi @kuru.kanagalingam , thk for your feedback, i own a frizt box. i cant find any rules that block ihost⊠btw it seem that the people who cant see the update increasing in the forum.
Sorry you and others still having the issue. I had same issue it was stuck on 1.6.3 and not much help here so that why I try to help with my experience. So other thing you can try Wireshark and see what happening to the traffic. Ideally it would be easier if we know what IP or domain to white list.
hi @kuru.kanagalingam .
As @salvo80, I also have a Fritz in cascade. However, yesterday I connected the ihost to the main modem, first with low firewall and then directly in dmz. Nothing has changed.The problem does not seem to be solvable by changing settings in our devices.
The only solution here is to get REAL support from the developers. So far I have only read âIâm sorryâ or âMay beâ but no concrete action.
@ward I work in IT too⊠and with similar mistakes (you removed an update mode without being sure whether the new one will work) I would have already lost my job. Can you put forward a resolution plan? In the last two months I have had to reconfigure everything about twenty times now. Before relying on ihost I had no problems for the last 8 years.
We are customers not testers. Please keep this in mind.
@ward
hi, i tried various things w/o any visible results. knowing the ip of the server would be of great help if the problem is some kind of âbroken connectionâ. First of all may u, at least, confirm what @Alexie (if i remember well) said in another post that ihost search for update only once a day at 12 pm? if that the case all our effort are meaninglessâŠ
Btw i also agree that with @liberaccio, one shoudnt remove an update system that works with one you are not sure it will work for all (at least let them coexist for a whileâŠ).
thk for your work and time.
Best regards
Salvo
I do believe that the pre 1.13.x versions still have to be updated by linking the eWeLink and my experience of updating from 1.6.3 from eWeLink to 1.13.2. Also my experience not ideal for any users as the error message not really reflect any meaningful way. Only using my experience in dealing with issue like I was able to fix mine. SonOff team do need to create FAQ updated with some of this information users experienced since iHosts release. What I see in the FAQ is well outdated information.
This is supposed to be an easy procedure?