search

arjenhiemstra / ithowifi

Itho wifi add-on module (ESP32 wifi to itho I2C protocol)
GNU General Public License v3.0
181 stars 32 forks source link

Monitor only RF Devices not in remotesinfo #213

Closed bartvanraalte closed 8 months ago

bartvanraalte commented 11 months ago

Describe the bug I have a RFT CO2 added to the addon with remfunc "Monitor Only". On the "RF Devices setup" page, the "capabilities" column is filled with the correct information: timestamp:1699130340, lastcmd:11, lastcmdmsg:IthoAuto, co2:481

This information is however not published to the remotesinfo MQTT topic. Also via the API (/api.html?get=remotesinfo) it does not show this remote.

Because I want to use the add-on purely for monitoring purposes, I like to have the remote connected to the Itho directly. The add-on is able to "sniff" the data from the remote perfectly fine, as the data is visible on the webui. I'm now looking for a way to get that data out of the add-on.

To Reproduce Steps to reproduce the behaviour:

  1. Add remote with remfunc "monitor only"
  2. Validate information is added in the "capabilities" column on the webui
  3. Check the /api.html?get=remotesinfo api
  4. Remote is not listed

Expected behaviour I would expect to also see remotes that are in "montor only" mode.

Device information

arjenhiemstra commented 11 months ago

Thanks for reporting this! I'll look into it.

arjenhiemstra commented 8 months ago

I cannot reproduce this in 2.6.0. I have a monitor only device myself and this shows up on MQTT. Could you provide a screenshot of the web interface?

bartvanraalte commented 8 months ago

Does this screenshot help, or are you looking for another page? image

(Note: device with index 1 is out of reach, but the rest do work fine)

bartvanraalte commented 8 months ago

Now see all the remotes on the /api.html?get=remotesinfo endpoint, and also on MQTT. The software version is exactly the same as when I reported the issue, and I didn't change the config. Maybe it only started to work after a restart (powercycle), but that would just be a guess.

bartvanraalte commented 8 months ago

I'll close this ticket, as I was not able to reproduce this anymore on 2.6.0. Now upgraded to 2.7.0, and it still works as expected.