hassio_addons icon indicating copy to clipboard operation
hassio_addons copied to clipboard

Ver. 0.1.18b is not reporting any values to MQTT but receiving messages from the weather station

Open convicte opened this issue 1 year ago • 16 comments

I've tried with both whitelisting enabled and disabled. No difference. Downgrading to 0.1.17b corrects the issue and the sensors are updated again, though I had to reboot the VM running the HA for this to take effect, because the HA restart didn't work.

image

image

image

image

convicte avatar May 19 '23 09:05 convicte

After downgrade to 0.1.17b

image

convicte avatar May 19 '23 09:05 convicte

I am also having this same issue.

gregsawatzky avatar May 19 '23 15:05 gregsawatzky

After doing a reboot of Home Assistant (not just a restart), everything is working with version 0.1.18b.

gregsawatzky avatar May 19 '23 15:05 gregsawatzky

No mater how many times I restarted HA or the whole VM the HA works from, this never made a difference. The issue persisted across reboots.

convicte avatar May 19 '23 16:05 convicte

If you log into the Mqtt server using something like mqtt explorer do you see it updating? In Mqtt explorer it would come across as flashes if you were just watching at a high level.

That log make it look like it's sending it to Mqtt. But I wonder if the topic got weird.

You should have two pics for each device. One under the rtl_433 which is the raw data. And one under the home assistant topic/sensor which will have each device and under each device all the separate entities. The one under the homeassisnt topic should have the typical Mqtt device config with a state topic that points back to the the correct rtl_433 topic.

Just trying to figure out where it's breaking down, because the log says it is sending the config to home assistant. Once the config is in MQTT then the device is getting its data from that device data that is sent to rtl_433.

thejeffreystone avatar May 20 '23 03:05 thejeffreystone

I think I'm going to back out some of the changes. I dont think they are going to make a difference anyway.

thejeffreystone avatar May 20 '23 03:05 thejeffreystone

Same here with version: 0.1.19 The puzzling issue is that topics from Oregon (-R 12) are coming thru correctly i.e. from MQTT explorer, values from rtl433 > homeassistant > HA GUI , all ok. Whereas, topics from Fine Offset (-R 32) are NOT. i.e. from MQTT explorer, values from rtl433 (shown ok) > homeassistant (topics created but not updated ) > HA GUI shows 'Unknown'. Previously with 0.1.17 all was ok. (not sure about 0.1.18)

CINCIN365 avatar May 21 '23 16:05 CINCIN365

Same problem with version: 0.1.19

rusnak666 avatar May 21 '23 16:05 rusnak666

Similar to @CINCIN365 above - the only thing working was my ThermoPro temperature sensor (“Prologue TH” in rtl_443 terms), but Acurite and Fineoffset sensors were not working. Neither was my water meter (Badger Orion). I reverted to my backup of 0.1.15b, which was the version I was previously using, and all is well.

baf avatar May 22 '23 00:05 baf

Same issues with ver 0.3.21 of Acurite to Home Assistant. No updates for about a week now. How do I revert back to a previous version?

brandon-meadows avatar May 24 '23 23:05 brandon-meadows

I'm having the same issue with some moisture sensors and a rain gauge. I even tried deleting one of the MQTT devices just to see how it handled it, and then it did get recreated like a new device, but it still shows unknown for the values. Any way to roll back without a backup? My last backup of this has fallen off, so I can't do anything but sit and wait.

wljohnson05 avatar May 30 '23 03:05 wljohnson05

My sensors did this aswell, the problem was because of the auto discovery defaulted to channel 'A' instead of '0' but the entry.sh still defines '0' as default. Could this be the problem for you others aswell?

(I made a pull request for fixing this but messed up totally and accidentally closed it aswell: https://github.com/thejeffreystone/hassio_addons/pull/49)

slappare avatar May 30 '23 12:05 slappare

My sensors did this aswell, the problem was because of the auto discovery defaulted to channel 'A' instead of '0' but the entry.sh still defines '0' as default. Could this be the problem for you others aswell?

(I made a pull request for fixing this but messed up totally and accidentally closed it aswell: #49)

I do see a lot of the entities using that A in the raw rtl_433 state topic. Example: state_topic: rtl_433/Fineoffset-WH51/*******/A/battery_ok

wljohnson05 avatar May 30 '23 13:05 wljohnson05

@thejeffreystone is this channel update something that needs to be rolled back to get this working, or is there something we need to change to make it work correctly now?

wljohnson05 avatar May 31 '23 18:05 wljohnson05

@thejeffreystone I think mine is the same issue with channel 'A' for Acurite and Fineoffset. Any update? I don't know how to back out to a previous version.

Edit/Update: I forked your repo and changed entry.sh to channel 'A' instead of '0', as @slappare suggested, and my Acurite and Fineoffset sensors started updating again.

brandon-meadows avatar Jun 03 '23 12:06 brandon-meadows

Added a new pull request since I messed up the last one: https://github.com/thejeffreystone/hassio_addons/pull/54

slappare avatar Jun 07 '23 08:06 slappare