search

maxinminax / node-mihome

Control Mi Home devices, such as Mi Robot Vacuums, Mi Air Purifiers, Mi Smart Home Gateway (Aqara) and more
MIT License
121 stars 35 forks source link

Flows stopped due to missing node types. mihome-cloud #39

Open QuocurIQ opened 3 years ago

QuocurIQ commented 3 years ago

node 15.14.0 node-red 0.20.5 node-red-contrib-mihome 1.0.1

After installation from pallete manager I can't see the mi home cloud node, as shown in the images in the description. The config node, when I double-click on the mihome devices is always empty, when I try to update it.

BOOMER74 commented 3 years ago

You seem to be on the wrong package 😄 You need node-red-contrib-mihome.

mihome-cloud it's a config node and it's don't showing on nodes list. You need to open devices node and configure Cloud field.

QuocurIQ commented 3 years ago

Hello.

Thank you for your valuable input. So do I have to download the package from github? The one in npm/pallete doesn’t work? The github readme says I can use the Palette Manager or npm …...

Steps to reproduce

node-red: 1.32

  1. I install node-red-contrib-mihome from the pallette
  2. I drop the "mihome - devices" node on the flow
  3. I double-click the devices node
  4. I click on the pencil next to the Add new mihome cloud
  5. I edit my login info
  6. I select region de
  7. I click on Update, then Done
  8. I deploy the changes
  9. I get the error message as described

Here a link to a screen recording.

https://youtu.be/OSVTM7CSOsY https://youtu.be/OSVTM7CSOsY

Kind regards

Marek

On 27 Apr 2021, at 22:03, Sergei Novikov @.***> wrote:

You seem to be on the wrong package 😄 You need node-red-contrib-mihome https://github.com/BOOMER74/node-red-contrib-mihome.

mihome-cloud it's a config node and it's don't showing on nodes list. You need to open devices node and configure Cloud field.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/maxinminax/node-mihome/issues/39#issuecomment-827892355, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACMGVGALQQJQ3MU74XDJJ53TK4KBVANCNFSM43DGKARA.

BOOMER74 commented 3 years ago

Please try to reinstall to the last version. I did a clean install of node-red and install package, all works.

node-red

Also, please reopen bug in node-red-contrib-mihome issues.

QuocurIQ commented 3 years ago

Where do I get the latest version? I installed 1.0.2 from the Palette Manager. It seems not to work with node-red 1.32. It even looks weird in the Palette Manager, see attached screenshot.

Screen Shot 2021-04-28 at 07 16 23
QuocurIQ commented 3 years ago

I tried on another instance of node-red:1.0.6 and it works. It's either something with 1.32 or the fact I'm running it in a docker container

Thanks one again for your help.

QuocurIQ commented 3 years ago

Duuude. I just noticed I was on the wrong package :D. Anyways, I got the node-red-contrib-mihome partially working in an older version of node-red. There is a devices node, that gets all the devices, including props, so I can read the measurements from there. But I have a BLE Thermohygrometer. It returns some data, but the props object is missing - compared to the lumi.sensor_ht.v1.
The device model is: miaomiaoce.sensor_ht.t2.

Here is what I'm getting from the devices node (ids and IPs modified):

did: "blt.3.167deadbeef95" token: "D3ADB33FD3ADB33FD3ADB33F" longitude: "0.00000000" latitude: "0.00000000" name: "Device Name" pid: "6" localip: "8.8.8.8" mac: "DE:AD:BE:EF:95:95" ssid: "" bssid: "" parent_id: "" parent_model: "" show_mode: 1 model: "miaomiaoce.sensor_ht.t2" adminFlag: 1 shareFlag: 0 permitLevel: 16 isOnline: true desc: "Device online " extra: object uid: 6665630343 pd_id: 1337 password: "" p2p_id: "" rssi: 0 family_id: 0 reset_flag: 0

What's interesting, is that the localip is my WAN public IP, as opposed to the zigbee sensors, that report the local IP of the mihome gateway ...

How can I help to add support for this device?

Thanks

Regards

Marek

BOOMER74 commented 3 years ago

Hi. miaomiaoce.sensor_ht.t2 should be work with mihome-th-monitor node. You need to use mihome-devices node only to get all devices list and easily find did (device id) field for required device.

QuocurIQ commented 3 years ago

Hi. The mihome-th-monitor always gives me: "Mi Home: TH Monitor: cannot find last data for temperature or humidity"

This happens for the zigbee ones, as well as the BLE. That's why I use the devices node, and extract the measurement from the "prop" property and divide by 100. But the BLE doesn't have a "prop". What's also interesting, that I don't see the battery info in neither of the sensors outputs. But that might be a node-red-contrib-mihome issue. The ht.t2 sensor not having "prop" looks more like node-mihome to me.

Thanks

Regards

Marek

QuocurIQ commented 3 years ago

Hi.

Got the mihome-th-monitor node working for the BLE Sensor, by using the device id also in the Name field of the node. The zigbee sensor still gives me: Mi Home: TH Monitor: cannot find last data for temperature or humidity.

The BLE sensor also doesn't have a parent_id. Could it be that it's connected through my phone, not the gateway? I see it in the BLE child devices on the gateway .... My idea was to determine the location of the sensor by the gateway it's connected to. This way, I wouldn't have to do any changes in node-red to start collecting data from new sensors....

Regards

Marek