Home Assistant beginners

b0rn2sk8 · 16 Apr 2024 at 18:35

Thanks Katie, what’s the best way you’d suggest to roll back?

katie279 · 16 Apr 2024 at 19:14

Hmm, sorry just checked and it looks like a bit of a pain - know integrations has been radically improved in recent times, so was thinking of that (just click and choose version). Forgot GivTCP was an add-on, so its a bit of a pain/messy process - basically uninstall, download version from GitHub and install locally - not ideal.

Might be worth posting your bug in the GivTCP GitHub first and see what the Devs say?

Pickers · 16 Apr 2024 at 20:27

GivTCP requires MQTT and stuff too - have you checked that all the 'pathways' are clear?? By that I mean that the required add-ons are still functional too?

b0rn2sk8 · 16 Apr 2024 at 20:29

I'm not seeing any errors related to Mosquito MQTT, I'd have thought that would show up in the logs instead of the addon just quitting within a few seconds of being launched?

Pickers · 16 Apr 2024 at 21:54

b0rn2sk8 said:
I'm not seeing any errors related to Mosquito MQTT, I'd have thought that would show up in the logs instead of the addon just quitting within a few seconds of being launched?

You are probably right - just thinking of all possible weak links.
I use it too - haven't updated to latest version yet so am going to hold off.

b0rn2sk8 · 16 Apr 2024 at 21:55

The mystery continues -

I just went to re-install GivTCP and HA threw the following error:

Can't install britkat/giv_tcp-ma:2.4.3: 500 Server Error for http+docker://localhost/v1.44/images/create?tag=2.4.3&fromImage=britkat%2Fgiv_tcp-ma&platform=linux%2Farm64: Internal Server Error ("Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout")

This was showing in the HA Core Log

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 20:40:07 (2 occurrences)
Last logged: 21:23:17

Failed to to call /addons/a6a2857d_givtcp/install - Can't install britkat/giv_tcp-ma:2.4.3: 500 Server Error for http+docker://localhost/v1.44/images/create?tag=2.4.3&fromImage=britkat%2Fgiv_tcp-ma&platform=linux%2Farm64: Internal Server Error ("Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout")
Failed to to call /addons/a6a2857d_givtcp/options -

I now got it back installed and then when I went to set the config I got this error:

Failed to save add-on configuration, Unknown error, see supervisor logs

Nothing was in the logs, When I hit save again, it saved.

In any case GivTCP seems to be up and running now - not sure what I did other than uninstall it, reboot the Pi, and install it again while encountering all the above errors.

However, the data is now not showing up in MQTT, I don't really have time to mess around with it tonight so its now a job for another day.

Pickers · 16 Apr 2024 at 22:02

Ah a pi.

I used to get quite a lot of issues with pi - as in the GivTCP would stop updating sensors and the only way to get it back working was a reboot.

I never checked logs but (and I touch wood here) since moving my HA to hyper V on a micro pc, it's had 100% uptime.

I'm not saying it's the pi but it's possible. Are you using an SD card or an SSD?

b0rn2sk8 · 16 Apr 2024 at 22:13

SD card - given the issues I am having, a dodgy SD card is on the list of things to check....

dlockers · 16 Apr 2024 at 22:25

Yeah I migrated from Pi -> VirtualBox -> native Windows box. I kept getting too many oddities on Pi with SD (Peugeot app specifically).

b0rn2sk8 · 16 Apr 2024 at 22:41

I’ve got an unraid NAS I could host it on within a VM if push came to shove.

Edit: its got plenty of spark resources it’s running on a 6 core 5820k and has 16gb ram.

Bluecube · 16 Apr 2024 at 22:51

If you still want to use a Pi then pair it with a SSD. However, Unraid will run HA just fine. I ran HAOS for years as an Unraid VM before recently moving it to Proxmox

katie279 · 16 Apr 2024 at 23:37

Ah, yes had the same thought tonight - ie were you using pi and with SD card. No issues with Pi (I've used one for years with zero issues), but SD cards really aren't meant for long time server-like use. I had similar saving errors on a different bot of software once, I suspect the SD card is starting to bork. SSD solved it for me...!

valve90210 · 17 Apr 2024 at 09:47

Does anyone have any recommendations for decent, battery powered zigbee motion sensors? I've been using Sonoff SNZB-03 sensors but out of the three I've purchased, two have died on me in under a year and the other one has fairly regular incidents of dropping off the network which is very frustrating.

I've done a good bit of reading and know a lot of people recommend Hue sensors but I'm reluctant to spend so much per sensor! I would go for something like the ESP Lite but neither of the areas I want sensors have power accessible so battery it has to be.

dlockers · 17 Apr 2024 at 09:53

@aVdub just bought some TP Link ones but not sure if they are zigbee.

Do you have any old Alexa shows?

They can do motion IIRC.

I just ended up swallowing the bill - I have 1 outdoor Hue, and 4 indoors (hall, WC, kitchen, bathroom).

the-evaluator · 17 Apr 2024 at 09:58

the-evaluator said:
Something I've been toying with for a while, but really need to get off my arse and see if I can get it working - different coloured lights depending on which recycling bin needs to go out.

Our recycling collection alternates, blue bin one week, red the next. Collection day is Tuesday. I'd like an LED strip to power on some time on Monday afternoon and be either red, or blue. I've got a Govee LED strip setup in HomeAssistant with the appropriate scripts and automations to set the colour of the strip. I've already setup Waste Collection Schedule so I have a calendar that knows which bin needs to go out.

The missing piece is setting the light to come up, with the right colour and the right time.

With some pointers from one of the UK Home Assistant Facebook communities I've had this working for a few months and it's superb!

5pm on Monday evening an LED strip in the kitchen turns on either red, or blue. The strip then turns off when I start the going to bed routing via Alexa or if that doesn't get triggered (if we're away for example) then it gets turned off at 22:00.

