Thx for the logs, our dev will look into them during the day (3am here)
Also we just released a patch V2.3.2 to fixed issues we can restore and identify the cause.
Please check the update log and a detailed explanation post:
I just updated to 2.3.2. logs are back. Still no Actions in device control. Seems like it is just me.
New logs sent from just after try.
Thanks for the follow up, will get back to you soon
noticed this warning
âMaxListenersExceededWarningâ
perhaps it is this. I have access to settings file to create password so, I think, can amend maximum, although sensors seem to be working.
Did the new log help at all?
Incidentally, I have Node Red also on a Raspberry Pi running Home Assistant. It also has no Actions in the Control Device Node despite running 1.3.1 of the palette Iâm going to go through all my flows there and delete any EWeLink nodes (as I donât think there are many) so I can delete and reinstall the eWeLink palette.
That didnât work. Now I donât even have a Control Device Node.
See photo of installed nodes. If I look in palette manager it says there is a control device node. Iâm installing the 1.31 that was updated 3 days ago so Iâm pretty certain this is the right palette.
The Docker Node Red is 2.0.5 whilst the Home assistant Node Red is 2.0.3.
I guess that rules out Node Red or a corrupted NR eWeLink Palette. My guess is that the iHost is serving the Palette to the HA using only in July memory so we k ow it isnât the TF card and there was no control node before I got a ticket from the iHost. I guess that there being no Control Node even before any interaction of the new palette with the iHost means it canât be the iHost at all and must be the NR Palette 1.3.1
deleted and reinstalled your palette
here are the NR latest logs
25 Oct 23:48:09 - [info] Uninstalling module: node-red-contrib-ewelink-cube
25 Oct 23:48:12 - [info] Uninstalled module: node-red-contrib-ewelink-cube
25 Oct 23:48:12 - [info] Removed node types:
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:api-server
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:get-devices
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:event-state
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:event-online
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:control-device
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:event-add-device
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:event-del-device
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:event-device-info
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:put-device-state
25 Oct 23:48:12 - [info] - node-red-contrib-ewelink-cube:register-device
25 Oct 23:48:12 - [info] Removed plugins:
25 Oct 23:49:20 - [info] Installing module: node-red-contrib-ewelink-cube, version: 1.3.1
25 Oct 23:49:26 - [info] Installed module: node-red-contrib-ewelink-cube
gatewayInfoMap----------- Map(2) {
âda81a31180ae2a3eâ => {
deviceid: â1001de90ecâ,
ip: â192.168.0.238â,
mac: âd0:27:03:33:e1:aaâ,
ethernet_ip: â192.168.0.238â,
ethernet_mac: âd0:27:03:33:e1:aaâ,
domain: âihost.localâ,
fw_version: â2.3.2â,
name: âiHostâ,
isV2: true
},
âf2d03366bf385df9â => {
deviceid: â1001de90ecâ,
ip: â192.168.0.238â,
mac: âd0:27:03:33:e1:aaâ,
ethernet_ip: â192.168.0.238â,
ethernet_mac: âd0:27:03:33:e1:aaâ,
domain: âihost.localâ,
fw_version: â2.3.2â,
name: âiHostâ,
isV2: true
}
}
NB, although it can see the iHost (twice with Same IP & MAC) I have not interacted at all with iHost.
Weâve checked the log.
It only recorded for 2 mins and has 84 successful control device request.
And nothing worng about the control device log.
Please try open the inspect tools of browser then reproduce the problem with the network section open.
Record a video or take a screenshot.
So we can pinpoint the problem more correctly.
And send us the full node-red log after the record.
Here is an example for the screenshot:
Thank you very much for your patience.
I now have two node Red places with the eWeLink palette installed.
- Raspberry Pi 4 and Home Assistant, but no Device Control node at all (see photo above)
- iHost, with Device Control Node, but lots more flows to create noise
Plus I have tried multiple browsers
- Microsoft Edge (default)
- Firefox
- Google Chrome
Which device do you want used and which browser?
If all the devices shows no action like you mentioned before.
Then there is no limit for the choice of device.
As for the choice of browser, chrome would be fine.
I created a new flow and only have a Device control node on it. This is a page with iHost node Red only, not a nested window from the iHost.
Oddly there are actions in Google Chrome, but not (Iâve double checked now) in Microsoft Edge or Mozilla Firefox.
That includes virtual devices as-well as real devices.
There is a toggle button instead of on/off like I saw before.
We did reproduce the problem with the Ghostery Tracker and Add blocker extention enable in Edge.
It blocks a file with only 100 lines code.
We also very curious about why.
As we are addressing the problem, please put your node-red page in the white list of the blocker, that would fix the problem for now.
I turned off the âGhostery Tracker and Add blockerâ extension to Edge and now actions appear, but thatâs not a new extension. Iâve had it for years.
I wonder what changed in how the Device Cobtrol node is coded that the Ghostery extension thinks device control actions are a tracker or add⌠maybe it updated but normally it asks for money when it does so with a splash screen.
We did reproduce the problem with Ghostery Tracker and Add blocker extension enable in Edge.
It blocks a file with just 100 lines of code.
We also very curious about why.
While we addressing the problem, please put your node-red page into the white list in your blocker for now.
Ghostery is an open source extension. I think they have a browser based on Firefox too. This is the Github:
https://github.com/ghostery
@@/resources/node-red-contrib-ewelink-cube/components/thermostat.js
Please can add the above content to custom filters as following the steps below:
- Click Ghostery icon to open popup
- Click three horizontal lines at top-right
- Click âPrivacy protectionâ
- Look for âCustom filtersâ and enable it
- Paste the above content and click save button
- Wait until save button to be activated, then reload the problematic webpage
Then the problem will be solved for now.
We already file an issue to the ghostery team and will wait for their fix.