The problem may be that the equipment sometimes takes time to react… So you have to wait.
If you have a door opening sensor, you will immediately see if it works by moving it.
Yes! Thanks, great I plan to do that! 
I’ll need to add the IP address, let’s see if I can retrieve it easily. Thanks!!
I admit it’s taking a while, but what type of device do you have?
By chance @Jacky did you enable developer mode on the gateway??
With Wireshark, can you see the multicast packets arriving on your PC?
Weird anyway … You tell me again with the raspberry pi
If you load the dev seeds in the DB, you should be able to log in with the demo account.
You have a config file to set the server URLs. API http and ws.
Edit: front/config.js
Well… it’s variabilized in a config file. Front and back are two stand-alone apps. So you have to specify to the front where it should hit 
Hi, actually the service is working on your end! A small issue on the front end that I normally fixed, I just need to push everything, it’s my fault!
If you see addTemperature.js in the logs, it means a device has gone through it!
I actually forgot an else in a function on the front end that was causing everything to crash…
So it will be fine, I’ll push as soon as my tests pass and you can test.
@Jacky normally if you pull it, it should work
So pay attention, if the sensor was not added to the database, the values cannot be updated. The sensor must be in the first tab to be created in order to be updated. You often have to wait a second time for it to speak on the network :).
So yes … It’s complicated, I don’t know how to differentiate LOL. I only have information like ‹ sid › …
We would need to link the two and I have no idea how to do that!
I’ll think about it on my side. Otherwise, wait for it to come up and give the temperature and check on the miHome application and compare … 
On my end, it’s the same, the gateway communicates very little with the temperature device
Oh I see that!
Do you have the latest version? Because on my end, I don’t see any issues! I’ll test at home this afternoon with my gateway
I just noticed two bugs:
-
I think devices are being reported multiple times. In the device view, I have more temperature probes and motion detectors than I actually have in the house (a surprise delivery :D).
-
Once a device is deleted from the device view, I can no longer reassign it via the setup view.
Regarding device identification, there is a solution. The SID should be displayed in the setup view. Then, from the mi-home application, you can find out the SID of the devices.
@pierre-gilles, this meets the zwave requirement with the node ID reporting. Could we consider displaying this information somewhere, for example next to the device name or elsewhere:
I think this is not limited to only Xiomi and Zwave, all devices have an ID.
How do you do it? 
I’ll add it!!
Yes, I will do it as quickly as possible.
To note that from Sunday until next Sunday, I will be unavailable (no access to a computer).
I have a small idea about this!
In the Xiaomi configuration page, we could display an indicator (a kind of highlight) on the box of each device when a value has just been reported on a sensor, leaving it for about 1 or 2 seconds.
That way, you just need to open the window and see which one lights up to understand which device is which.
Example in scenarios, when a step is being executed, I highlight the box in blue:
We could do the same on the Xiaomi device box that has just been triggered.
We can add a mention « Last value: 20 seconds ago » as well.