search

thejeffreystone / hassio_addons

Apache License 2.0
48 stars 29 forks source link

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

Open convicte opened 1 year ago

convicte commented 1 year ago

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 commented 1 year ago

After downgrade to 0.1.17b

image

gregsawatzky commented 1 year ago

I am also having this same issue.

gregsawatzky commented 1 year ago

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

convicte commented 1 year ago

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.

thejeffreystone commented 1 year ago

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 commented 1 year ago

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

CINCIN365 commented 1 year ago

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)

rusnak666 commented 1 year ago

Same problem with version: 0.1.19

baf commented 1 year ago

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.

brandon-meadows commented 1 year ago

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?

wljohnson05 commented 1 year ago

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.

slappare commented 1 year ago

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)

wljohnson05 commented 1 year ago

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 commented 1 year ago

@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?

brandon-meadows commented 1 year ago

@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.

slappare commented 1 year ago

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