I’ve recently bought an Zigbee MQTT energy sensor (Zemismart SPM01-D2TZ) which is a Zigbee MQTT device. The product is seen and linked to iHost (through zigbee2cube) but is described as “not yet supported”. Since it seems that iHost supports energy meter/sensors I am wondering why it is not supported and if it can be added. Thanks
Hey
As different brands have different modifications to zigbee, we can only support a selected range.
But there’s a big update coming, extending iHost’s compatibility, you can give it a try till then.
For now, if you can still return it, I would recommend so.
Sorry for the inconvenience.
1 Like
Any tentative date?
Sometime in June, but I can not give a solid date.
2 Likes
After the update I can see it without the disclaimer that is not supported however I cannot get any data from the sensor. BTW the sensor is not eWeLink but it supports MQTT which is a very used standard… any idea?
For now you could create a virtual device using the eWeLink palette in Node Red on the iHost, but I haven’t tried creating a virtual power device. NodeRED also has MQTT in so you could map your MQTT readings to the virtual (hopefully) power device you just created. You can definitely create virtual devices with numbers, as I’ve done that. You can also run an MQTT broker in the Docker on the iHost as I tried that and installed mosquito and connected one device to check it worked.
Then in the future when it works fully just delete your virtual device.
A little bit over my knoledge… unless you would like to help me more…
There is no virtual device type available at present.
I tried without success trying to use number fields in other types of virtual device, but in the end this caused problems. The same happened with light sensors.
We need these, and locks, and alarms, as well as others already posted on other threads.
You can create virtual devices of various types and then they appear on the iHost and in Casts, but they tend to be only pre-existing device types. So for instance if you had a light sensor that used MQTT you could make a pretend Temperature sensor on the iHost until they make one themselves.
Here’s an official video on how to create virtual sensors, but the video is just a basic device. Making other sensors is a bit of trial and error. The key bit is to give each device a unique identifier (UUID) using
My guess is that a pretend power one will be relatively easy but I’ve never made one.
1 Like
I’m not on a big screen now and both the iHost and Node Red need big screens but watching the video above at 1:22 there is a smoke alarm device type. Does it not work?
I normally go for temperature for random numbers, but it was not easy to figure out how to get data in and I’ve forgotten how I did it.
Node Red has its own dashboard too (if you add the palette for it). My attempts always looked really ugly though. It adds extra graphing capabilities. If an eWeLink Virtual Device does not work that is how I have done it.
I appeciate you ingenuity but I think that eWeLink should add a energy consumption type to ihost… come one eWeLink!
1 Like
I don’t know why energy is not a virtual capability. Same with target temperature, so you can’t make a virtual radiator valve. I don’t really get why there are missing capabilities that exist in eWeLink for real, but I haven’t perused the options for a while and that video is old.
Also humidity can be used when you need a percentage as @csongor.varga shows on a video on his YouTube channel.
Personally don’t use this, but as these virtual devices show on the Matter bridge in Smartthings, that means they come across in Alexa. Depends on the type but can then be used to trigger routines.
Just checked with our team, the good news is that it’s planed. But I can not guarantee a solid date. More work is needed, as different devices tend to have different ways to calculate the energy entity.
1 Like