A simple thing, but I'm really happy with it.

aVdub · 17 Apr 2024 at 10:07

dlockers said:
@aVdub just bought some TP Link ones but not sure if they are zigbee.

Do you have any old Alexa shows? They can do motion IIRC.

I just ended up swallowing the bill - I have 1 outdoor Hue, and 4 indoors (hall, WC, kitchen, bathroom).

Which ones - Camera - sensor?

I do have Alexa shows, but use the TP Link app to view camera's and sensors when away from home, although I do use them now and then to view front and rear cameras.

Sensors and pir I have set to automate things are certain times or away, which can also be set to switch on internal cameras.

valve90210 · 17 Apr 2024 at 10:40

aVdub said:
Which ones - Camera - sensor?

I do have Alexa shows, but use the TP Link app to view camera's and sensors when away from home, although I do use them now and then to view front and rear cameras.

Sensors and pir I have set to automate things are certain times or away, which can also be set to switch on internal cameras.

I was asking about zigbee motion sensors, dlockers was saying you'd recently purchased some tplink ones, are they zigbee based?

Bluecube · 17 Apr 2024 at 10:48

The best Zigbee motion sensors in my experience are the Philips Hue ones. Cost a lot but they’re rock solid and have never let me down. Batteries last forever too.

aVdub · 17 Apr 2024 at 11:21

valve90210 said:
I was asking about zigbee motion sensors, dlockers was saying you'd recently purchased some tplink ones, are they zigbee based?

OIC

They connect together via the SubG protocol.

b0rn2sk8 · 17 Apr 2024 at 19:46

In a further update to my GivTCP saga, last night I mentioned that I had got GivTCP working but nothing was showing up in MQTT.

Randomly today all the devices connected, passed one packet of data and disconnected again.

2024-04-17 08:28:20: New connection from 172.30.32.1:35877 on port 1883.
2024-04-17 08:28:21: Client <unknown> closed its connection.
2024-04-17 08:28:21: New connection from 172.30.32.1:43969 on port 1883.
2024-04-17 08:28:21: New client connected from 172.30.32.1:43969 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:28:22: New connection from 172.30.32.1:33139 on port 1883.
2024-04-17 08:28:22: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:28:23: Client <unknown> closed its connection.
2024-04-17 08:28:23: New connection from 172.30.32.1:57869 on port 1883.
2024-04-17 08:28:23: New client connected from 172.30.32.1:57869 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:28:24: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:29:01: New connection from 172.30.32.1:41307 on port 1883.
2024-04-17 08:29:02: Client <unknown> closed its connection.
2024-04-17 08:29:02: New connection from 172.30.32.1:51667 on port 1883.
2024-04-17 08:29:02: New client connected from 172.30.32.1:51667 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:29:02: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:29:40: New connection from 172.30.32.1:52701 on port 1883.
2024-04-17 08:29:41: Client <unknown> closed its connection.
2024-04-17 08:29:41: New connection from 172.30.32.1:56435 on port 1883.
2024-04-17 08:29:41: New client connected from 172.30.32.1:56435 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:29:42: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:30:26: New connection from 172.30.32.1:42669 on port 1883.
2024-04-17 08:30:27: Client <unknown> closed its connection.
2024-04-17 08:30:27: New connection from 172.30.32.1:43585 on port 1883.
2024-04-17 08:30:27: New client connected from 172.30.32.1:43585 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:30:27: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:31:05: New connection from 172.30.32.1:39551 on port 1883.
2024-04-17 08:31:06: Client <unknown> closed its connection.
2024-04-17 08:31:06: New connection from 172.30.32.1:40499 on port 1883.
2024-04-17 08:31:06: New client connected from 172.30.32.1:40499 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:31:06: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:31:44: New connection from 172.30.32.1:43053 on port 1883.
2024-04-17 08:31:45: Client <unknown> closed its connection.
2024-04-17 08:31:45: New connection from 172.30.32.1:58625 on port 1883.
2024-04-17 08:31:45: New client connected from 172.30.32.1:58625 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:31:45: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:32:23: New connection from 172.30.32.1:48861 on port 1883.
2024-04-17 08:32:24: Client <unknown> closed its connection.
2024-04-17 08:32:24: New connection from 172.30.32.1:47937 on port 1883.
2024-04-17 08:32:24: New client connected from 172.30.32.1:47937 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:32:24: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:33:02: New connection from 172.30.32.1:49299 on port 1883.
2024-04-17 08:33:03: Client <unknown> closed its connection.
2024-04-17 08:33:03: New connection from 172.30.32.1:52273 on port 1883.
2024-04-17 08:33:03: New client connected from 172.30.32.1:52273 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:33:03: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:33:41: New connection from 172.30.32.1:34697 on port 1883.
2024-04-17 08:33:42: Client <unknown> closed its connection.
2024-04-17 08:33:42: New connection from 172.30.32.1:56321 on port 1883.
2024-04-17 08:33:42: New client connected from 172.30.32.1:56321 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:33:42: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:34:22: New connection from 172.30.32.1:39047 on port 1883.
2024-04-17 08:34:23: Client <unknown> closed its connection.
2024-04-17 08:34:23: New connection from 172.30.32.1:40453 on port 1883.
2024-04-17 08:34:23: New client connected from 172.30.32.1:40453 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:34:24: Client GivEnergy_GivTCP_1 disconnected.
2024-04-17 08:35:02: New connection from 172.30.32.1:35459 on port 1883.
2024-04-17 08:35:03: Client <unknown> closed its connection.
2024-04-17 08:35:03: New connection from 172.30.32.1:42951 on port 1883.
2024-04-17 08:35:03: New client connected from 172.30.32.1:42951 as GivEnergy_GivTCP_1 (p2, c1, k60, u'homeassistant').
2024-04-17 08:35:03: Client GivEnergy_GivTCP_1 disconnected.

