Hi Csongi, As I can see there is a "put-device-state node" as well in the ewelink-cube nodes where you can select the previously registered device, but also not sure how to send over data to these so that iHost will reflect these. I.E. if you configure a switch then with the control device node you can alter the states of this switch, but I cannot figure out how to send temp data over for example. Let me know if you can figure out something on this. Cheers, Istvan
Hi Csongor. I run my home automation on a Smartthings hub but was looking into the possibility of learning Node-Red for more advanced automation but find that the Node-RED plugin that the SmartThings API uses is cloud based. I like the iHost, and can see from your videos that it has possibilities, especially if it bridges with Matter. If I follow your route and buy myself an iHost, will the automations I can learn from your videos in Node-Red on iHost run 100% locally?
Yes, the whatever you run on Node-Red will be running locally on iHost. What I am not sure if you are controlling a wifi device that is integrated to iHost is that a local control or via the cloud.
hi Csongor, at about 30:00 you say you didn't succeed to toggle the new device you just created... i just added a "control device" node, selected the device created in ihost by the node you showed, and as action i select reverse, that's it, i can toggle it now... i connected 1 of these dummy device to a shelly 1 and now i can toggle it (via http requests) via ihost dashboard :D
Yes, I realized that I can use the control device node. And I also figured out how to update some other virtual devices as well. I am planning to make a video on that.
Where are to getting this error? But the sound of it, I am not sure if I would be able to help, I think it is better you ask it in forum dot ewelink dot cc. More experts there.
Hi Varga, I need some help - i got some TRV's from Sonoff - i can't see them in ewelink, but i can see them in Node red, the ideea is simple - when 1 trv needs heat it will start a pump / plug sonoff , and when all trv's are idle ( as they don't have off ) then pump should stop, could you please help me with this
First every time update comes from any of the TRVs, store them in a flow variable using a change node. And either in a function node, or in a series of switch nodes, check all of them flow variables (e.g. switch nodes in series) and if any of them are ON, or all of them are OFF you switch the plug.
Yes, when you start Node-red for the first time, you click "run" and the settings window appears (3:35 min. in the video). The first is Network selection. And in the current version you have a choice: host or bridge. My default was the host and I left it that way. And I don't know what significance it has?
Csongod, did you figure it out how to backup all this stuff??? i mean, when using docker containers, i probably can add an other container which mounts the same volumes and export them someway via rsync or whatever... but the data of the ihost itself, how to save it to be prepared to a device failure, or moving to new one, or just to be safe? there's no export in web gui, but i'd like to have a programmatical way to create a cron job to save all, periodically... i just received it this evening, i may have missed this, beware
Yes, that is a good question, I did not go into those details yet. There is some discussion here, but it is still and open topic: forum.ewelink.cc/t/ihost-backup-function/16662
@@squalazzo we would need somebody who knows his way around docker. I am sure it would be possible to backup and restore a full container. But I am not sure if it can be done from another container. But even resyncing a sizeable zigbee network is a pain. But that is not unique to ihost.
I followed your tip about assigning a static IP address to iHost. But I keep getting 'Failed to connect, Check server settings' Very odd & frustrating. Any help gratefully received.
With the built in eWelink integration, I can pull all my wifi devices into iHost and it can control them locally. There could be a few old devices that are not compatible, or not yet compatible. But it works just fine.
@@philipfeghaly4210 Exactly as you said. And you can delete all the scenes from the ewelink app, just create them in iHost, so they execute locally. The only thing which is not working, is when you pair any Zigbee device to iHost, it does not show up in the ewelink app, so you cannot control it when you are away.
Hi Csongi,
As I can see there is a "put-device-state node" as well in the ewelink-cube nodes where you can select the previously registered device, but also not sure how to send over data to these so that iHost will reflect these. I.E. if you configure a switch then with the control device node you can alter the states of this switch, but I cannot figure out how to send temp data over for example. Let me know if you can figure out something on this.
Cheers,
Istvan
OK, I will definitely cover this if I find it out.
Hi Csongor. I run my home automation on a Smartthings hub but was looking into the possibility of learning Node-Red for more advanced automation but find that the Node-RED plugin that the SmartThings API uses is cloud based.
I like the iHost, and can see from your videos that it has possibilities, especially if it bridges with Matter. If I follow your route and buy myself an iHost, will the automations I can learn from your videos in Node-Red on iHost run 100% locally?
Yes, the whatever you run on Node-Red will be running locally on iHost. What I am not sure if you are controlling a wifi device that is integrated to iHost is that a local control or via the cloud.
hi Csongor, at about 30:00 you say you didn't succeed to toggle the new device you just created... i just added a "control device" node, selected the device created in ihost by the node you showed, and as action i select reverse, that's it, i can toggle it now... i connected 1 of these dummy device to a shelly 1 and now i can toggle it (via http requests) via ihost dashboard :D
Yes, I realized that I can use the control device node. And I also figured out how to update some other virtual devices as well. I am planning to make a video on that.
@@csongorvarga waiting for it! ❤️
Can you please help me. I keep getting this error:
AxiosError: Request failed with status code 500
Where are to getting this error? But the sound of it, I am not sure if I would be able to help, I think it is better you ask it in forum dot ewelink dot cc. More experts there.
Hi Varga, I need some help - i got some TRV's from Sonoff - i can't see them in ewelink, but i can see them in Node red, the ideea is simple - when 1 trv needs heat it will start a pump / plug sonoff , and when all trv's are idle ( as they don't have off ) then pump should stop, could you please help me with this
First every time update comes from any of the TRVs, store them in a flow variable using a change node. And either in a function node, or in a series of switch nodes, check all of them flow variables (e.g. switch nodes in series) and if any of them are ON, or all of them are OFF you switch the plug.
Hi, after installation, I ran Node-red as "host" and not as "bridge". Can you tell me what the difference is and whether it should be changed?
Node-Red? Are you sure? You mean use iHost as a host or bridge?
Yes, when you start Node-red for the first time, you click "run" and the settings window appears (3:35 min. in the video). The first is Network selection. And in the current version you have a choice: host or bridge. My default was the host and I left it that way. And I don't know what significance it has?
@@mateuszsala5531 Oh yes that screen. it was never really explained for me what the difference it. I always use it on the default setting.
Csongod, did you figure it out how to backup all this stuff??? i mean, when using docker containers, i probably can add an other container which mounts the same volumes and export them someway via rsync or whatever... but the data of the ihost itself, how to save it to be prepared to a device failure, or moving to new one, or just to be safe? there's no export in web gui, but i'd like to have a programmatical way to create a cron job to save all, periodically... i just received it this evening, i may have missed this, beware
Yes, that is a good question, I did not go into those details yet. There is some discussion here, but it is still and open topic: forum.ewelink.cc/t/ihost-backup-function/16662
@@csongorvarga thanks, I'll take a look
@@csongorvarga i added my concerns in that thread right now, let's see... almost 1 year and still nothing...
@@squalazzo we would need somebody who knows his way around docker. I am sure it would be possible to backup and restore a full container. But I am not sure if it can be done from another container. But even resyncing a sizeable zigbee network is a pain. But that is not unique to ihost.
@@csongorvarga let's do it :) tell me where we can talk more in depth, discord or whatever, i'm in :)
Hi. Are you currently running 2 nodered server?
Will it be wise to run nodered on ihost and also in another server on the same home?
I am planning to do iHost specific code on the ihost. But I think either way works. And no issues having two instance on the same network.
I followed your tip about assigning a static IP address to iHost. But I keep getting 'Failed to connect, Check server settings' Very odd & frustrating. Any help gratefully received.
And if you check the settings on the iHost what is the ip?
Success. Operator error! Early days, still learning. Thanks.
i have problem with ihost in homeassistant node-red
And what is the issue?
hello , all my devices are wifi, should i buy the Ihost ? i dont want to deal with home assistant . just want a local dashboard
With the built in eWelink integration, I can pull all my wifi devices into iHost and it can control them locally. There could be a few old devices that are not compatible, or not yet compatible. But it works just fine.
@@csongorvarga so to control my house locally i use ihost & for when im not in my home i can still use ewelink app ? or its one or the other ?
@@philipfeghaly4210 Exactly as you said. And you can delete all the scenes from the ewelink app, just create them in iHost, so they execute locally. The only thing which is not working, is when you pair any Zigbee device to iHost, it does not show up in the ewelink app, so you cannot control it when you are away.