Update to 0.10 broke Timer add-on things (now are "disconnected")

WebThings
#1

The good news is don’t have the problems others are reporting. I did have problems but (succinctly) I solved some issues by shutting my Raspberry Pi 3 down totally for ~15 minutes (to fix Zigbee not working at all. And maybe other issues.) I solved time issues in rules by configuring the new localization settings. I have WiFi and Zigbee things. All of them work.

The remaining issue is my Timer things are showing as being disconnected. Any of the rules that use them don’t work now.

Oh, I changed Celsius to Fahrenheit in localization (thanks!) The temperatures now display as Fahrenheit. But editing rules that involve temperatures doesn’t work well. The edit box isn’t working well in rules.

#2

Timer issue should be fixed here: https://github.com/tim-hellhake/timer-adapter/pull/4

As for the Fahrenheit issue in rules, what issue are you seeing exactly?

#3

I also had problems with my timers, but I solved thee issue simply removing and re adding the timers to my rules; I just had a few, so it was doable in a couple of minutes.
Hope this workaround helps someone

#4

I don’t know enough about github to do anything with that fix. I opened timer-adapter.js in an editor to see if I could manually incorporate the code you linked to, but the code in timer-adapter.js was too different from what you linked to.

Since I changed units to Fahrenheit in the new localization window, when I edit the value of a temperature, the change I make immediately turns into random looking numbers in the edit dialog box. No matter if I edit with the keyboard or if I use the up/down arrows to increment/decrement the value.

But if I ignore what is on the screen and blindly, say, use Ctrl-A to select all the text in the temperature dialog, press “del” to delete it all, and then type in the value I want and then exit the edit mode, the correct value is entered. But seeing all the randomish numbers in the editing box is disconcerting.

#5

I’m sure the timer adapter will be updated soon, so you’ll get the fix automatically.

The conversion code for rules was a bit challenging. I’ll look into it and see if I can make things a little better.

#6

I am also seeing the problem with the temp sensors. I am getting mostly all negative numbers, even if I change to a positive number, or manually input the temp number. When using the arrows to change it, I can put it where I want it, but when I release the mouse button it snaps to -11. Same if I manually input the temperature.

#7

Any idea when this will happen? I tried uninstalling and reinstalling the timer addon. And shutting the gateway RaspPi down completely for about a half hour, but after restarting all my timers remain disconnected and inoperable.

For a while, yesterday I think, the timers were shown as disconnected but they (mostly) worked. But this has gone away and for all of today they are disconnected and inoperable.

Also, I determined that I wasn’t using two of my timers. I tried to remove them but they are still there. Ditto for a Zigbee on/off switch that wasn’t working right. I removed it from the gateway, shut the gateway down, removed the battery from the switch, but it won’t go away.

#8

The fix has been released, but since the device IDs had to be changed, you’ll need to remove your old timers from the gateway and re-add them.

#9

Thanks. I did what you said and they work. Adding the visual display of the seconds counting is a nice addition.

But I still have the problem not being able to remove the old timers. And the Zigbee on/off switch that I removed the battery from still can’t be removed.

#10

I also am unable to delete my previous timers. Any way to manually do this?

#11

I’ve actually fixed this on the master branch already, post-0.10.

To fix things on the release build, you’ll have to do something like this on the command line:

sqlite3 ~/.mozilla-iot/config/db.sqlite3 "SELECT id FROM things"
# Find the ID of your old thing(s).
# The IDs were previously identical to the name you assigned.
sqlite3 ~/.mozilla-iot/config/db.sqlite3 "DELETE FROM things WHERE id = 'your id'"

Replace your id with… your ID.

After that, you can restart the gateway:

sudo systemctl restart mozilla-iot-gateway
1 Like
#12

Thanks, I had the same problem and solved by doing that.

#13

It isn’t working for me.

sqlite3 ~/.mozilla-iot/config/db.sqlite3 "SELECT id FROM things"

only returns the IDs of valid things. The timer IDs are all for the newly created timers that work. There are no IDs for the old timers that don’t work and I can’t get rid of.

I tried to do

sqlite3 ~/.mozilla-iot/config/db.sqlite3 "DELETE FROM things WHERE id = 'Leak-state'"

where 'Leak-state' is the display name of one of the old timers. (The new working timer has a slightly different display name.)

Also, I can’t get rid of the Zigbee device that I removed from the gateway (and removed the battery from the actual device.) I did

sqlite3 ~/.mozilla-iot/config/db.sqlite3 "DELETE FROM things WHERE id = 'zb-8418260000e90e56'"

and restarted the gateway. 'zb-8418260000e90e56' is the actual id. But it won’t go away. I can remove it on the Things page. But if I go into pair mode by clicking on the “+”, it keeps reappearing.

Just to double check, I’m restarting the gateway like

sudo systemctl restart mozilla-iot-gateway.service

Correct?

#14

The command worked for me. I was able to remove both the old timers. Did you get any errors when running the sqlite3 delete command?

#15

No. No errors at all.

#16

If you run it again, do you get an error? You should since the ID should not longer exist.

#17

I ran

sqlite3 ~/.mozilla-iot/config/db.sqlite3 "DELETE FROM things WHERE id = 'zb-8418260000e90e56'"

three times in a row and no error messages.

#18

Did you try a reboot afterwords? I know it should not be necessary when restarting the service, but it would not hurt to try anyway.

#19

Since the v0.10 update, I have been having weird random problems too. The gateway will lose connection to my HABridge about ever other day. This never happened before. This one has not been an issue for me.

#20

Just rebooted and no change. The old timers still show up on the Things page. The phantom Zigbee on/off switch still shows up when I get into pairing mode with the “+” icon.

Mine are more of an aesthetic blemish. I’m happy to have working timers again. The gateway seems to be working otherwise. But I’m not connected to anything like an HA Bridge.