2024-04-17 19:37:53,526 - Inv1 - read - [DEBUG ] - ----------------------------Starting----------------------------
2024-04-17 19:37:53,528 - Inv1 - read - [DEBUG ] - Getting All Registers
2024-04-17 19:37:53,528 - Inv1 - read - [DEBUG ] - Connecting to: 192.168.1.71
2024-04-17 19:37:53,532 - Inv1 - queue - [DEBUG ] - Pushed job 8d3a2f1f-043b-4771-9f9b-4ac99088d190 into GivTCP_1
2024-04-17 19:37:54,112 - Inv1 - sync - [DEBUG ] - Connection to Modbus server established. Socket ('192.168.1.84', 45827)
2024-04-17 19:37:54,114 - Inv1 - transaction - [DEBUG ] - Current transaction state - IDLE
2024-04-17 19:37:54,114 - Inv1 - transaction - [DEBUG ] - Running transaction 1
2024-04-17 19:37:54,116 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:54,267 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:54,269 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:54,271 - Inv1 - transaction - [DEBUG ] - Adding transaction 1
2024-04-17 19:37:54,272 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:54,775 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:54,775 - Inv1 - transaction - [DEBUG ] - Running transaction 2
2024-04-17 19:37:54,779 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:54,932 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:54,934 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:54,937 - Inv1 - transaction - [DEBUG ] - Adding transaction 2
2024-04-17 19:37:54,938 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:55,441 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:55,441 - Inv1 - transaction - [DEBUG ] - Running transaction 3
2024-04-17 19:37:55,442 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:55,598 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:55,600 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:55,602 - Inv1 - transaction - [DEBUG ] - Adding transaction 3
2024-04-17 19:37:55,603 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:56,105 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:56,106 - Inv1 - transaction - [DEBUG ] - Running transaction 4
2024-04-17 19:37:56,109 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:56,258 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:56,260 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:56,262 - Inv1 - transaction - [DEBUG ] - Adding transaction 4
2024-04-17 19:37:56,263 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:56,765 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:56,766 - Inv1 - transaction - [DEBUG ] - Running transaction 5
2024-04-17 19:37:56,767 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:56,927 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:56,929 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:56,931 - Inv1 - transaction - [DEBUG ] - Adding transaction 5
2024-04-17 19:37:56,932 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:57,435 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:57,436 - Inv1 - transaction - [DEBUG ] - Running transaction 6
2024-04-17 19:37:57,439 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:57,595 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:57,596 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:57,603 - Inv1 - transaction - [DEBUG ] - Adding transaction 6
2024-04-17 19:37:57,604 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:58,106 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:58,107 - Inv1 - transaction - [DEBUG ] - Running transaction 7
2024-04-17 19:37:58,109 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:37:58,272 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2024-04-17 19:37:58,275 - Inv1 - payload - [DEBUG ] - [b'\x00\x00', b'\x00\x00', b'\x00\x00', b'\x00\x8a']
2024-04-17 19:37:58,277 - Inv1 - transaction - [DEBUG ] - Adding transaction 7
2024-04-17 19:37:58,278 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2024-04-17 19:37:58,780 - Inv1 - transaction - [DEBUG ] - Current transaction state - TRANSACTION_COMPLETE
2024-04-17 19:37:58,781 - Inv1 - transaction - [DEBUG ] - Running transaction 8
2024-04-17 19:37:58,784 - Inv1 - sync - [DEBUG ] - New Transaction state 'SENDING'
2024-04-17 19:38:00,787 - Inv1 - transaction - [DEBUG ] - Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'

Something very funky is going on here.

I might just nuke it and start over.